ActivationEmail Plugin - can't modify System Events

I've installed Bob Ray's ActivationEmail plug-in version 1.1.0 on Revo 2.2.4, and am following his tutorial at http://bobsguides.com/activationemail-plugin-tutorial.html.

All went fine until I got to the point of duplicating the default Property Set for the plug-in, and pointing it to the copy I'd made of the "ActivationEmailTpl" chunk. When I edited the value for "activationEmailTpl", a red triangle appeared at the corner of the field to indicate that it had been modified. When I clicked the "Save" button, a progress bar appeared briefly at the centre of the screen, as I'd expect, but the red triangle remained, and the property wasn't updated. I eventually managed to work around this by going to Tools | Property Sets and modifying the property there - this worked.

However, the next step of the process in the tutorial requires that the OnUserBeforeSave System Event for the plug-in be pointed to the newly created and modified Property Set. Once again, I could modify the Property Set field, and the red triangle appeared. But when I clicked Save at the top, the "Please Wait. Saving..." progress bar appeared briefly, but the change isn't saved. And I can't see a way round this one!

Any ideas, please?

That's odd. I would try manually deleting all the files in the core/cache directory and, if that doesn't work, turning off the compress_js and compress_css System Settings. Go to System -> System Settings and type compress in the search box at the upper right.

See if there's anything helpful on the MODX error log (Reports -> Error log).


If none of that works, you could possibly be having trouble with mod_security: http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me




------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Hi Bob,

Thanks for getting back to me on this.

I tried deleting all the files in core/cache, then turning off compress_js and compress_css (compress_js was already disabled). But no dice. The Error Log is completely blank, although I know that it did have some (not relevant) entries in there yesterday. Guess it's blank as a result of deleting cache files.

I had a look at the wiki article on mod_security - it suggests modifying the .htaccess file. Thing is, I don't have an .htaccess file to modify. There is an ht.access file in the web root directory, but this looks like a sample file for use when setting up FURLs. Anyway, I tried creating an .htaccess file in the web root, containing some of the contents suggested in the wiki article. But this broke things altogether - any attempts to access the site or the manager interface just resulted in an "Internal Server Error" message in the browser!

Perhaps I'm misunderstanding how to set up the .htaccess file? Or maybe it should be in a different directory?

On many hosts, setting mod_security settings in .htaccess will throw a 500 error. Sometimes you can use a php.ini file (with slightly different syntax). Sometimes you have to ask the host to disable some mod_security settings, though I'm still not sure that's your problem.

Clearing your browser cache and cookies (and/or trying another browser) is worth a try.

You might just have a corrupted file in your MODX install, especially if you used FTP to transfer the files.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Maybe it is a corrupted file, as you say - I did use FTP to upload it all.

I ended up getting round the problem by hacking the database (I know, I know). My new Property Set had an ID of 1 in the modx_property_set table. And the plugin had an ID of 5 in the modx_site_plugins table. In the modx_site_plugin_events table, for plug-in ID 5, the OnUserBeforeSave row had the propertyset column set to 0 (the Default Property Set). I changed that to 1 in PHPMyAdmin, and that's done the trick.

Thanks for your help on this.

(BTW, my copy of your book arrived from Amazon a few days ago!)

Thanks for buying my book.

It's very common to get a corrupted or missing file when you use FTP to transfer the thousands of MODX files.

See this for another method: http://bobsguides.com/modx-upgrade-faq.html. The page is written for upgrades, but there's nothing stopping you from "upgrading" to the version you already have using this method.

What you did in the DB should be fine since it's what MODX would have done if it was working.



------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html [ed. note: BobRay last edited this post 14 years, 3 months ago.]

Great, I'll do that, and hopefully it'll prevent future weirdisms along those lines!

Thanks again for your help.