Fatal error: Attempt to modify property “queries” on null

  • Resolved gaiusjaugustus

    (@gaiusjaugustus)


    8 months ago

    My previous post was closed despite it not being resolved. Please don’t mark this as resolved until it is, so we can keep the conversation in one thread.

    I’m getting the following error on my website every hour or so while the plugin is active. When I deactivate the plugin, the error stops occurring.

    WordPress Version: 6.4.3
    ARMember Lite: 4.0.27

    Here’s the error and stack trace:

    PHP Fatal error Uncaught Error: Attempt to modify property “queries” on null in /…/wp-content/plugins/armember-membership/core/classes/class.arm_restriction.php:1220

    Stack trace:

    • #0 /…/wp-includes/class-wp-hook.php(324): ARM_restriction_Lite->arm_pre_get_posts(Object(WP_Query))
    • #1 /…/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(Object(WP_Query), Array)
    • #2 /…/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
    • #3 /…/wp-includes/class-wp-query.php(1881): do_action_ref_array(‘pre_get_posts’, Array)
    • #4 /…/wp-includes/class-wp-query.php(3824): WP_Query->get_posts()
    • #5 /…/wp-includes/class-wp.php(696): WP_Query->query(Array)
    • #6 /…/wp-includes/class-wp.php(816): WP->query_posts()
    • #7 /…/wp-includes/functions.php(1336): WP->main(”)
    • #8 /…/wp-blog-header.php(16): wp()
    • #9 /…/index.php(17): require(‘/home/gaiusjaug…’)
    • #10 {main}

    thrown in /…/wp-content/plugins/armember-membership/core/classes/class.arm_restriction.php on line 1220

    Thank you in advance for your help!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support dimplemodi

    (@dimplemodi)

    Hello,

    Kindly update ARMember Latest version 4.0.28 and let me know how it goes.

    Thanks

    Thread Starter gaiusjaugustus

    (@gaiusjaugustus)

    Thank you for the follow up.

    I updated my AR Member plugin to version 4.0.28. I also updated my site to WP 6.5 and ensured all my other plugins are up to date.

    The fatal PHP error has continued to occur every hour or two. Here are the times today I received an email indicating the error occurred: 1:34 AM, 3:34 AM, 5:33 AM, 7:34 AM, 9:33 AM, 11:33 AM, 1:33 PM, 2:42 PM, 4:05 PM, 5:34 PM, 7:33 PM, 9:33 PM. I have my site set up to notify me of every error, which has been fine up until this.

    The email from Fatal Error Notify always points to a request related to the blog: eg, /blog, /blog/feed/, /blog/page/2/. But when I visit the page, even with debugging on, I don’t see any errors on the page or in the console.

    Any ideas as to why this could be occurring or where the error is coming from?

    Plugin Support dimplemodi

    (@dimplemodi)

    Hello,

    I noticed that you are using the ARMember pro plugin. Please note that this forum is for the ARMember Lite only so due to forum limitations, I am unable to assist you with the ARMember pro related queries.

    Thanks

    Thread Starter gaiusjaugustus

    (@gaiusjaugustus)

    I am *not* using ARMember Pro. I’m currently using ARMember Lite. I stated this in my initial post, and nowhere in my posts did I indicate I was using Pro.

    Please answer my question……

    Any ideas as to why this could be occurring or where the error is coming from?

    I want to upgrade to Pro, but if I need to be able to trust the Lite version before committing to a purchase.

    Thread Starter gaiusjaugustus

    (@gaiusjaugustus)

    Updating for anyone who runs across this same error.

    I upgraded to Pro. When I installed the Pro plugin, the error went away.

    That shouldn’t be viewed as a solution, and should be reported to developers.

    Plugin Support dimplemodi

    (@dimplemodi)

    Hello,

    Thank you for reporting the issue.

    As far as your concern is regarding the ARMember Lite, I have checked at the local server and no such issue was found but still, I am passing this to the core team and if an issue is found then, it will be fixed!

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Fatal error: Attempt to modify property “queries” on null’ is closed to new replies.