Deprecated JS call and critical site-health message

  • Resolved Michael

    (@mitfi)


    4 years, 7 months ago

    Dear Support Team

    Thanks for the plugin!

    Two topics I ran over:

    1. From the WordPress “Enable jQuery Migrate Helper” plugin, I receive the following message:
    “/wp-content/plugins/insert-php/libs/factory/feedback/assets/js/deactivate-feedback.js: jQuery.fn.load() is deprecated“.
    Is this a correct statement and are you going to correct this?

    2. Despite having your plugin active and everything working with no real issues to be seen, I get the following ?critical“ message on the site-health page:
    “Active PHP Session encountered”, with some remarks about potentially associated REST-API and Loopback issues.
    Is it normal that your plugin won’t prevent that message?

    Thanks in advance for talking your time to support this inquiry.

    Best regards

    Michael

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Michael

    (@mitfi)

    Dear all,

    Point 1. above does not refer to this plug-in, sorry, this was my fault!

    However, Point 2 above still remains.

    Thanks a lot in advance!

    Best regards

    Michael

    Plugin Author Daniel Bachhuber

    (@danielbachhuber)

    Hi @mitfi,

    Despite having your plugin active and everything working with no real issues to be seen, I get the following ?critical“ message on the site-health page:
    “Active PHP Session encountered”, with some remarks about potentially associated REST-API and Loopback issues.
    Is it normal that your plugin won’t prevent that message?

    WP Native PHP Sessions moves PHP session data from the filesystem to the database (which is helpful if your site runs on multiple web servers). It doesn’t manage anything about the use of PHP sessions themselves. There’s likely a plugin or some custom code starting a PHP session without closing it, which isn’t anything WP Native PHP Sessions would handle.

    Here’s the Core Trac ticket where this particular Site Health check was added. You can read through it for more details on the nature of the check.

    To resolve the issue, you’ll need to track down the plugin, plugins, or custom code that’s starting a PHP session without closing it. If it’s an actively maintained plugin, I think you can safely ignore the warning until the plugin author pushes an update with the fix. But, if it’s custom code or an abandoned plugin, you might need to do some fixing on your own.

    Hope this helps.

    Thread Starter Michael

    (@mitfi)

    Hi @danielbachhuber,

    thanks a lot for your explanations, which made me better understand the PHP SESSION concept and how “WordPress Native PHP Sessions” deals with it!

    I could identify and eliminate the source of the issue.

    Thanks again for your fast and precise response and of course thanks a lot for your time!

    Best regards

    Michael

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Deprecated JS call and critical site-health message’ is closed to new replies.