WPIntell

Source evidence

Uninstall is not clean ?

WP BrowserUpdate · support · 2025-03-25T19:09:00+00:00

mixedsentiment
mediumseverity
0.85relevance
11replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 34 rows with source links

11.8% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
ecollart resolved
Hello, I uninstalled once your plugin and a test made a few weeks later on Google PageSpeed still reports presence of your code on my homepage <a href="https://browserupdate.org/" rel="noopener" onclick="javascript:window.open('https://browserupdate.org/', '_blank', 'noopener')…" data-wahfont="12"> I then re-install it to check if there is any setting to check to remove any trace completely but I found none. Can you tell me how to completely uninstall if I ever want to test that again ? Thanks for your help Eric Collart The page I need help with: [ log in to see the link] Hi Eric, Do me a favour and check if you have a plugin called Cookie Law Info enabled. Disable it and see if the artefact disappears. Report back here. The plugin itself definitely removes itself from the WordPress database but it will not remove any code that has been placed by another party. Hello, thanks a lot for your quick reply. I use a plugin for GDPR named CookieYes but Cookie Law Info could be the previous name of the plugin… I will check this when time permits and let you know the result here Eric Collart Any chance you ran a test in the past two weeks? Otherwise, I’m going to set this issue to resolved. Hello, not yet but planning this for late evening today (Belgian time); sorry for taking so long … Eric Collart Hello, The code is no more trapped by PageSpeed Insight tool if the plugin CookieYes is also deactivated. I will chase CookieYes support why the hell are they doing that ? This ticket can be closed. Thanks a lot for your help and your plugin Eric Collart Marking “Resolved” That’s brilliant news! If you don’t mind, I’d love it if you could let me know what the CookieYes lot say when they get back to you. Hello, I got a procedure to follow to upload script touched by CookieYes but not tested yet… You’ll find the forum post at https://wordpress.org/support/topic/some-javascript-kept-in-place-even-after-their-plugin-uninstallation/#post-18424229 Hoping it will be useful for you ! Eric Collart Why do you think this is useful for me? When my plugin will be removed via the admin panel, it won’t leave any traces behind. Just because you asked me to report answer from CookieYes support… Your plugin has the correct behavior what is not the case of CookieYes plugin that should not prevent removal of scripts from other plugins. It could be I’ll change to another GDPR plugin to avoid that… Huge thanks for your useful plugin and hint about that CookieYes problem. Eric Collart This reply was modified 1 year, 1 month ago by ecollart . Ah, apols, I take the hit. Understood to get inspired to implement what the CookieYes team suggested. All good. Thanks for coming back.

Comments

11 shown
MacSteini 2025-03-25T22:17:00+00:00

Hi Eric, Do me a favour and check if you have a plugin called Cookie Law Info enabled. Disable it and see if the artefact disappears. Report back here. The plugin itself definitely removes itself from the WordPress database but it will not remove any code that has been placed by another party.

ecollart 2025-03-25T22:43:00+00:00

Hello, thanks a lot for your quick reply. I use a plugin for GDPR named CookieYes but Cookie Law Info could be the previous name of the plugin… I will check this when time permits and let you know the result here Eric Collart

MacSteini 2025-04-08T23:21:00+00:00

Any chance you ran a test in the past two weeks? Otherwise, I’m going to set this issue to resolved.

ecollart 2025-04-09T08:37:00+00:00

Hello, not yet but planning this for late evening today (Belgian time); sorry for taking so long … Eric Collart

ecollart 2025-04-09T20:00:00+00:00

Hello, The code is no more trapped by PageSpeed Insight tool if the plugin CookieYes is also deactivated. I will chase CookieYes support why the hell are they doing that ? This ticket can be closed. Thanks a lot for your help and your plugin Eric Collart

ecollart 2025-04-09T20:00:00+00:00

Marking “Resolved”

MacSteini 2025-04-10T07:49:00+00:00

That’s brilliant news! If you don’t mind, I’d love it if you could let me know what the CookieYes lot say when they get back to you.

ecollart 2025-04-18T13:16:00+00:00

Hello, I got a procedure to follow to upload script touched by CookieYes but not tested yet… You’ll find the forum post at https://wordpress.org/support/topic/some-javascript-kept-in-place-even-after-their-plugin-uninstallation/#post-18424229 Hoping it will be useful for you ! Eric Collart

MacSteini 2025-04-18T17:28:00+00:00

Why do you think this is useful for me? When my plugin will be removed via the admin panel, it won’t leave any traces behind.

ecollart 2025-04-18T17:38:00+00:00

Just because you asked me to report answer from CookieYes support… Your plugin has the correct behavior what is not the case of CookieYes plugin that should not prevent removal of scripts from other plugins. It could be I’ll change to another GDPR plugin to avoid that… Huge thanks for your useful plugin and hint about that CookieYes problem. Eric Collart This reply was modified 1 year, 1 month ago by ecollart .

MacSteini 2025-04-18T22:08:00+00:00

Ah, apols, I take the hit. Understood to get inspired to implement what the CookieYes team suggested. All good. Thanks for coming back.