Fatal Error after updated to v1.12.2

  • Resolved cheey2003

    (@cheey2003)


    2 years ago

    Hi there,

    My WooCommerce site encountered the following fatal error after updated the plugin to v1.12.2 from v12.2.1 which caused the entire WP Admin area inaccessible and required me to manually delete the plugin files in order to restore access.

    The log file revealed the following error message:

    2022-04-05T16:31:15+00:00 CRITICAL Uncaught Error: Cannot unset string offsets in /home/instance-name/dusun.com.my/public/wp-content/plugins/google-listings-and-ads/src/DB/Migration/Migration20211228T1640692399.php:75
Stack trace:
#0 /home/instance-name/dusun.com.my/public/wp-content/plugins/google-listings-and-ads/src/DB/Migration/Migrator.php(47): Automattic\WooCommerce\GoogleListingsAndAds\DB\Migration\Migration20211228T1640692399->apply()
#1 /home/instance-name/dusun.com.my/public/wp-content/plugins/google-listings-and-ads/src/DB/Installer.php(53): Automattic\WooCommerce\GoogleListingsAndAds\DB\Migration\Migrator->migrate()
#2 /home/instance-name/dusun.com.my/public/wp-content/plugins/google-listings-and-ads/src/Installer.php(103): Automattic\WooCommerce\GoogleListingsAndAds\DB\Installer->install()
#3 /home/instance-name/dusun.com.my/public/wp-content/plugins/google-listings-and-ads/src/Installer.php(83): Automattic\WooCommerce\GoogleListingsAndAds\Installer->install()
#4 /home/instance-name/dusun.com.my/public/wp-content/plugins/google-listings-and-a in /home/instance-name/dusun.com.my/public/wp-content/plugins/google-listings-and-ads/src/DB/Migration/Migration20211228T1640692399.php on line 75

    May I know what should I do to proceed?

Viewing 3 replies - 1 through 3 (of 3 total)
  • leedman

    (@leedman)

    2 years ago

    I had the same and had to roll back to 1.12.1 to get the site working again.

    Please let me know when it’s fixed.

    Thanks

    omesie

    (@omesie)

    2 years ago

    Same issue.

    Plugin Author Jason a11n

    (@jconroy)

    2 years ago

    Hi @cheey2003 and others,

    Sorry for the difficulties – thanks for reporting. The team is working on getting our a fix asap.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal Error after updated to v1.12.2’ is closed to new replies.