Backing out new theme update now. Will install on staging site for more information and continuation of troubleshooting.
Hello,
Please give more information about what plugins it is, if they are tested with the theme https://www.screencast.com/t/hO1cTSy0 what buttons it is about and widgets. if you can send us screenshots or contact us by email at contact@tagdiv.com and there give us the details.
Thank you!
Sorry for the delay. We’ve been troubleshooting many, many errors since 11.2 release. It breaks WooCommerce payments as well as a couple of other plugins.
I have contacted our hosting company, WPMU Dev. They indicate the theme breaks WooCommerce with a fatal error: Error: [09-Aug-2021 17:03:23 UTC] PHP Fatal error: Uncaught TypeError: Return value of WCPayMultiCurrencyMultiCurrency::get_enabled_currencies() must be of the type array, null returned in /var/web/site/public_html/wp-content/plugins/woocommerce-payments/includes/multi-currency/MultiCurrency.php:520
—
We’re going to start by reverting back to the previous version of Newspaper theme.
Critical error was a result of the WooCommerce payments plugin. It has been deactivated and removed.
We’re backing out the latest release of Newspaper theme. It has broken another website, builderspridecabinetry.com. It has moved the content up into the header. We’ll either need a fix for these problems, or we’ll be looking for another theme.
Screenshot: https://www.dropbox.com/s/3xwnv1f8r6l5zff/Screenshot%202021-08-17%2013.38.32.png?dl=0
In this particular case, the header template was changed from Header Template 30 to ‘none’. The fix was to change it back from ‘none’ to Header Template 30.
-
This reply was modified 4 years by
bob@mrrogersweborhood.com.
The header template was not manually changed to ‘none’. This must have happened during the Newspaper theme update.
Hi there.
Sorry for the lengthy delay. I finally found the offending plugin: Easy Updates Manager Premium: https://easyupdatesmanager.com/buy/
I’ve reported this to the plugin author, but am wondering what additional information I can provide them (or TagDiv) to fix the plugin conflict.
Thanks.
Bob