Error with PHP Upgrade

  • Resolved fkildoo

    (@fkildoo)


    6 months, 2 weeks ago

    After upgrading PHP from 7.4.33 to 8.3.7 I get an error at the top of the page:

    Warning: Attempt to read property “ID” on null in
    … /wp-content/plugins/content-control/inc/functions/rule-callbacks.php on line 88

    Using:
    Plugin version 2.2.8
    WordPress version: 6.5.3

    I have downgraded PHP to go back to normal.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Kim L

    (@kimmyx)

    Hi @fkildoo,

    Sorry to hear you encountered an error after upgraded your PHP version.

    Did you have existing restriction rules before you upgraded?

    If yes, could you please try the following:

    Export the rules first > then delete the rules > upgrade your PHP > and re-import your exported restriction rules.

    You can also recreate your rules and then deleted the old ones that were created before you upgraded.

    Let us know if that works!

    Thread Starter fkildoo

    (@fkildoo)

    That did not work. I am getting the same error. I had 1 rule set up, so I did what you suggested. I exported then deleted the rule (permanently), upgraded PHP, then reimported the rule. Same issue. I then deleted the rule (permanently), and then recreated the rule from scratch. The rule redirects 1 user role to a custom URL, from the home and search results page. I have reverted back to PHP 7.

    Plugin Support Kim L

    (@kimmyx)

    Hi @fkildoo,

    Thanks for trying our suggestion.

    Could you send us a screenshot of your restriction rules? We’ll try to reproduce it on our test site.

    We appreciate your continued patience. ??

    Thread Starter fkildoo

    (@fkildoo)

    Thank you. Here are the screenshots:

    Plugin Support Kim L

    (@kimmyx)

    Hi @fkildoo,

    Thanks for the screenshots!

    We were able to reproduce the warning when the restriction “Content is The Home Page” is added.

    We’ve informed our developers about this so they can take a look.

    We’ll let you know once we receive feedback.

    Let us know if you have other questions in the meantime. ??

    Plugin Author Daniel Iser

    (@danieliser)

    @fkildoo – Please test v2.3.0. I believe it may solve this particular issue.

    Thread Starter fkildoo

    (@fkildoo)

    Working well now with v2.3.0. Thanks Daniel!

    Hi @fkildoo ,

    We’re glad that helped.

    Please don’t hesitate to reach out if you need more assistance.

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