Moving this to alpha/beta
Have you tried it on 2011?
Have you tried turning off your other plugins?
Thread Starter
C0BALT
(@c0balt)
I have tried with all other plugins off, as I originally said in the post.
I have also tried it with a third party theme and 2010, both with all other plugins disables.
I have also tried now with 2011 theme, and I get the same result.
Ultimate Post Type Manager 1.6.9
WP 3.3b2 AND WordPress 3.3-beta2-19067
PHP version 5.2.17
MySQL version 5.1.58
I can confirm the issue, and I had a look at the plugin’s code. It is calling wp_tiny_mce(), which has apparently been deprecated in 3.3b (in favor of wp_editor(), which seems to work quite differently). The plugin writer(s) will need to rewrite the plugin for 3.3 compatibility.
Can also confirm this. Have tried to contact the author, both on his blog and in this forums. No response yet.
On a few sites of mine, this plugin is so essential that it will stop me from upgrading WordPress on those.
What I can’t understand is that using a (newly) deprecated function makes an editor appear on top of every admin screen. Using a deprecated function usually just causes a warning when debugging.
Yeah, it does seem odd. I haven’t had time to really dig into the code, but it seems to me that the older wp_tiny_mce() function worked more like a “preloader” in that it would queue and/or load certain files needed by the editor, but not actually initialize the editor. The plugin would then initialize it later on, conditionally.
Evidently, the wp_editor() function works very differently. It may seem wrong to replace a deprecated function by one that works so differently, but I believe wp_tiny_mce() was never a documented function, and therefore not subject to the same expectations?
No, not documented doesn’t mean not subject 🙂 Just means no one documented it.
As Knut said, it should only give you an warning, and even then ONLY if you’re debugging. You didn’t turn debugging on, did you?
Ipstenu, no, I didn’t have debugging turned on. Tried again now with debugging on, and it does indeed give the deprecated warning.
Any insight into why the two functions behave so differently? Seems to me that any plugins using wp_tiny_mce() may encounter the same issue in 3.3
Or could it just be that this particular plugin was using wp_tiny_mce() incorrectly in the first place, but in such a way that (by pure luck) it still managed to work?
Hi,
I have made the changes and will be updating the plugin soon and that too before 3.3 is released.:)
Regards,
-Xydac
and sorry for being so unresponsive..didn’t get much time these days…:P
-Xydac
Thank you for fixing it, Xydac! 😀 Getting it done before 3.3 goes live is perfect 🙂
Wouldn’t it be good if there was some kind of downward compatibility for the new wp_editor() function? Otherwise all plugins using the tiny_mce function (and these are quite a number) will most likely generate errors. I have already encountered two …
I know you don’t have a lot of time, XYDAC, but I was hoping you would be releasing this update soon so that I can update to 3.3. I’m going to go make a donation right now! Good luck and Happy New Year.
I fully stand behind what @negs says. I have also made a contribution, and hope for a release of the updated, 3.3 ready, version of this great plugin.
