wooptpm is not defined (JS console error)

Hi
adrian

It is likely that you are deferring the wooptpm.js script, which you shouldn’t, because with the new update it is required to be loaded before the inline scripts.

The inline scripts check if the visitor has made a choice in case you are using a consent management banner and adjust the tracking behaviour accordingly. In order to be able to do this in a consent management compliant way wooptpm.js needs to be loaded before the inline scripts.

Are you deferring wooptpm.js?
If so, how do you do it?

Regards
Aleksandar

Hi
@alekv

I didn’t have to do this in the past, but I followed your recommendation.

I excluded wooptpm.js from defer option of my optimizing plugin (flyingpress). Cleared cache and unfortunately I did not notice any improvement – the same message continues in console.

Maximum compatibility mode is enabled all the time by the way.

The script is still being deferred, which means your exclusion didn’t work.

Could you send me the link of the plugin that you are using for optimization?

I noticed that you are also using Optimocha’s Speed Booster Pack. Could it be that this is the one deferring the script?

@alekv

This is the plugin : https://flying-press.com/

Im not using optimocha speed booster pack, I dont even know what it is. Maybe something was tested in the past but not anymore.

For now im using flyingpress and asset cleanup pro (used just for turn off some css/js), you plugin is not disabled / deferred, etc by this plugin.

Try disabling both plugins, delete any cache, and then reload the website.

If the error is gone you can turn on one by one until you determine which of the plugins is deferring the scripts. Once you know which plugin it is let me know. I might be able to build a workaround into my plugin.

@alekv

When disabled Asset cleanup pro – nothing is happening

When disabled Flyingpress – it is working (no console warning).

For exlude defer im using same method as described here:
https://docs.flying-press.com/javascript/exclude-scripts-from-defer

Flyingpress has option to defer all js (+ add exclusions) and delay (click on user’s interaction). I’m using both all the time.

@alekv

Alek,

I confirm that its Flyingpress fault.

When I turn off defer js options its ok.
When its enabled and I am trying to exlude:
wooptpmGoogleInlineScripts.js
wooptpm
wooptpm.js
– it is not working at all (js error still exists).

Could you look closer for it?

I already have a workaround for Flying Press ready. But I need to do some more testing before I release it. Maybe in a few hours. If not then for sure tomorrow.

@alekv

Sure, its nothing urgent.
Thanks for your help, I will wait for incoming update.

I released a new version 1.12.2 that includes a workaround for Flying Press.

Let me know once you’ve installed it.

@alekv

I checked right now and it seems that problem still exists.

See this screenshot:
https://ibb.co/FXvNBtr

Plugin has been updated, cache cleared.

There was some kind of problem when releasing the version 1.12.2. The files with the relevant updates were not included in the update. I’ve now released 1.12.3 which contains the relevant code. Please install it and let me know once done.

@alekv

I followed the same steps as in the email step. unfortunately, the update did not help and there are still the same errors in console

Did you try to delete any caches?

Could you send me the debug information from the support tab to [email protected]?

@alekv

yes, I cleared whole cache.

I sent you an email with debug.