Comments

I wonder if you can make some sense of this for me - When I ftp'ed processtags.pl to the plugins directory, and chmod'ed it to 755, right afterwards I uploaded my index template with the process_tags="1" added to the MTEntryBody tag. Then when I rebuilt the site, the rebuild process hung, and I got a 500 error when loading mt.cgi. I decided to reverse what I had just done, and sure enough, when I delete processtags.pl, mt.cgi loads just fine. Another problem is that when the rebuild hung, it munged up my posts, so I have "double" posts inside all my posts. Appreciate any help you can provide. Sincerely, Rick Cogley rick.cogley@esolia.co.jp

Changing the perl script this way fixed this problem. # use bradchoate::postproc; if (MT->VERSION =~ m/^2\.2/) { require bradchoate::postproc; } Someone mentioned this on the MT support forum. Do you know why this worked? Kind regards Rick rick.cogley@esolia.co.jp

The Process Tags plugin gives MT a tag attribute that you can use to instruct MT to take the output of a tag (like <MTEntryBody>) and examine it for MT tags. At the time that I wrote Process Tags, MT didn't provide plugin authors with a method of creating tag attributes, only tags. Brad Choate wrote a plugin called postproc that gave other plugins the ability to create tag attributes. Process Tags needs Brad's postproc in order to run. In MT 2.51, Movable Type added support for global attributes so you can create attribute plugins without needing postproc. The new attribute support was added in such a way that older plugins relying on postproc could still use postproc instead of MT's built in attribute support. (MT's developer is a smart guy). So plugins that were written before MT 2.51 (like Process Tags) need postproc or need to be updated to work without it. Process Tags hasn't been updated, and still needs Brad's plugin. I know you said you have postproc installed, but there must be something wrong with your installation. I'm running Process Tags and postproc on MT 2.51 without any problems at all. The code change that you describe patches the plugin so that postproc is only needed if your MT version is 2.2 or 2.21. Otherwise Process Tags uses MT's built in attribute support.

I installed this plugin in MT 2.51, *without* installing Brad Choate's postproc.pm. I deleted the line use bradchoate::postproc; and the plugin worked *fine*. I think you should make clear that, while it may do no harm, postproc.pm is not needed with MT 2.51.

Excerpt: If you post pics to your MovableType weblog, and you do not wish to place them in several different locations so they appear in your archives, the Process Tags plugin is something I cannot recommend enough. I know; it has been out since August of last ...

Hey Adam, I'm having issues getting this to work with 2.63 . I get this error message upon posting: Can't call method "column_names" on an undefined value at /home/movabletype/lib/MT/App/CMS.pm line 1672. Any ideas?

I can't seem to get it running with MTAmazon (at least). I am running MT 2.63. I have modified main index template to read and then tried creating a test entry containing the following: "> " align="left" border="0"> Price: but nothing shows up when either previewing or publishing. I have tried running both with postproc.pm and without it (require commented out) Any idea what's wrong with the setup?

Oops, MTAmazon tags got sanitized :) Here's a try with HTML tags changed somewhat, hope they are still recognizable [MTAmazon method="Asin" search="0399149864" line="books" lastn="1"] [p][a href="[MTAmazonLink]"] [img src="[MTAmazonSmallImage]" align="left" border="0"][MTAmazonTitle] [/a][br] [MTAmazonReleaseDate format="%B %e, %Y"][br] Price: [MTAmazonSalePrice][/p][br clear=all] [/MTAmazon]

jeah! was just thinking about this same thing on my vacation. glad to come back and see it implemented ;)

Excerpt: A writeup on how I am using MTAmazon with the process_tags plugin, and how I created my own tag for standard layouts for Amazon items.

When I ftp'ed processtags.pl to the plugins directory, and chmod'ed it to 755, right afterwards I uploaded my index template with the process_tags="1" added to the MTEntryBody tag. Then when I rebuilt the site, an error occured. So, I cannot make entry with MTAmazony yet. MT::App::CMS=HASH(0x82ee79c) Use of uninitialized value at lib/MT/Builder.pm line 130. Appreciate any help you can provide. I use MT version2.64.

Excerpt: Some insight into the construction of this site with a smattering of tips and tricks...

Excerpt: Process Tags pluginp...

Exactly how do I use this plug-in? In my Index template I changed the line to But it doesn't seem to have any effect. My purpose for using process_tags is to allow my readers to vote on issues within an entry using: http://www.rayners.org/2003/03/mtvote_1.php

Have you got this to work with MT3.11 dynamic templates? I find that the process_tags attribute is ignored if you ask MT to build the templates dynamically (but works fine if you build the templates statically). Appreciate any ideas on how to fix this?

I'm having the same problem with MT's dynamic archives (v3.121)

awesome plugin... would love to use it. have installed correctally i believe... but it does not work. no error on rebuild or anything. its as if i have done nothing. the tags i use just end up in the mark-up... any ideas? soooooooo..... frusterating.

Excerpt: dank plugins kann man den funktionsumfang von movabletype schön aufbohren. mt-photogallery erstellt bildergalerien. process tags sorgt dafür, dass mt-tags auch in einträgen verarbeitet werden. damit das plug-in funktioniert, muss die datei "postproc...

Hello. I used this plugin Process Tags to use MTGoogleMaps plugin at MT 3.2-Release2. But, the error message were displayed during I rebuilt all stuff in MT. Undefined subroutine &MT::Plugin::GoogleMaps::GoogleMaps called at lib/MT/Builder.pm line 159. Stuation ------------- I edited index.html(Main index) template. Before : After : MT System Menu : GoogleMaps plugin settings My Google Maps API key and URL have been set. "Path to the template file" text field is "/var/www/html/mt/plugins/MTGoogleMaps/" Direstory Structure : /var/www/html/mt/extlib/bradchoate/macros.pm /var/www/html/mt/extlib/bradchoate/postproc.pm /var/www/html/mt/lib/MT/Builder.pm GoogleMaps plugin directory /var/www/html/mt/plugins/MTGoogleMaps/.DS_Store /var/www/html/mt/plugins/MTGoogleMaps/GoogleMaps.pl /var/www/html/mt/plugins/MTGoogleMaps/map.tmpl Other plugins : /var/www/html/mt/plugins/Blacklist/ /var/www/html/mt/plugins/nofollow/ /var/www/html/mt/plugins/spamlookup/ /var/www/html/mt/plugins/TemplateRefresh/ /var/www/html/mt/plugins/amazon.pl /var/www/html/mt/plugins/blogtimes.pl /var/www/html/mt/plugins/macros.pl /var/www/html/mt/plugins/MTIncludePlus.pl /var/www/html/mt/plugins/mt-isbn.pl /var/www/html/mt/plugins/MTPaginate.pl /var/www/html/mt/plugins/processtags.pl OS : Fedora Core 4 Environment : Perl v5.8.6 PHP 5.0.4 MovableType version 3.2 Release-2 mtpostproc.pm version 1.3 processtags.pl version 1.0 Please teach the problem that this MT cannot be restructured(rebuild?). As you see, my English is poor English. I will make an effort to forge an English ability every day. English that I use might be incomprehensible because of poor English. I rely on the translation engine only these sentences.

Hi - I installed Process Tags and MTGoogleMaps. I receive the following error from the cron job: Found = in conditional, should be == at cgi-bin/mt/plugins/GoogleMap.pl line 249. Subroutine MT::Template::Context::add_global_filter redefined at cgi-bin/mt/extlib/bradchoate/postproc.pm line 22. Subroutine MT::Template::Context::post_process_handler redefined at cgi-bin/mt/extlib/bradchoate/postproc.pm line 41. Any suggestions? Thanks in advance.

Wow, That was easy. Great plugin. Exactly what I was looking for. Thanks.

That was just what I needed! Thank You! Thank You!

Where does this go? Thanks

MTCategoryDescription process_tags="1"

Hi~ I think it is a great plugin that I wanted. But is it available to use this plugin in MT 3.2? Actually I failed to use this in my weblogs. (Every tags with this parameter meet an error messages which notifies the out-of-contexte using of template tags)

Thank you very good plugin! Process Tags plugin needed small hack to work with MT3.2. But with MT3.31, original code works fine for me. Regards, Hisaaki Shibata

I can confirm that commenting out "use bradchoate::postproc;" allows process_tags to work with MT 3.3 without requiring the postproc extension (which was disrupting Notifier on my installation). additionally, by comment out the said line, the MT Plugins interface allows you to see the process_tags 'resources'; ie, the process_tags attribute. thank you for the plugin. I can now refer to entries by id from within entries without fear of urls gone wrong: regards, Gregory

Has anyone been able to make the process_tag work with MT4.1? I'm having trouble and can't figure out which lines to change to make it work. Thanks in advance for your assistance -- I'll be happy to provide details as requested.

ProcessTags is working with 4.1 ;-) I downloaded v1.0, commented out the "use bradchoate::postproc;" line and uploaded it to my MT4 server. I did NOT upload the postproc.pm file. at first, I thought it wasn't working and then I realised that I had reverted the template sets to an MT set and needed to reinsert the process_tags="1" attribute in each and every instance of , and . once I had done that and republished the files, everything worked fine. note that attributes are processed in the order that they are specified in the tag (new in MT4?). therefore, and are very different.

Thanks Gregory, been trying to get this to work for ages, tried the same method as you and it worked!

I uploaded both parts of the plugin, added the tag to the entry more tag, and presto it works in 4.2 Excellent..

Question: We have downloaded the plug in because we want to use the template variables on pages and entries. We also downloaded the FCK editor plugin and re-configured it. I created a page that uses a template variable, when I'm in the WYSWSG editor. I save the page, and I can see the variable's value on the page in the browser. However, if I re-open the page in WYSWSG mode, it breaks the variable by putting the < and > in place of the that close the variable. So instead of having this on the page: Instead you have: <$mt:var name="test"$> I would really appreciate any assistance on this issue. Thanks

Thanks gonna try this, even bearing in mind the freshness warning...hope it works. cheers p