email tracking can’t be disabled (again)

Hi @zappob

I really am sorry to hear that. Across 3.0.7 and 3.0.12 there shouldn’t be any changes with regard to saving settings.

We will investigate the issue and keep you posted on any updates.

Best regards,
Bartek

Additional information:

As reported, after deactivating and saving, the options appear activated again when the page is reloaded. This can be repeated as often as desired.

What I had already tested: deleting the browser cache does not help either!

New finding: after about 24 hours, the correctly set options appear in a new browser window. I don’t know if it’s a coincidence, but the settings that were deactivated yesterday are displayed correctly today. However, today it continues like yesterday: once activated options remain visible as activated, even if they have been deactivated, even across different browsers and systems.

We use Safari on macOS 13.2.1, but the error also occurs with Firefox 109.0.1,

Could it be a display error on the settings page? But it only affects ShopMagic, we don’t have any other pugin that also shows this problem.

Or could it be that the settings are saved with a delay?

These are just different ideas why this error is so tricky to track.

BR, Zappo

More information to the saved settings:

I enabled and then disabled in Firefox the option “enable outcomes clear”, it still shows enabled when reloading the page, also when opening the settings in Safari (completely independent).

But the setting I found in the database are looking like this:

shopmagic_general_settings

{“wpdesk_tracker_agree”:false,
“enable_session_tracking”:false,
“enable_email_tracking”:false,
“enable_pre_submit”:false,
“enable_outcomes_purge”:false,
“shopmagic_email_from_name”:””,
“shopmagic_email_from_address”:””,
“sm_enable_logs”:false}

——————————–

And now I have found the overarching connection: it is due to the Litespeed Cache plugin. After deleting the Litespeed cache, the options are displayed correctly.

Nevertheless, the question remains: why is this behaviour visible in the ShopMagic settings, no (!) other plugin shows even a similar problem.

To my knowledge, Litespeed only caches the frontend of WordPress and not the backend.

I now have a workaround, but I would be happy if you could investigate this strange behaviour on your site, as it only occurs in your plugin.

BR, Zappo

I’ve investigated the issue, and it seems LiteSpeed caching plugin on LS servers can produce such results in some configuration (I recreated it with standard recommended settings, but more aggressive caching surprisingly didn’t bring up the issue).

Unfortunately, at the moment the issue is a bit stuck, due to limited cache purging possibilities exposed by LiteSpeed plugin API (you can easily purge the whole website cache, which wouldn’t be appreciated, but tagging a specific URL is difficult).

You mention it doesn’t occur in other plugins. Well, I wouldn’t totally agree, but what makes ShopMagic special is the fact we use REST API for administrative side. Cache plugins usually skip admin area, but REST API is a part of regular WordPress website, subjected to regular caching rules.

Finally, we will get to the bottom of the issue, and it will be fixed. I’m glad that you have found a workaround for the meantime. Again, I apologize for the inconveniences.

Hi @bartek,

yes, the statement “no (!) other plugin shows even a similar problem” is a bit bold and should be reduced to “no other plugin we have in use shows even a similar problem”. And there are 72, not several hundred thousands.

Thanks for naming the REST API, as far as I could test it by now, disabling the caching of the REST API in LiteSpeed really seems to solve the problem. I don’t know, if this is the solution, because I don’t know, how much it affects the page speed, but at least there is a hint. I really would appreciate, if you can fix this, or find the answer with the LiteSpeed team. Just a thought.

BR, Zappo

• This reply was modified 1 year, 6 months ago by ZappoB.
• This reply was modified 1 year, 6 months ago by ZappoB.