• Resolved hollywoodonlocation

    (@hollywoodonlocation)


    I deactivated then reactivated Shield Security and now on my users page there is a string of codes.

    Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home1/thebroad/public_html/sensitivityreviews/wp-content/plugins/wp-simple-firewall/src/lib/src/Modules/Plugin/Processor.php on line 186

    This is from Shield’s Firewall. Do I need to disable the firewall to get rid of these errors? If so, how do I do that?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter hollywoodonlocation

    (@hollywoodonlocation)

    PS Also having other errors on other pages now. Now sure if it is related or not.

    Plugin Support Jelena

    (@jmisic)

    Hi,

    These are just PHP Deprecated notices and cause no harm or actual errors on your site. This is just an artifact from support a large range of PHP versions and ensuring there’s a compatible library.

    You probably shouldn’t be logging these on a production site. The best thing you can do here is configuring your PHP logging to not log Deprecation notices and here’s how to do that:
    https://stackoverflow.com/questions/5628148/disable-e-deprecated-in-php-error-log#answer-5651783

    We’ll also definitely review them and try to eliminate them for future releases.

    If you’re getting other types of errors aside from deprecated ones, feel free to share them.

    Thanks.

    Plugin Author Paul

    (@paultgoodchild)

    Deprecated notifications are part of PHP, and you’ll see them in greater numbers when you run higher versions of PHP.

    They aren’t errors, but just notices to say that in future versions of PHP, they will likely generate errors.

    You shouldn’t be displaying PHP Deprecation notices on a live WordPress site. Deprecations don’t cause problems and they don’t impact your site in any way… unless you display them on the website. That output may interfere with other processes, such as sending headers/cookies, perhaps as you’re alluding to when you say it’s causing other “errors” on other pages.

    The solution is to not display deprecation notices, or errors, on a public, live website. We have an article on our site that outlines steps you can take to prevent PHP notices being displayed. There are many resources for this sort of thing if you want to find alternatives or perhaps options for your particularly web hosting setup. Here are some:

    I hope this helps.

    Thread Starter hollywoodonlocation

    (@hollywoodonlocation)

    This is an issue. When I log in to see users there are about 20 strings of this error. Unable to follow your instructions above as it is too technical/complicated for me. Why does this require CODING to remove the errors? Any other ways to remove?

    Thank you.

    PS Tried to remove the string in this conversation per your suggestion, but can no longer edit it.

    Plugin Author Paul

    (@paultgoodchild)

    You may need to discuss this forum post with your host so that they configure your webhosting to not display errors. Either you need to do it, or your webhost needs to do it, or you’ll need to engage with someone with the know-how to make such changes.

    What we outlined is standard practice on a WordPress site – never display errors/warnings on a public site. Coding is required because this is how WordPress sites operate.

    Thread Starter hollywoodonlocation

    (@hollywoodonlocation)

    Why is this all of a sudden a problem? Is it the update to the plugin that caused this? Have been using for a long time without these issues.

    Plugin Author Paul

    (@paultgoodchild)

    We develop and release updates regularly, sometimes there are issues that pop up – it’s the nature of software development. We’ll have mitigation for this deprecation warning in our next release.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.