Hi
I’ll look into it but the first thing to be able to perform your ajax (and probably gzipping also) is simply to prevent any such error to be displayed. They should be logged to a file and never displayed as they create a (fairly small) security risk. Note that this is unrelated to weeblrAMP, it’s just a general security practice.
So you should first set your WP_DEBUG to false in your wp-config.php file, or adjust the corresponding PHP setting on your server.
Now on to the warning:
1 – What’s the history? when did this start to happen?
2 – If you update to weeblrAMP 1.10.2.693, did you re-save configuration after updating (normally not required at all, just checling).
Best regards
Hi
Sorry about previous message, I skipped the “with debug turned on”. So you know what you’re doing and should skip to the second part, the questions.
Best regards
Hi again,
I tested this locally and I can reproduce it so we should be able to fix it quickly.
Best regards
Hi
We have identified the issue and created a fix. We’ll have a new release very quickly. In the mean time, you can simply go to weeblrAMP settings page and press the Save button. This will re-save the configuration and solve the problem. Be sure to double-check your Analytics settings, it might be reset in the process (this won’t happen when installing the fixed version we’ll release hopefully tomorrow).
Thanks again for your report.
Best regards
Yes this is in my beta testing environment. I updated the plugin and didn’t save the settings for it after updating. Once I saved the plugin settings again the warning disappeared.
Hi
Glad it’s sorted, we’ll have the new release today.
Best regards
