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

near line 148 I added before it:

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.

Thanks Derek I’ll check it out. I’m assuming that the FCKeditor extension is doing something similar and I’ll see if I can make heads or tails of where last_call goes there.

I just wanted to say thank you - thank you! I found out about this just now in response to a question about building in entry locking and am excited to put this to use. I haven’t tried it yet but still want to say, “Wonderful work!”  It’s great to see so many things continually released for EE - it makes me happy to have joined the EE train.

Does quick Saving extent your time on the article?

This extension isn’t working for me on 1.6.2 Build:  20080124

Other extensions

Add Sitename (v.1.1.2)
Geo Coordinates (v.1.0.5)
Fresh Variables (v.1.0)

Looks like Geo Coordinates (v.1.0.5)  and this extension don’t get along. It worked after I disabled Geo Coordinates

I’m not familiar with that extension, textdriven, but if you contact the author of the extension (or if you are capable with PHP), they should be able to get it to work alongside other extensions by using $EXT->last_call.

It’s an extension by Mark Huot

http://expressionengine.com/forums/viewthread/40657/

I’ll let him know.