[Résolu] JS Errors in admin area since last upgrade

[Auteur]

Publications

[davidM-29]

JS Errors in admin area since upgrading to latest versions of Types and Views - disable the pair of plugins and the JS errors go away and functionality is immediately restored

Re-enabling Types is fine - it is Views that is causing errors and the backend to not work

[Nigel]

Hi David

Could you share a screenshot of the errors or copy and paste them here so I can see what we're dealing with.

We already have some reports of errors but I need to know if yours are the same.

[davidM-29]

Hi Nigel - screenshot attached

[Nigel]

It looks like you will also have PHP errors in your logs if you could check there which may be related to a conflict with the Events Manager.

Could you please run a conflict check.

Start with your theme, switching to twentyseventeen.

Then try disabling all non-Toolset plugins and see if you still have the error.

If not it should be possible to identify which plugin is causing the conflict, and we can try and reproduce that on an independent site.

[davidM-29]

It is not particular to adding a new event - I can go to add a new post and see the same mess - Yoast is dead amongst a lot of other things - same with new page - the only plugins upgraded this morning were types and views and as I said previously - everything works perfectly if views is disabled ... and there were no errrora prior to the upgrade of these two plugins

[Nigel]

A conflict is the most likely cause.

If you want you can provide a copy of the site and I'll try the conflict tests: lien caché

I'll set your next reply as private for you to share the backup.

[Nigel]

Hi David

I tried to take a copy of your site for testing locally but was unable to. Duplicator won't install, and the All in One WP Migration archive I made failed to complete importing on my local test site.

So I did some conflict testing on your site and found that the issue was still present if I de-activated all plugins except Types and Views, but that it disappeared if I switched theme to twentyseventeen.

So I installed the flatsome theme on my local test site to see if that in combination with Views 2.6 would produce the errors, but it did not, it is only happening on your server.

The JS error reports a 500 error from the ajax call if you try and edit a post, so your debug logs will have useful information, but I don't have FTP access to check them.

Can you please ensure debugging is enabled in wp-config.php, and let me know what the fatal PHP errors are when editing a post?

[davidM-29]

OK - I have asked the hosting company for that info - I can go back a version of Types and Views - that will resolve it - the evidence of it failing is all over the edit screen not just when you try to save - look at the RichTextEditor or the Yoast tabs - anything Javascript is failing at page load

[davidM-29]

Right - so if I look at the site this morning - with loads of plugins disabled - there is limited front-end functionality & the back end is still broken

So I have reenabled enough plugins to get back to where it is fuinctional on the front end - the backend is still broken

(Please dont ever leave HideMySite disabled - this is a beta site _ not for the public to see)

I have gone through the log file for the last couple of days - nothing of any real interest in there

Typically

[01-Jun-2018 01:07:06 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 01:07:06 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 01:07:06 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 01:07:06 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 03:04:20 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 03:04:20 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 03:04:21 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 03:04:21 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 03:46:51 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 03:46:51 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 04:26:46 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 04:26:46 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 04:26:46 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 04:26:46 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 05:02:32 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 05:02:32 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 05:02:32 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 05:02:32 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 05:37:41 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 05:37:41 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 07:12:23 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 07:12:23 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 07:12:23 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 07:12:23 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 07:12:29 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 07:12:29 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 07:18:37 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 07:18:37 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 07:18:37 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 07:18:37 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 07:19:09 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 07:19:09 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 07:19:11 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 07:19:11 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 07:19:41 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 07:19:41 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76
[01-Jun-2018 07:19:45 UTC] PHP Notice: Constant WP_DEBUG already defined in /home/naturesl/public_html/beta/wp-config.php on line 75
[01-Jun-2018 07:19:45 UTC] PHP Notice: Constant WP_DEBUG_DISPLAY already defined in /home/naturesl/public_html/beta/wp-config.php on line 76

[Nigel]

Hm. The JS errors report 500 errors for the ajax requests, so there should be PHP fatal errors in the log.

I'm going to need a copy of the site, but the backup plugins I tried failed, so could you please provide a SQL export of your database. I'll install that on a local site with the required plugins etc. You can provide a dropbox link or similar here.

I was trying to be careful to leave your HideMySite plugin activated, sorry if I didn't.

[davidM-29]

Here you go - it is smaller than I expected - but that is a good thing

lien caché

[Nigel]

Thanks for that.

I imported it into a local test site, and tried to reproduce the error as I saw it on your own server, with Types and Views and the Flatsome theme active, but cannot.

I've asked my colleagues for advice and will get back to you.

[davidM-29]

Ok - for now - I have gone back to the previous version of the plugins - not having a working back-end was crippling us getting the new site live

And ... as soon as I installed them, everything came back to life!

[Beda]

Please try this:

1. Delete the Toolset Software in your install completely
2. Download fresh copies manually. From here:
https://toolset.com/account/downloads/
Please download each plugin you need manually
3. Upload them to your system and activate them

Is the issue gone?

I ask to do this because I can see that your site suffers from a problem with our installer – it wants to ship you a completely wrong update.
This is due to the fact that this site is not registered for Toolset as it seems, and hence, it pulls updates from WordPress ORG system which delivers you another Types version.
If you install that Types version, installer and other updates stop working.

I assume, there might now be a little mess of wrong updates in the system, which should be possible to solve as above outlined.

Please make a backup before you proceed.

If then the issue persists, we need a copy where we can see this issue.

As the copy Nigel has did not help us nor him to see the issue, we would then need to grab a new one, perhaps making first sure on your staging site to disable all non-Toolset Plugins and custom Themes to check the error again, and then duplicate the site (Database backup AND FTP files from that very moment will do.)

If the issue persists after above steps please if possible can you provide us with the required data to proceed?

Last resort, if we still cannot replicate, is to deploy your site on a server of ours to see if we can work together on this exception.

[davidM-29]

Hi Beda, that is how I do an upgrade - I go to toolset.com - download the new files - delete the old versions on the beta site - upload the new versions & activate - so I am following the procedure you want me to anyway - that does not work, as I get into the non-working backend scenario

Additionally - when I first encountered the issue - I removed the installed versions of types and views as well - and pulled new versions from toolset,com - but that had the same end result