Fatal Flaw. Has caused server to hang. Crashes when using php 8.4 WHM and all Cpanel Accounts.

[mykkal]

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.8.2
Active theme: Hello Elementor (version 3.4.4)
Current plugin: GTM4WP - A Google Tag Manager (GTM) plugin for WordPress (version 1.21.1)
PHP version 8.4.10

Error Details

An error of type E_ERROR was caused in line 154 of the file /home/ironpalm/public_html/wp-content/plugins/duracelltomi-google-tag-manager/admin/admin-tab-integrate.php. Error message: Uncaught Error: Undefined constant "GTM4WP_OPTION_INTEGRATE_WCDLMAXTIMEOUT" in /home/ironpalm/public_html/wp-content/plugins/duracelltomi-google-tag-manager/admin/admin-tab-integrate.php:154
Stack trace:
#0 /home/ironpalm/public_html/wp-content/plugins/duracelltomi-google-tag-manager/admin/admin.php(706): require_once()
#1 /home/ironpalm/public_html/wp-includes/class-wp-hook.php(324): gtm4wp_admin_init('')
#2 /home/ironpalm/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#3 /home/ironpalm/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#4 /home/ironpalm/public_html/wp-admin/admin-ajax.php(45): do_action('admin_init')
#5 {main}
thrown

[mykkal]

I've had to disable the plugin. THat's an issue because we run ads. But it keeps throwing fatal flaw after fatal flaw.

[mykkal]

any updates?

[duracelltomi]

Are you the same person who reported the same on the WP.org forum?
https://wordpress.org/support/topic/error-on-last-update-8/

[mykkal]

No i'm a different person. I noticed that. I actually don't have an account on wordpress.org. I was banned by Jan Dembrowski. He's a well known bully. So there's multiples of us having the issue -- Mike McKoy 770-203-8805

…

On Fri, Aug 29, 2025 at 9:55 AM Thomas Geiger ***@***.***> wrote: *duracelltomi* left a comment (duracelltomi/gtm4wp#414) <#414 (comment)> Are you the same person who reported the same on the WP.org forum? https://wordpress.org/support/topic/error-on-last-update-8/ — Reply to this email directly, view it on GitHub <#414 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A456OIIJMEGAKFKU4KMBOYD3QBLWJAVCNFSM6AAAAACE57QYVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZXGEZDMOJVGI> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[mykkal]

Has this issue been resolved? I accidentally closed the ticket but I don't want to renable and crash the server. I also need to use it! -- Mike McKoy 770-203-8805

…

On Fri, Aug 29, 2025 at 12:04 PM Mike McKoy ***@***.***> wrote: No i'm a different person. I noticed that. I actually don't have an account on wordpress.org. I was banned by Jan Dembrowski. He's a well known bully. So there's multiples of us having the issue -- Mike McKoy 770-203-8805 On Fri, Aug 29, 2025 at 9:55 AM Thomas Geiger ***@***.***> wrote: > *duracelltomi* left a comment (duracelltomi/gtm4wp#414) > <#414 (comment)> > > Are you the same person who reported the same on the WP.org forum? > https://wordpress.org/support/topic/error-on-last-update-8/ > > — > Reply to this email directly, view it on GitHub > <#414 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A456OIIJMEGAKFKU4KMBOYD3QBLWJAVCNFSM6AAAAACE57QYVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZXGEZDMOJVGI> > . > You are receiving this because you modified the open/close state.Message > ID: ***@***.***> >

[duracelltomi]

I was not able to identify any root cause, on sites where I have updated the plugin, this error never happened

[mykkal]

I can give you access to our site. and others are still reporting it in your forums. they are also reporting problems with event tracking. We definitely have the problem.

…

-- Mike McKoy 770-203-8805

On Fri, Sep 5, 2025, 10:31 AM Thomas Geiger ***@***.***> wrote: *duracelltomi* left a comment (duracelltomi/gtm4wp#414) <#414 (comment)> I was not able to identify any root cause, on sites where I have updated the plugin, this error never happened — Reply to this email directly, view it on GitHub <#414 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A456OIMA2LM4YA6A75LWLIL3RGNE7AVCNFSM6AAAAACE57QYVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJYGU3DSNZTGM> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[mykkal]

Okay you're deflecting. The problem is real and the code could be written better but you won't acknowledge it. Multiple people have told us they've emailed, posted in the wordpress forums, and on github. But you're not acknowledging any of us, including those of us that literally had the same exact error and had a server you could test on. We're going to redo everything by hand with GTM (the actual google product). You need to rethink building and supporting a product to this scale... You don't seem to have the will to be comprehensive nor the ability to quality assure what you've built in actual production environments. Good luck in the future. I don't not think being an independent development company is a good idea for you going forward. -- Mike McKoy 770-203-8805

…

On Fri, Sep 5, 2025 at 11:46 AM Mike McKoy ***@***.***> wrote: I can give you access to our site. and others are still reporting it in your forums. they are also reporting problems with event tracking. We definitely have the problem. -- Mike McKoy 770-203-8805 On Fri, Sep 5, 2025, 10:31 AM Thomas Geiger ***@***.***> wrote: > *duracelltomi* left a comment (duracelltomi/gtm4wp#414) > <#414 (comment)> > > I was not able to identify any root cause, on sites where I have updated > the plugin, this error never happened > > — > Reply to this email directly, view it on GitHub > <#414 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A456OIMA2LM4YA6A75LWLIL3RGNE7AVCNFSM6AAAAACE57QYVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJYGU3DSNZTGM> > . > You are receiving this because you modified the open/close state.Message > ID: ***@***.***> >

[morvy]

@mykkal if the code could be written better, create a pull request. If there is an issue, report it, provide steps to replicate. If you can't code and can't help, just stop using the product and move along.. insulting a developer is the least probable way of getting things fixed

[mykkal]

oh we can definitely code and help. It's just obvious from your statement that you're passing the buck. We aren't the only ones that offered you a chance to see the environment. You literally don't want to sir and that's why I suggested you should not pursue being a development company. Best of luck to you

…

-- Mike McKoy 770-203-8805

On Sun, Sep 7, 2025, 10:04 AM morvy ***@***.***> wrote: *morvy* left a comment (duracelltomi/gtm4wp#414) <#414 (comment)> @mykkal <https://github.com/mykkal> if the code could be written better, create a pull request. If there is an issue, report it, provide steps to replicate. If you can't code and can't help, just stop using the product and move along.. insulting a developer is the least probable way of getting things fixed — Reply to this email directly, view it on GitHub <#414 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A456OIKOZQZD44VBMWWCUOD3RQ3ODAVCNFSM6AAAAACE57QYVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENRTG44TSNRQHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[morvy]

@mykkal I'm not the author of the plugin, but when I needed something to fix and provided PR it was accepted. Maybe if you just fix something you believe is not OK, provide PR and comment without hating everything around, it would've been accepted in no time..

[mykkal]

This is wisdom not hate. When the developer says they can't reproduce and there is nothing wrong after being offered a look into the environment multiple organizations have quoted the same error for it reflects quality and work ethic. He dismissed it twice when I offered assistance. So therefore, let his QA stay at its current level and he can continue denying that flaw until those medium and enterprise sites leave him. That's the proper evolution of things. We'll enter our tags by hand...The problem he's having will 'fix' itself via another more reliable plugin. Works every time.

…

-- Mike McKoy 770-203-8805

On Sun, Sep 7, 2025 at 10:46 AM morvy ***@***.***> wrote: *morvy* left a comment (duracelltomi/gtm4wp#414) <#414 (comment)> @mykkal <https://github.com/mykkal> I'm not the author of the plugin, but when I needed something to fix and provided PR it was accepted. Maybe if you just fix something you believe is not OK, provide PR and comment without hating everything around, it would've been accepted in no time.. — Reply to this email directly, view it on GitHub <#414 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A456OIIMQN46DCVXGNYAGAL3RRALVAVCNFSM6AAAAACE57QYVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENRTHAZDKMBVGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[duracelltomi]

Let me add my thoughts:

This is an open source project. I am doing this in my free time. I hear your frustration, but I need to be firm: I can't replicate the issue you've described on my end. WP's forum is just not suitable to manage tickets. I was warned by admins that asking or accepting for credentials is againts the forum rules the repo could be banned from the directory.

As mentioned earlier, The best way you can help me is to provide exact steps to reproduce the issue and any relevant code snippets that might fix it.

I'm currently testing a pull request for a different tracking issue and hope to release an update soon. However, each new version requires careful testing to prevent problems on other sites. I also hope I (we) can find the cause of this issue soon.