WordPress 4.2 update causing multiple issues

1 and 2. As these are commercial products, we ask that you please go to their official support channel. In order to be good stewards of the WordPress community, and encourage innovation and progress, we feel it’s important to direct people to those official locations.

Forum volunteers are also not given access to commercial products, so they would not know why your commercial products are not working properly. This is one other reason why volunteers forward you to the commercial product’s vendors. The vendors are responsible for supporting their commercial product.

3. Try deactivating all plugins. If that resolves the issue, reactivate each one individually until you find the cause.

If that does not resolve the issue, try switching to the Twenty Fifteen theme to rule-out a theme-specific issue (theme functions can interfere like plugins).

James,

I appreciate and understand the viewpoint but this isn’t a plugin issue, it is very much a WordPress issue.

I have overcome the problems, since 4.2.1 was released a few hours after 4.2. I had to roll back several client sites but the majority simply needed 4.2.1 to be installed (or re-installed in some cases) and then the commercial plugins all started working again.

Talking to several theme developers and plugin developers I can see very clearly that 4.2 caused a great deal of anguish for site owners and developers and, in truth, there are still issues. But I’ll deal with the individual plugin developers on those as I am sure between them there will be plenty of positive input to overcome the 4.2 and 4.2.1 release.

I appreciate and understand the viewpoint but this isn’t a plugin issue, it is very much a WordPress issue.

Sort of. Plugins and themes have to play nice with WordPress, not the other way around. If it weren’t that way then development would come to a halt. ??

4.2.1 is compatible but some authors have implemented code that doesn’t necessarily work going forward with new versions. It’s usually the way the API is called in the theme or plugin.

1. In my own site I was asked to update the database after the update and then my home page Revolution Slider ceased to display. The Avada theme developers are looking in to this issue.

The problem is on your site and with the code you are running, the Avada theme and Revolution slider. That’s why James replied as he did and those authors need to fix their code to make it work with 4.2.1 (the .1 is important BTW).

Now you are running a production site and upgrades should be vetted by you before you upgrade. If you do choose to roll back to an earlier version till those authors get it together then I recommend 4.1.4.

I’m not advocating old releases but that one has been patched as well to address the XSS comment issue. Once Avada and Revolution slider are up to date then you may want to test 4.2.1 and then roll it out to your live installation.

Jan,

“Sort of” … sure, I get the symbiotic nature of the core and anything that tries to hang of the core but in this particular case there were no changes to code of any plugin or theme to get things to work. As soon as 4.2.1 was installed the plugins started to work again.

The rolled back sites have since been updated to 4.2.1 and everything is back to normal. Again, no plugins that were affected by 4.2, have been updated to make them work.

For the record I am not knocking WordPress – I am a massive fan. I was simply seeking help and advice.

Ok, so now that you’re on 4.2.1, everything works as desired for you?

James,

Not entirely. I have ‘fixed’ all but 2 websites.

One site refuses to allow the VFBPro to update and the other site still needs to be updated from 4.1.4 back up to 4.2.1 but that’s more because I am waiting for some server side changes to come in to play.

So the one site that won’t update the plugin is in the hands of that plugin developer…..but I am happy to try any other suggestions on offer. I have previously tried changing to the 2015 theme and disabled all plugins but to date nothing is working.

While waiting for the plugin developer, are you able to just update that one manually by uploading the new plugin via SFTP?

James,

I am nervous of doing that because when this issue first happened I deactivated and uninstalled VFBPro and manually uploaded the plugin via FTP.

On logging back into the site after the manual upload I activated the plugin and was asked to update the database, which I did, and then found that the plugin data (a complex form) had been zapped. No form. That’s why I had to restore the site.

So I have now just updated that restored site to 4.2.1, updated the plugin and everything is back to normal. Now I have just one site (one of my own – not a client site) that refuses to budge.

But the good news is that I can do whatever I want with that site! allsortsofstuff.net is a WordPress site with the Classipress theme plus a flat styled child theme. I have changed this to 2015 and deactivated plugins but VFBPro still wont update.

Ok, I understand. Hopefully the developer behind the plugin will get back to you soon.