Here is a gotcha I just found. I had been getting reports that the related entries plugin stopped working for some (not all) people when they upgraded to MT...
For those not on or closely monitoring ProNet, Byrne posted this handy piece of code below. Where was this when I needed it!? ;) I really wanted to do...
Hi all I'm writing a ruby app that is posting to MT via XMLRPC and for simple text it works fine some of the time with toy examples, but trying with the real...
Oops I've got XML::Parser 2.34 installed on perl 5.8.6 if that helps Looking at forums it seems to be related to foreign character support any further ideas...
Hi Gavin, That error message is almost certainly related to a character encoding problem... what is the character set specified for the XML you're sending?...
Today I tried to use the plugin_action in one of my plugins and was quite frustrated with the results. I wanted to use that method to create a link on a MT...
In the ProNet post Byrne made on using the new upgrade features in MT ... Perhaps I'm misunderstanding something. Where am I supposed to have have the...
Ideology aside, I've really wanted a set of first class coding standards for plugins forever. I've asked for this a few times, but no one has ever really given...
I liked the neatness of putting everything in one file (yes, bloated, but easier to install). All the templates as scalar variables, inlined, plus adding app...
I'm with you David -- having everything in one file makes it harder to navigate your code and re-use previous functionality. However it seems that it's popular...
Yea, well, I had everything in plugins/MTLJPost/ for a while, then .cgi files in places, putting things in extlib, etc.. I just found it easier for people if i...
Hi Tim, ... I might be misunderstanding you on this point, but are you saying that plugin libraries should go into lib/, CGI scripts into the main directory,...
... The file that does all of the registering would still remain in plugins as would templates and any other misc. files. I'm find with that though I have to...
Sorry - I should have been more explicit: There is no "initialize_plugin" method - that is my own fabrication. I just wrap it in a subroutine for easier...
So in other words, use init_request. That method checks a configuration param or some other piece of data to check what version of the object schema was last...
Based on how you implemented you need a MT::App in your package that is presumably run before any part of the plugin is run. Is that correct? If so, I take it...
Let me see if I can probe Brad to give us an overview of this feature. To be honest, I have not cracked open 3.3 yet - I am still hacking on 3.2. :-D <nudging...
... Tim, you may like that better as a plugin developer, but, as a user, I like all of the plugin code in one subdirectory of plugins/. That way, when I want...
I also like the "single directory" option from a user perspective. It's marginally easier for me personally, and I can make do with the other method if needed...
... A related issue is plugins that are distributed as part of a package but also on their own. Tim mentioned BigPAPI in his original post--I had intended for...
Agreed - I've seen this behavior on BigPAPI as well (I typically try and keep it in the "plugins" directory, but I'm sure I may have missed it once or twice)....
Ooh, yeah, the php vs perl plugin installation routine annoys me too in terms of having stuff spread all over the place. At the same time, I hear the request...
I totally forgot about PHP plugins. Is there a list of the best PHP MT plugins? I'd love to look at the code for inspiration. David ... -- djacobs@... ...
Well, the "best" PHP plugins for Movable Type are just called plugins. That is, they run equally well under both PHP (dynamic) and Perl (static). Did you mean...
This is a good conversation. Here are some thoughts from throughout the thread. I'm all for making plugins as easy to install and manage for users. I am...
New keys you will be able to register with your plugin: schema_version and object_classes. MT->add_plugin(new MT::Plugin({ # stuff ... schema_version => 1.0, ...