• Resolved fooey

    (@fooey)


    Noticed that our error log is filling with these

    [02-Jun-2025 13:31:00 UTC] PHP Warning: Attempt to read property “post_title” on null in /home/site/public_html/wp-content/plugins/ays-popup-box/public/class-ays-pb-public.php on line 3196 [02-Jun-2025 13:31:00 UTC] PHP Warning: Attempt to read property “post_type” on null in /home/site/public_html/wp-content/plugins/ays-popup-box/public/class-ays-pb-public.php on line 3199

    Thousands of these. Please advise. We are using version 5.3.2

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

    (@hyenokian)

    Dear @fooey,

    Thanks for the topic.

    I want to mention that we tested this case with the version you mentioned, but didn’t get those warnings on our end.

    Could you please place the popup on a Test page and provide us with the link to it so we can take a closer look?
    Also, let us know if these warnings started appearing after updating to this version or if they were there before, too.

    Looking forward to hearing back from you.

    Thank you.

    Thread Starter fooey

    (@fooey)

    Yes,

    It was occurring prior to this release. We don’t currently have any pop-ups live, but there were two still active. They were date restricted. However, we were still getting the errors. I added one to a test page for you to review here so hopefully that helps. Thanks!

    Plugin Support Jasmine

    (@hyenokian)

    Dear @fooey,

    Thanks for the reply.

    Please let us know the following.
    Have you previously had a post where the popup was located, and then later you deleted that post?
    Or maybe you had a post that was included in the popup’s settings, and that post was later deleted or made private?

    These questions arise because the warning you’re seeing suggests that the popup is trying to load on a post but cannot find it.

    The warning:

    [02-Jun-2025 13:31:00 UTC] PHP Warning: Attempt to read property "post_title" on null in /home/site/public_html/wp-content/plugins/ays-popup-box/public/class-ays-pb-public.php on line 3196 [02-Jun-2025 13:31:00 UTC] PHP Warning: Attempt to read property "post_type" on null in /home/site/public_html/wp-content/plugins/ays-popup-box/public/class-ays-pb-public.php on line 3199

    In the screenshot below you can see the lines mentioned in the warning message:

    Could you let us know if this warning keeps appearing in your error log, or if it was just a one-time occurrence?

    If you remember which post it might have been, please share details about it.

    Looking forward to hearing back from you.

    Thank you.

    Thread Starter fooey

    (@fooey)

    It was not a one-time occurrence. The only pop-ups in the plugin were all assigned to the home page, pages, and test pop-up page (usually put here first to test), which is the url that was included in the last thread. None of the pop-ups are active/published, except for the one I reactivated for you to see the page so I don’t know why it is looking for anything. It seems odd that it would be trying to find a post to display on if it’s not published.

    My answers below:

    Have you previously had a post where the popup was located, and then later you deleted that post?

    Hard to say…I think that is a common scenario for any wordpress site and I cannot say for sure because I am not tracking the pages that we assign pop-ups to over any period of time. If the pop-up is not published, why is it actively looking to populate a page/post anyway?


    Or maybe you had a post that was included in the popup’s settings, and that post was later deleted or made private?

    Same answer as above.

    I just checked the error log and it’s starting to fill again. Thousands. It’s the only error in the log. Please advise.

    Plugin Support Jasmine

    (@hyenokian)

    Dear @fooey,

    Thanks for the reply.

    Apologies for the late response – we do not work on weekends.

    We’re sorry that this issue occurred, and we truly appreciate you bringing it to our attention.

    Our developers have reviewed the problem and were able to identify the cause. They will fix it in the upcoming update.

    In the meantime, please contact us via this form, so we can provide you with the fixed zip file as soon as possible.

    Looking forward to hearing back from you.

    Thank you.

    Plugin Support Jasmine

    (@hyenokian)

    For other readers, the customer contacted us via email, we provided the fixed zip file for the issue, and the problem was resolved.
    Also, we have included the fix in the latest update of the plugin (v5.3.5). You can update to the latest version and be sure the problem is resolved there.

    Dear @fooey,

    You can update to the latest version and check the fix there.

    Thank you.

    Thread Starter fooey

    (@fooey)

    thank you for your help, it solved the issue!

    Plugin Support Jasmine

    (@hyenokian)

    Dear @fooey,

    Thanks for the reply.

    Glad to hear that the problem has been fixed.

    If your query is resolved, please take a moment to rate and review the plugin or support.

    Thanks in advance!

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Filling error log’ is closed to new replies.