Thread

Thank you Derek about executing my feature request 😊

:-D

not to discredit this great extension but I’m personally a fan of “locking” out other users IF the lock requires ACTIVITY on the edit page. I get that often when I do online banking, where the session ends if no activity has been detected within 20 min.

The Edit Alert extension could be used as a stepping stone to such an extension that actually locked out areas, but for reasons I explain in the blog entry, it’s not something I have a personal interest in developing, and isn’t likely to make it into the base application for similar reasons.

I am wondering, will this extension work with a stand alone edit form for the weblog module rather than the wiki?  So that a message is displayed within the front end entry edit page itself when the article is being edited, either through the CP or the stand alone edit form?  I have a wiki style site but am not using the wiki module because of its custom field limitations.

It could be modified to do so, lee, but as stand alone edit forms are not a base feature, I did not use the weblog standalone form hooks in this extension.

Thanks for the Reply Derek.  If you do develop this extension further, this is a direction I think would be useful to many.  Thanks again.

Anyone know why this extension doesn’t work with either the FCKeditor or TinyMCe extensions enabled? If I use this extension by itself, it works fine. If I try to use it while either the wysiwyg editors are enabled, the show_alert() javascript function doesn’t get generated and since the page tries to load it, a javascript error gets generated. It looks like for some reason the extension code that generates this javascript function doesn’t get executed.

Try changing the priority of the Edit Alert extension so it gets ran first.  It could be that the other extensions are not retaining the changes that the Edit Alert extension is introducing.

Derek, I changed all the priorities in the Edit Alert extension to 1, and the wysiwyg editors both have their priorities set to 10, yet the same problem occurs (I obviously only enable one of the wysiwyg editors at a time). I don’t use any other extensions so I’m open to suggestions.

Are you using the latest versions of said extensions?  I thought we had updated them all to be multi-extension friendly, which would make my initial guess irrelevant.  Just trying to rule out some common problems as I don’t have time immediately to examine the extensions to see if it’s something altogether different.

The three extensions I was testing (Edit Alert, FCKeditor, and TinYMCE) were all downloaded within the past week so I’m assuming that they’re the latest. It would seem that something is preventing the Edit Alert extension from generating the actual javascript function although the onload call to that function is added to the body tag.

Well I managed to find a workaround although I’m not exactly sure why it works. I set all the priority levels in the Edit Alert extension back to 10 and then before the

return $ret;

echo $ret;

which solved the problem. It now works with either of the wysiwyg editors and by itself. Any idea why?

Well that sounds like it supports my first theory.  I’ll double check the extensions this afternoon and will post back with the details.

Thanks Derek

That was indeed the case, TinyMCE was not utilizing $EXT->last_call to work with other extensions using the same hook.  I have updated it.  If you revert your change to the Edit Alert extension, and replace your TinyMCE extension file with the updated version (1.0.1), compatibility should be restored.