Fatal Error: Google Drive

  • Resolved moonmaker

    (@moonmaker)


    1 month ago

    When I open wordpress I am greeted with the error below. It does not let me look at the plugin or change any settings on the site, this error is the only thing that shows up. It only will show the following error and the option to upgrade to WordPress to 6.6.2 but I am scared to do so as it might cause further issue. This is on the staging site and the production site still functions as needed. I think it is due to the Google drive backup being connected to an old account but how can I change it if the settings won’t load? Please advise asap, I cannot make updates to the site while this is happening.

    Would it help to upload the backup from production over the staging site? I don’t know how to as all I can see on the staging site is the error.

    Error: Fatal error: Uncaught TypeError: property_exists(): Argument #1 ($object_or_class) must be of type object|string, null given in /var/www/html/staging/wp-content/plugins/wp-staging-pro/Pro/Backup/Storage/Storages/GoogleDrive/Auth.php:412 Stack trace: #0 /var/www/html/staging/wp-content/plugins/wp-staging-pro/Pro/Backup/Storage/Storages/GoogleDrive/Auth.php(412): property_exists(NULL, ‘success’) #1 /var/www/html/staging/wp-content/plugins/wp-staging-pro/Pro/Backup/Storage/Storages/GoogleDrive/Auth.php(253): WPStaging\Pro\Backup\Storage\Storages\GoogleDrive\Auth->refreshAccessTokenRemotely(‘1//06q_wy63P1JN…’) #2 /var/www/html/staging/wp-content/plugins/wp-staging-pro/Pro/Backup/Storage/StoragesServiceProvider.php(80): WPStaging\Pro\Backup\Storage\Storages\GoogleDrive\Auth->setClientWithAuthToken() #3 /var/www/html/staging/wp-content/plugins/wp-staging-pro/vendor_wpstg/lucatume/di52/src/tad/DI52/Container.php(248): WPStaging\Pro\Backup\Storage\StoragesServiceProvider->WPStaging\Pro\Backup\Storage\{closure}(Object(WPStaging\Framework\DI\Container)) #4 /var/www/html/staging/wp-content/plugins/wp-staging-pro/Framework/DI/Container.php(73): WPStaging\Vendor\tad_DI52_Container->make(‘WPStaging\\Pro\\B…’) #5 /var/www/html/staging/wp-content/plugins/wp-staging-pro/vendor_wpstg/lucatume/di52/src/tad/DI52/closuresSupport.php(31): WPStaging\Framework\DI\Container->make(‘WPStaging\\Pro\\B…’) #6 /var/www/html/staging/wp-includes/class-wp-hook.php(322): WPStaging\Vendor\{closure}() #7 /var/www/html/staging/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #8 /var/www/html/staging/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #9 /var/www/html/staging/wp-admin/admin-header.php(311): do_action(‘all_admin_notic…’) #10 /var/www/html/staging/wp-admin/index.php(137): require_once(‘/var/www/html/s…’) #11 {main} thrown in?/var/www/html/staging/wp-content/plugins/wp-staging-pro/Pro/Backup/Storage/Storages/GoogleDrive/Auth.php?on line?412

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

  • Hello @moonmaker

    Thanks for reporting us the issue. We are already aware of this issue and it’s our highest priority right now. Our engineers are working on it and we hope to fix it very soon.
    I will let you know once we resolve this issue.

    Thanks again,
    Cheers

    Plugin Author Rene Hermenau

    (@renehermi)

    @moonmaker

    We’ve just fixed this issue in latest version. Please update to free 3.9 or 5.9.

    Thank you
    René

    Thread Starter moonmaker

    (@moonmaker)

    Hi @renehermi and @voboghure,

    Thank you for the follow up. Any suggestions on how to update it as all I see is the fatal error, even when I select the plugin or WP Staging from the menu. In other words, I do not have the option to update.

    -Moonmaker

    Plugin Contributor alaasalama

    (@alaasalama)

    @moonmaker you can uninstall the plugin from the plugins page and install it again.

    Thread Starter moonmaker

    (@moonmaker)

    @alaasalama I am not able to access the plugin page due to the fatal error. When I click on the Plugins option from the menu it only shows the fatal error and does not give me the option to update it.

    Plugin Contributor alaasalama

    (@alaasalama)

    @moonmaker you can delete the whole plugin folder from “/wp-content/plugins/” via FTP, then install the recent version of the plugin again.

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