Forums » Plugin: Jetpack - WP Security, Backup, Speed, & Growth » Problems with the plugin

  • Resolved sergialarconrecio

    (@sergialarconrecio)


    Problems with the plugin (PHP Warning: DOMDocument::loadHTML(): htmlParseEntityRef: expecting ‘;’ in Entity, line: 1 in /home/sainformatica/public_html/wp-content/plugins/jetpack/json-endpoints/jetpack/class.jetpack-json-api-plugins-endpoint.php on line 214)

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    Thanks for the report! I believe this may be a conflict between Jetpack and another one of your plugins.

    Could you try to deactivate every other plugin on your site, one at a time, and let me know if you find the conflicting plugin? Once I have more information, I should be able to reproduce the issue and find a way to fix it.

    Thanks!

    I get this when I try to load the WooCommerce status page:
    /admin.php?page=wc-status&tab=status

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    @amityweb Could you follow the instructions above and let me know if you can narrow down the issue to a conflict between Jetpack and another plugin?

    Thanks!

    Sorry its a live site and the issue is with Jetpack, so I have had to disable Jetpack, not other plugins. Thought I would let you know of the Jetpack issue thats all. If I have time I will try to list the plugins we are using.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    @amityweb If you have a chance to reproduce the issue on a test site where you can deactivate other plugins, let me know!

    I also had a jetpack file not found error after upgrading, maybe its related to this. I could see some folders and files missing in the Jetpack plugin folder. So I completely deleted Jetpack and reinstalled and it all installed OK. So I think an automated Jetpack update resulted in not all files being downloaded causing errors. I had issues with the latest Jetpack release on several sites, so I am going to try uninstalling and reinstalling Jetpack on them all.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    That could indeed play a role. If you keep experiencing issues with plugin updates in the future, I would recommend that you get in touch with your hosting provider, and ask them if there are any limitations on your hosting plan that may cause issues when downloading large zip files or uncompressing them.

    We found the exact same message (except the name of the site, of course)–four times over about five minutes–in the error_log in public_html.

    We don’t have WooCommerce. And since we can’t disable every other plugin or build a new site–and we don’t know when the warning recurs anyway, since the log has all of one day in it–what is the importance of the warning? What might it mean in the context of this plugin and WP in general? Those seem important to know and are missing from the thread.

    I only came across the log in the first place because we’re troubleshooting periodic high CPU/IO issues (the times in the log don’t correspond with these issues, so I don’t think they’re related). I don’t know of any issues with the plugin, though that’s not to say that there aren’t any, since it’s a big plugin and I’m not familiar with all of it.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    @bjf2000 Would you be able to clone your site and see if you get the same warning on a test instance with the same plugins and the same settings?

    If so, could you then deactivate each one of your plugins, one at a time, and let us know if you find the source of the conflict?

    No, I don’t have an environment for that. Plus, I have no idea if it even recurs, or if it does, when. Do we even know necessarily that it even relates to another plugin, as opposed to a theme, or something else like the version of PHP (7.1, for example, has been causing some problems recently for JetPack)? What is the meaning of it in the first place? That might be the best place to start. Maybe here is a better place for this:
    https://github.com/Automattic/jetpack/issues

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    Do we even know necessarily that it even relates to another plugin, as opposed to a theme, or something else like the version of PHP?

    It could come from a conflict with your theme or a plugin. I can’t tell you which one though.
    It doesn’t come from your version of PHP though.

    (7.1, for example, has been causing some problems recently for JetPack)

    You’ll be happy to hear that we solved all those PHP 7.1 compatibility issues in the last Jetpack release!

    What is the meaning of it in the first place?

    It happens because there are some wrongly encoded characters somewhere on your site.

    Maybe here is a better place for this:
    https://github.com/Automattic/jetpack/issues

    We will work on suppressing those warnings in a future version of Jetpack so the errors are not reported anymore (you can follow our progress here), but until then I’m afraid the only way for you to figure out what is causing this is to proceed by elimination to find what’s adding those characters. The other alternative would be to ignore those errors since they don’t directly impact your site.

    Thanks for creating that over at Github.

    You’re right about it not relating to the PHP version. We had temporarily switched back to 5.6 for unrelated reasons this week, and I noticed that the errors appeared twice more in the log.

    Yes, to my knowledge JetPack doesn’t have a problem with the site, but as you know, JetPack does a lot of things, and I’m far from an authority on most of what it’s doing. In other words, while it would be nice if the warnings are inconsequential, I don’t know one way or the other.

    Just as note that other users also get this warning like me – last on 14-Oct-2017 running Version 5.4.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    @fireemerald Yes, the fix was only added recently. It will be included in the next version of Jetpack.
    If you’d like, you can apply it to your own installation of Jetpack:
    https://github.com/Automattic/jetpack/pull/7919

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Problems with the plugin’ is closed to new replies.