Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author alekv

    (@alekv)

    Okay, I answered on the other thread, and we’ll be closing this one.

    Thread Starter Firelight

    (@mdc2957)

    Thanks for the reply in the other thread. I read your doc about possible other reasons. I went to the elementor editior, and previewed my order confirmation summary page. In the console, I do see two errors, do either of these mean anything to you?:

    [NSL Definitive] CRITICAL: Could not find the source buttons. The shortcode style change might have changed the container class.

    and

    Pixel Manager error: The wpmDataLayer is not defined. Please make sure that the wpmDataLayer script snippet is inserted and not modified by any third-party plugin, such as a consent management platform or a JavaScript optimizer.
    (anonymous) @ functions_main.js:47
    setTimeout
    e.wpmDataLayerFullyLoaded @ functions_main.js:46
    (anonymous) @ main.js:14
    await in (anonymous)
    (anonymous) @ main.js:196
    (anonymous) @ wpm-public.p1.min.js?ver=1.54.1:1`

    Thread Starter Firelight

    (@mdc2957)

    I believe I solved the issue with the help of AI. It said that my cache was likely causing the issue, so it had me add

    wpm
    pixel-manager
    wpmDataLayer

    to the JS excludes and JS Deferred Excludes boxes. When I refreshed the page, the error in the console went away.

    Is there a way to reset the diagnostics counter to start checking the % again from zero after the fix?

    Thread Starter Firelight

    (@mdc2957)

    That actually wasn’t it, it was the ESI setting in Litespeed that caused the wpmDataLayer to not work. After I turned off ESI, the pixel fired, and the error was gone!

    Plugin Author alekv

    (@alekv)

    Okay, thanks for that information. The Pixel Manager should be compatible with ESI in Litespeed. I will look into this.

    Plugin Author alekv

    (@alekv)

    I tested this locally with Litespeed ESI, and everything worked fine. I had not had any issues. Unfortunately, I cannot replicate the problem that you ran into.

    Thread Starter Firelight

    (@mdc2957)

    Really hmm.. AI told me to check the page source for wpmDataLayer and I found this info:

    <!– lscwp Inject data layer through ESI block –>
    .
    .
    .
    <!– Block uncached by LiteSpeed Cache 7.7 on 2025-12-21 15:34:11 –><!– lscwp Inject data layer through ESI block esi end –>
    <!– END Pixel Manager for WooCommerce –>

    AI said:

    **LiteSpeed is using ESI (Edge Side Includes) to inject the wpmDataLayer!** This is a LiteSpeed-specific caching feature, but it’s causing the script to load **too late** – after the Pixel Manager’s main scripts have already tried to access it.

    Plugin Author alekv

    (@alekv)

    1. ESI should only work on pages when you are accessing it while logged into the shop. This means only logged-in users should be affected. And in your case, it looks like many more are affected. This is an indication that it is not ESI, but also not 100% sure to rule it out.

    2. The Pixel Manager has been built to work properly with ESI enabled, and in our tests, it used to work fine.

    I have to be able to replicate the issue that you have to have a proper look. Is there a way for you to give me access to what you see so that I can replicate the issue that you see? You can send me a support request to [email protected] if you need to send data that should not be public.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    @alekv I’m am 100% sure you mean well but please never ask for credentials on these forums.

    https://wordpress.org/support/guidelines/#we-reserve-the-right-to-manage-the-forums-to-the-best-of-our-ability

    Now for the why: The internet is a wonderful place full of very nice people and a few very bad ones. I’m sure everyone here is very nice however, by giving some ones keys to your house you are trusting they wont steal anything. Likewise the person who takes the keys is now responsible for the house FOREVER.

    If something was to go wrong, then you the author may well legally become liable for damages, which they would not normally have been as their software is provided without warranty.

    Please be aware that repeatedly asking for credentials will result in us escalating this to the plugins team.

    It’s never necessary to do that. Here’s why.

    There are many ways to get information you need and accessing the user’s site is not one of them. That’s going too far.

    *Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.

    *Ask the user to create and post a link to their phpinfo(); output.

    *Ask the user to install the Health Check plugin and get the data that way.

    *Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.

    *Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again.

    *Ask the user for the step-by-step on how they can reproduce the problem.

    You get the idea.

    Volunteer support is not easy. But these forums need to a safe place for all users, experienced or new. Accessing their system that way is a short cut that will get you into real trouble in these forums.

    Plugin Author alekv

    (@alekv)

    Hi @sterndata I have not asked for any credentials. I know about that rule, but in this case, if the shop owner wants to send me the link to a staging server or a URL that should not be be public then he as well could do that by sending it to our support inbox, or not?

    Especially in this case, it affects the purchase confirmation page, where even an example link might contain PII (personally identifiable information) in it.

    Do you agree that this is allowed to take to [email protected] or not?

    And if not, how would you then share this information?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Yes, if it’s just PII or other private stuff, it’s OK, but I want to be sure you will not ask for a password or, if one is provided, use it.

    Plugin Author alekv

    (@alekv)

    @sterndata

    I would even ask the mods to remove such information if it was posted here, which I already have done in the past.

    • This reply was modified 1 week ago by alekv.
Viewing 12 replies - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.