Plugins broken in 4.6

Edit: Aside from restructured admin HTML, there are some code changes in Textpattern 4.6 that might lead to misbehaving plugins. Some nice people (Bloke, ruud and michaelkpate) have set up forum posts in order to bring possible plugin issues to your attention and offer fixes for those. Here’s the list of these postings:

Re: Plugins broken in 4.6

stm_article_order

Broken feature:
Completely broken

Can be fixed with:
Hopefully: some compatibility changes to adapt the plugin to Textpattern 4.6’s current jQuery version (v1.12.3). It works again as soon as Textpattern 4.5.7’s jQuery v1.8.3 is used in /textpattern/lib/txplib_head.php

If you know what changes need to be done, please post here. Thanks. done

Re: Plugins broken in 4.6

[stm_article_order] If you know what changes need to be done, please post here.

The primary issue is that jQuery.browser no longer exists so browser detection is out. Trawl the code for any mention of jQuery.browser and remove / replace it. List of possible fixes are below. Note that ones marked with an asterisk may potentially break Opera, so require testing.

That at least allows dragging again, but as I say, there are Opera-specific tests that have been removed, which may need to be addressed with some clever tests. With luck, the tests may not be required any more since Opera changed their rendering engine. Whether there’s anything more that needs fixing after that remains to be seen.

Re: Plugins broken in 4.6

Ah, Stef, thanks! That brought it back to life. During the weekend I’ve tried to follow some blog tips but only tore my hair, so I ended up dropping in the migrate plugin, for the cost of yet another 10kb. Much better now!

Need to align some changes with the stm_ao-migrate version now and see what happened with the GIF/PNG part that got lost somewhere (not contained in v0.3). And throw in again Claire/cbe’s change, and then it’s ready for some nice folks that want try the mangy beast, esp. on Opera.

Re: Plugins broken in 4.6

Hi, Jean-Pol, that’s a good one, thanks! My most important fields are working (forms, pages, CSS). Except for article, which will become the most important one once the website is handed over to the clients. Did article save ever work in rah_post_versions after the move to AJAX saving? (Very likely I didn’t use it any more because of that but I really can’t remember.)

I’ve a vague feeling it might simply be the the ident code for article in the plugin preferences: