MT-Notifier 1.2.0 »
I've just released an updated version of MT-Notifier. Most of the changes are behind-the-scenes, and you won't see much different about the operation. However, there are a couple of new features, notably an enhanced ability to specify the "from" address on your outgoing notifications.
While versions prior to 1.2.0 had a $SENDER variable defined inside the notifier.pm module, versions 1.2.0 and higher will store this information in the plugindata table, along with the subscription information. This also allows a default address to be set on a per-blog or a per-installation basis.
If you have a version of MT-Notifier prior to 1.2.0 and would like to upgrade, simply copy the contents of the distribution over the existing files. Please note that this will erase the $SENDER value in your current installation, so you'll want to go right to the management interface and enter your new default address(es)!
You might also want to take a look at the new and improved online documentation for MT-Notifier. This link will always contain the most recent documentation and information about MT-Notifier, as well as a link to the most current version.
Comments (6)
When install 3 files and do connect to mt-notifier. cgi the following error comes out. How do do and be?
An error occurred: Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 106. Global symbol' $ auth' requires explicit package name at extlib/jayseae/notifier. pm line 106. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 107. Global symbol' $ auth' requires explicit package name at extlib/jayseae/notifier. pm line 107. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 108. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 109. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 110. Global symbol' $ auth' requires explicit package name at extlib/jayseae/notifier. pm line 110. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 111. Global symbol' $ auth' requires explicit package name at extlib/jayseae/notifier. pm line 111. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 112. Global symbol' $ auth' requires explicit package name at extlib/jayseae/notifier. pm line 112. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 113. Global symbol' $ auth' requires explicit package name at extlib/jayseae/notifier. pm line 113. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 114. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 114. Global symbol' % param' requires explicit package name at extlib/jayseae/notifier. pm line 115. Compilation failed inch require at mt-notifier. cgi line 37.
Posted by KOW on December 14, 2003 9:21 PM
As for MT-Notifier is MySQL necessary?
Posted by KOW on December 15, 2003 2:51 AM
Hi KOW - Looks like that one was my fault. Somehow a copy of a development module was in the archive. I think I updated the module on my site, but not in the archive. It should be all set now. Please re-download the distribution. You'll only need to reinstall the notifier.pm module.
As to MySQL, yes, it is required for the proper operation of MT-Notifier. I've got some ideas banging around in my head to make it work in other environments, but as of now, MySQL is a requirement.
Posted by Chad Everett on December 15, 2003 5:56 AM
Hello. I am using Berkeley DB. Because I am unable to try new distribution.
When is it that MT-Notifier corresponds to Berkeley DB and PostgreSQL? I am waiting to enjoy it. Thank you.
Posted by KOW on December 15, 2003 6:52 PM
As I understand it, the MT::PluginData module doesn't work all that reliably with either Berkeley or PostgreSQL. However, I don't have any actual experience to back that up - I'm just working on anecdotal evidence. You may wish to try MT-Notifier and see what happens.
If it does not work, then it will probably require me to use a solution similar to YAML, as Jay Allen did with MT-Blacklist, which essentially would allow the data to reside in text files on the server. I have no timetable on such a project at this point, but will be sure and post any progress here.
Posted by Chad Everett on December 15, 2003 6:57 PM
I put in new distribution. If it does it so MT-Notifier worked. I am sorry to misunderstand. Thank you very much.
Posted by KOW on December 16, 2003 1:27 AM