• Resolved Rosso Digital

    (@roberthemsing)


    When Companion Auto-Update and Google Site Kit are both active on the page we’re getting the following error notice in the admin backend:

    Notice: Undefined property: stdClass::$slug in /home/customer/www/[domain redacted]/public_html/wp-content/plugins/companion-auto-update/cau_functions.php on line 989

    The line it is referring to is:

    if ( in_array( $item->slug, $plugins ) ) {

    We’ve already reported this conflict to the Companion Auto-Update developers as well but we’ve also identified a conflict between Google Site Kit and Support Genix which triggers a different admin error notice so it seems that Google Site Kit might be the culprit here?

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

    (@jamesosborne)

    Thanks for reaching out @roberthemsing. We are currently working on removing deprecated dynamic property declarations, and once complete you won’t encounter such warnings. See below:
    https://github.com/google/site-kit-wp/issues/7202

    We expect this to be complete soon, with Site Kit releasing a new version every 2 weeks. With regards this appearing within the wp-admin panel, do you have PHP error reporting enabled? I’ll test this out myself to ensure there is no loss in Site Kit functionality, I expect all should work as expected, even with the warning printed.

    Thread Starter Rosso Digital

    (@roberthemsing)

    Hi @jamesosborne, yes we have debug logging and the debug display enabled as it’s a brand-new site and we wanted to be aware of any issues before we hand it over to the client. If you’re confident that there is no loss in functionality we will disable the logging and notice.

    Plugin Support James Osborne

    (@jamesosborne)

    Good idea to enable debugging and displaying errors @roberthemsing. You are also correct, I’m confident that the errors output don’t result in any loss of Site Kit functionality. I can keep this open if you wish, in order to inform you once the related GitHub issue has been resolved, at which point no errors will appear with debugging enabled.

    One other thing to note is that some of these errors are only output as of PHP8.2+. If you select a lower version many such errors or warnings won’t be classified as such.

    Thread Starter Rosso Digital

    (@roberthemsing)

    Hi @jamesosborne – the site runs on php version 7.4.33. If you could keep this ticket open and keep us updated on the progress that’d be great.

    Plugin Support James Osborne

    (@jamesosborne)

    Not a problem @roberthemsing. I’ll do that.

    Plugin Support James Osborne

    (@jamesosborne)

    @roberthemsing Just to let you know that we’ve released a fix for this issue which you identified. Can you update to the latest version of Site Kit and confirm all works as expected?

    Thread Starter Rosso Digital

    (@roberthemsing)

    @jamesosborne the issue seems to be resolved 🙂

    Plugin Support James Osborne

    (@jamesosborne)

    Glad to hear it @roberthemsing, and appreciate the follow up. If you run into any further issues, you know where to find us.

    As it also sounds like you’ve been a Site Kit user for some time, be sure to share your thoughts on the plugin so far.

    Best of luck.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Conflict with Auto-Update Companion’ is closed to new replies.