v2.1.0 causes errors

Resolved

(@efishinsea)

PHP Fatal error: Uncaught Error: Class "GTM4WP\Modules\EasyDigitalDownloads\EasyDigitalDownloadsModule" 
not found in /nas/content/live/wp-content/plugins/duracelltomi-google-tag-manager/src/Module/Registry.php:68

Stack trace:
	#0 /nas/content/live/wp-content/plugins/duracelltomi-google-tag-manager/src/Plugin.php(77): GTM4WP\Module\Registry::with_default_modules()
	#1 /nas/content/live/wp-content/plugins/duracelltomi-google-tag-manager/duracelltomi-google-tag-manager-for-wordpress.php(81): GTM4WP\Plugin->boot()
	#2 /nas/content/live/wp-includes/class-wp-hook.php(353): gtm4wp_bootstrap('')
	#3 /nas/content/live/wp-includes/class-wp-hook.php(377): WP_Hook->apply_filters(NULL, Array)
	#4 /nas/content/live/wp-includes/plugin.php(523): WP_Hook->do_action(Array)
	#5 /nas/content/live/wp-settings.php(630): do_action('plugins_loaded')
	#6 /nas/content/live/wp-config.php(120): require_once('/nas/content/li...')
	#7 /nas/content/live/wp-load.php(50): require_once('/nas/content/li...')
	#8 /nas/content/live/wp-blog-header.php(13): require_once('/nas/content/li...')
	#9 /nas/content/live/index.php(17): require('/nas/content/li...')
	#10 {main}
 thrown in /nas/content/live/wp-content/plugins/duracelltomi-google-tag-manager/src/Module/Registry.php on line 68

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

Erich
(@erichboileau)

14 hours, 22 minutes ago

Same issue.

An error of type E_ERROR was caused in line 68 of the file /nas/content/live/coastalcon/wp-content/plugins/duracelltomi-google-tag-manager/src/Module/Registry.php. Error message: Uncaught Error: Class "GTM4WP\Modules\EasyDigitalDownloads\EasyDigitalDownloadsModule" not found in /nas/content/live/coastalcon/wp-content/plugins/duracelltomi-google-tag-manager/src/Module/Registry.php:68 Stack trace: #0 /nas/content/live/coastalcon/wp-content/plugins/duracelltomi-google-tag-manager/src/Plugin.php(77): GTM4WP\Module\Registry::with_default_modules() #1 /nas/content/live/coastalcon/wp-content/plugins/duracelltomi-google-tag-manager/duracelltomi-google-tag-manager-for-wordpress.php(81): GTM4WP\Plugin->boot() #2 /nas/content/live/coastalcon/wp-includes/class-wp-hook.php(353): gtm4wp_bootstrap('') #3 /nas/content/live/coastalcon/wp-includes/class-wp-hook.php(377): WP_Hook->apply_filters(NULL, Array) #4 /nas/content/live/coastalcon/wp-includes/plugin.php(523): WP_Hook->do_action(Array) #5 /nas/content/live/coastalcon/wp-settings.php(630): do_action('plugins_loaded') #6 /nas/content/live/coastalcon/wp-config.php(118): require_once('/nas/content/li...') #7 /nas/content/live/coastalcon/wp-load.php(50): require_once('/nas/content/li...') #8 /nas/content/live/coastalcon/wp-login.php(12): require('/nas/content/li...') #9 {main} thrown

It’s taking my sites completely offline. Probably needs an immediate fix.

wigster
(@wigster)

13 hours, 25 minutes ago

Same error/issue, urgh — shame when this kind of site breaking issues slip the net!
PHP Fatal error: Uncaught Error: Class "GTM4WP\Modules\EasyDigitalDownloads\EasyDigitalDownloadsModule" not found

kotoedo
(@kotoedo)

13 hours, 16 minutes ago

Our support discovered the issue in duracelltomi-google-tag-manager/duracelltomi-google-tag-manager-for-wordpress.php. They said the fix required the full PHP name.

Uncaught Error: Class "GTM4WP\Modules\EasyDigitalDownloads\EasyDigitalDownloadsModule" not found in /nas/content/live/stgfacstaff/wp-content/plugins/duracelltomi-google-tag-manager/src/Module/Registry.php:68#012Stack trace:#012#0 /nas/content/live/stgfacstaff/wp-content/plugins/duracelltomi-google-tag-manager/src/Plugin.php(77): GTM4WP\Module\Registry::with_default_modules()#012#1 /nas/content/live/stgfacstaff/wp-content/plugins/duracelltomi-google-tag-manager/duracelltomi-google-tag-manager-for-wordp… GTM4WP\Plugin->boot()#012#2 /nas/content/live/stgfacstaff/wp-includes/class-wp-hook.php(353): gtm4wp_bootstrap('')#012#3 /nas/content/live/stgfacstaff/wp-includes/class-wp-hook.php(377): WP_Hook->apply_filters(NULL, Array)#012#4 /nas/content/live/stgfacstaff/wp-includes/plugin.php(523): WP_Hook->do_action(Array)#012#5 /nas/content/live/stgfacstaff/wp-settings.php(630): do_action('plugins_loaded')#012#6 /nas/content/live/stgfacstaff/wp-config.php(69): require_once('/nas/content/li...')#012#7 /nas/content/live/stgfacstaff/wp-load.php(50): require_once('/nas/content/li...')#012#8 /nas/content/live/stgfacstaff/wp-admin/admin.php(35): require_once('/nas/content/li...')#012#9 /nas/content/live/stgfacstaff/wp-admin/plugins.php(10): require_once('/nas/content/li...')#012#10 {main}#012 thrown in /nas/content/live/stgfacstaff/wp-content/plugins/duracelltomi-google-tag-manager/src/Module/Registry.php on line 68
dabeed
(@dabeed)

12 hours, 44 minutes ago
After I updated from 2.0.4 to 2.1.0, the site broke with WordPress’s “There has been a critical error on this website” message. The PHP error log shows this on every request:

PHP Fatal error: Uncaught Error: Class “GTM4WP\Modules\EasyDigitalDownloads\EasyDigitalDownloadsModule” not found in /wp-content/plugins/duracelltomi-google-tag-manager/src/Module/Registry.php:68
Stack trace: 0 /wp-content/plugins/duracelltomi-google-tag-manager/src/Plugin.php(77): GTM4WP\Module\Registry::with_default_modules() 1 /wp-content/plugins/duracelltomi-google-tag-manager/duracelltomi-google-tag-manager-for-wordpress.php(81): GTM4WP\Plugin->boot() 2 /wp-includes/class-wp-hook.php(353): gtm4wp_bootstrap(”)

… 5 /wp-settings.php(633): do_action(‘plugins_loaded’)

A forced clean reinstall of 2.1.0 (wp plugin install duracelltomi-google-tag-manager –version=2.1.0 –force) gives the same error, so this isn’t a partial update.

The src/Modules/ folder in the 2.1.0 package contains these folders: Amp, Blacklist, ClientDeviceData, ConsentMode, ContactForm7, Container, MediaEvents, PageVariables, UserEvents, VisitorData and WooCommerce. There is no EasyDigitalDownloads folder, but Registry.php line 68 registers that module by default. It looks like the folder was left out of the release.

Easy Digital Downloads is not installed on this site.

Rolling back to 2.0.4 fixes the site. I’m staying on 2.0.4 until a fixed release is out.
- This reply was modified 12 hours, 44 minutes ago by dabeed.
- This reply was modified 12 hours, 42 minutes ago by dabeed.
Plugin Author Thomas Geiger
(@duracelltomi)

12 hours, 9 minutes ago

Hi @efishinsea and everyone,

I am very sorry for this. It comes from a mistake I made while publishing the release.

My first commit of 2.1.0 to wordpress.org this morning left out the four module folders that are new in 2.1, Easy Digital Downloads among them. I corrected it ten minutes later, at 09:12 UTC, and the package on wordpress.org has been complete since shortly after that. I downloaded it again this evening to be sure. The folder list that @dabeed posted matches that first commit exactly, so your sites received the early copy and not the current one.

The paths in your error logs look like WP Engine. As far as I know, WP Engine serves plugin updates from its own mirror of wordpress.org by default, so my assumption is that the mirror picked up the package during those few minutes and still hands it out. I have not been able to confirm this yet. If your site is not hosted on WP Engine, please tell me here, because that would change the picture.

To bring a site back, delete or rename the folder wp-content/plugins/duracelltomi-google-tag-manager over (S)FTP. This stops the error and your settings stay in the database. Then install GTM4WP 2.1.1, which I have just released for this. It is the same code as 2.1.0 in a complete package, and because its download address is new, it cannot come from an old copy. Download it directly from wordpress.org and install it with Plugins, Add New, Upload Plugin:

https://downloads.wordpress.org/plugin/duracelltomi-google-tag-manager.2.1.1.zip

With WP-CLI, passing that URL to wp plugin install with --force --skip-plugins does the same. No change to the plugin’s PHP code is needed.

wordpress.org holds a new release back from the dashboard for about six hours for its security review, so wp-admin can keep offering 2.1.0 until then. If you are on WP Engine, please do not take that update on your other sites, and please ask their support to refresh their copy of this plugin, since the next site can receive the same package until that happens.

I will post here as soon as I know more.

Severisth
(@severisth)

11 hours, 57 minutes ago

This fix worked.

My site on WP Engine did also go down. Looking at logs > errors in WP Engine dashboard showed it was this plugin. I connected to the site via SFTP and renamed the plugin folder to “duracelltomi-google-tag-manager-OLD” which disabled the plugin instantly and brought the website back online. I then went to Plugins in WordPress and uploaded the ZIP for the new version of the plugin. It picked up the same settings as before, as far as I can tell, and everything is now working.

Plugin Author Thomas Geiger
(@duracelltomi)

11 hours, 32 minutes ago

Hi @severisth,

Thank you for confirming this, and for writing down the steps you took, because they will help the next person who lands on this topic. I am glad that your site is back, and I am sorry that it went down in the first place.

You can now delete the folder that ends in -OLD. It still holds the incomplete copy, and WordPress lists it as a second plugin, so activating it by mistake would bring the error back.

I have asked WP Engine to check their copy of the plugin. I will post here when I hear back from them, and when 2.1.1 reaches the dashboard update. If anyone here is still stuck, please let me know and I am happy to help.

dabeed
(@dabeed)

11 hours, 28 minutes ago

2.1.1 worked for me too. This site is on Flywheel (WP Engine). To avoid the out of date mirror, I updated from wordpress.org:

wp plugin install https://downloads.wordpress.org/plugin/duracelltomi-google-tag-manager.2.1.1.zip –force –skip-plugins –skip-themes

All seems good now. Thank you!

kotoedo
(@kotoedo)

11 hours, 16 minutes ago

Thank you, Thomas! The update to v2.1.1 worked.
Plugin Author Thomas Geiger
(@duracelltomi)

10 hours, 57 minutes ago
Hi @dabeed and @kotoedo,

Thank you both for confirming that 2.1.1 works, and thank you @dabeed for sharing the WP-CLI route. The forum changed the dashes in that command, so here is a clean copy for anyone who needs it:
```
wp plugin install https://downloads.wordpress.org/plugin/duracelltomi-google-tag-manager.2.1.1.zip --force --skip-plugins --skip-themes
```
One warning for everyone who deactivated the plugin to bring a site back: please do not use the Delete link on the Plugins screen, because that also removes the plugin’s settings, including the container ID. Upload the new version instead, and select “Replace current with uploaded” when WordPress asks.
Thread Starter e dev
(@efishinsea)

8 hours, 44 minutes ago

fixed

deirdrej10940
(@deirdrej10940)

7 hours, 44 minutes ago

Site went down earlier, did the fix. Working fine now. Thank you for doing this so quickly.

Plugin Author Thomas Geiger
(@duracelltomi)

4 minutes ago

Hi @efishinsea, @deirdrej10940 and everyone,

Thank you for confirming that your sites are working again.

wordpress.org now offers 2.1.1 as a normal update in the dashboard, so a site where you deactivated the plugin can take it from the Plugins screen, and you can then activate the plugin. Please check that the screen shows 2.1.1 before you click Update. On WP Engine the update comes through their mirror by default, and I cannot see that from my side, so it can appear later there. If a site still offers 2.1.0, please do not take that update, and upload the 2.1.1 ZIP as described above instead.

A site that shows the error on every page has no working wp-admin, so it still needs the manual steps from my first reply.

I have not heard back from WP Engine yet. I will post here when I do.

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

You must be logged in to reply to this topic.

Tags