Version 4.4.3+ Causes Fatal Error with Google Site Kit 1.98.0

  • Resolved Tim Nolte

    (@tnolte)


    1 year, 7 months ago

    I am seeing sites dying with a fatal error in cases where this plugin is version 4.4.3 and newer along with the 1.98.0 version of the Google Site Kit plugin.

    [14-Apr-2023 05:16:29 UTC] PHP Warning:  require_once(/var/www/html/web/wp-content/plugins/google-site-kit/third-party/vendor/composer/InstalledVersions.php): Failed to open stream: No such file or directory in /var/www/html/web/wp-content/plugins/google-site-kit/includes/loader.php on line 34
[14-Apr-2023 05:16:29 UTC] PHP Fatal error:  Uncaught Error: Failed opening required '/var/www/html/web/wp-content/plugins/google-site-kit/third-party/vendor/composer/InstalledVersions.php' (include_path='.:/usr/share/php') in /var/www/html/web/wp-content/plugins/google-site-kit/includes/loader.php:34
Stack trace:
#0 [internal function]: Google\Site_Kit\{closure}('Composer\\Instal...')
#1 /var/www/html/web/wp-content/plugins/wp-security-audit-log/classes/Helpers/class-classes-helper.php(102): is_subclass_of('Composer\\Instal...', '\\WSAL_AbstractV...')
#2 /var/www/html/web/wp-content/plugins/wp-security-audit-log/classes/ViewManager.php(105): WSAL\Helpers\Classes_Helper::get_subclasses_of_class('WSAL_Views_Audi...', '\\WSAL_AbstractV...')
#3 /var/www/html/web/wp-content/plugins/wp-security-audit-log/wp-security-audit-log.php(847): WSAL_ViewManager->__construct(Object(WpSecurityAuditLog))
#4 /var/www/html/web/wp-content/plugins/wp-security-audit-log/wp-security-audit-log.php(343): WpSecurityAuditLog->init()

    Downgrading Google Site Kit to version 1.96.0 works with the latest version of WP Activity Log or downgrading WP Activity Log to version 4.4.2 works with the latest version 1.98.0 of Google Site Kit.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Tim Nolte

    (@tnolte)

    Cross linking reported issue: https://www.ads-software.com/support/topic/version-1-98-0-causes-fatal-error-with-wp-activity-log-4-4-3/

    Plugin Support robertabela

    (@robert681)

    Thank you for posting this and for using our plugin @tnolte

    I am sorry to read about your issue. This is happening because the Google Site Kit plugin uses an older version of composer. That plugin loads before ours (because of the name, our starts with w) so when Composer loads from our plugin, there is a conflict because our plugin uses the latest one.

    As a temporary solution, until they update their plugin, you can copy the file InstalledVersions.php from our plugin in the Google Site Kit. So copy the file from here:

    wp-content/plugins/wp-security-audit-log/vendor/composer/InstalledVersions.php

    to:

    wp-content/plugins/google-site-kit/third-party/vendor/composer/

    I hope the above helps. Should you have any more questions please do not hesitate to ask.

    Have a great day.

    Thread Starter Tim Nolte

    (@tnolte)

    Plugins are all installed via Composer so simply copying files is not quite that simple. I can possible look at trying to do a Composer patch but that might be tricky since we are talking about the new for placing an entire file and not just patching the code in an existing file.

    Plugin Support robertabela

    (@robert681)

    I understand that @tnolte

    If you have any feedback / recommendation on how we should handle this from our side please let us know because at the moment, from what we see, we can’t do much from our end.

    Thread Starter Tim Nolte

    (@tnolte)

    @robert681 I’m pretty sure it has additionally been confirmed by the Google Site Kit developers that that is an issue on their side. There shouldn’t be anything that you need to do. I’m marking this as resolved.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Version 4.4.3+ Causes Fatal Error with Google Site Kit 1.98.0’ is closed to new replies.