Gilou24

Hi Jose,
Sorry, but I just updated to version 1.8.8.7.4 and my site crashed.
I’m talking about the problem with Thrive Leads (it’s ok for adding the mobile version)
So I added commented out the last line of the free-soul-deactivate-plugins.php file again to make it work.
Regards,
Gilles

I don’t see these elements …

I have also just done the inspection test of the elements … which seem to be present (see here: https://i.imgur.com/tzaarwW.jpeg)

Ok, mu-plugins did indeed contain the following files:
freesoul deactivate plugins [fdp]
Health Check Troubleshooting Mode
passwords-functions.php
I temporarily deleted these files to verify, but that did not resolve the issue

I just sent you, via the contact form of your website, the copy of the environment information concerning my blog.
Hope this can help you solve this problem.

In fact, not having recently created a mobile page, the problem may be older …
I just deactivated Rank Math SEO. It doesn’t change anything.
Well, I can’t afford to deactivate all plugins …
But I installed the Health Check & Troubleshooting plugin which allows testing without changing anything on the blog on the visitor side.
As you can see in the video (https://un-jardin-bio.com/tmp/plugin-deactivated.m4v), even with the default theme and all plugins disabled, except “Specific Content for Mobile”, the add mobile version button does not appear …

Sorry, I use Rank Math SEO (pro) plugin…

Hi,

I have the same message error a lot of time on error-log.php file :

[11-Aug-2021 05:18:38 UTC] PHP Warning: Attempt to read property “ID” on bool in /…/wp-includes/post-thumbnail-template.php on line 106

Gilles

ok, it works by commenting out the last line of the file with //
So you got it right.

On the other hand, I don’t have an error message for the mu-plugin version (the folder has 755 permissions and the eos-deactivate-plugins.php file has 644 permissions)

ok, it works by commenting out the last line of the file with //
So you got it right.

On the other hand, I don’t have an error message for the mu-plugin version (the folder has 755 permissions and the eos-deactivate-plugins.php file has 644 permissions.

I don't know if this can help you, but here is the code affected by the error:

/ **
 * check if the current TCB version is the one required by Thrive Leads
 *
 * @return bool
 * /
function tve_leads_check_tcb_version () {
if (! tve_in_architect ()) {// the internal TCB code will always be up to date
return true;
}

$ internal_architect_version = include TVE_LEADS_PATH. '/tcb/version.php';

/ * make sure that the we have the same version of architect inside the plugin and as individual plugin, otherwise conflicts can appear * /
if (! defined ('TVE_VERSION') ||! version_compare (TVE_VERSION, $ internal_architect_version, '=')) {
return false;
}

return true;
}

If you need anything else (entire file, or copies of other Thrive files …) to fix the issue, don’t hesitate to ask me.

Best regards,
Gilles

• This reply was modified 3 years, 3 months ago by Gilou24.

what surprises me is that by updating FDP directly on the blog, the mu-plugin version does not update (it remains in 1.8.8.6); contrary to what you told me …

I confirm that Thrive Leads does not need Thrive Architect to function. I just deactivated it on the plugin management page and everything works fine (with FDP version 1.8.8.6)

I made the last update (back to 1.8.8.7) directly on the blog, but the mu-plugin version remained in 1.8.8.6 …
And, as you thought, after disabling and then re-enabling FDP, I have the fatal error again …
The problem is as much on the home page as on the articles …
In the meantime, I tested by activating Thrive Architect on these pages to check, but that doesn’t change anything (and a priori, Thrive Leads works without Thrive Architect …).
I have just put version 1.8.8.6 back again so that my site does not crash … and there the mu-plugin version is back to 1.8.8.6 …

Thank you for your quick reply.
I did the update again to check … and the problem no longer occurs…
Maybe there was a problem updating ?
Best regards,
Gilles

Hi,
3 months later…
Thanks
Gilles