Hello Jordy,
As a follow-up here is some information that I received from the WPPA+ developer that identifies the problem within Meow Lightbox. I hope this helps.
The json data that is received at the client side lookes like (fragment of svg html item):
<animate attributeName=\"opacity\" ...\"indefinite\" \/>
When it is processed by my ajax js functions JSON.parse() it has been changed to:
<animate attributename=\"opacity\" ...\"indefinite\" \>
So, the (redundant) / at the end of the animate tag is removed, but not the escape char, causing the error message in the browser console:
Uncaught SyntaxError: JSON.parse: bad escaped character at line 1 column 678 of the JSON data
because of \> being bad escaped.
So, recommend Jordy stop removing redundant slashes at the end of self closing tags, or check if the slash has been escaped in which case: also remove the escape char.
We discovered two more issues with the Meow Lightbox plugin cited below.
The json data is being damaged by Meow Lightbox plugin as follows:
It changes
wppaAjaxRemoveComment(\\'125\\',true)
into
wppaajaxremovecomment(\\'125\\',true)
(and)
It changes
https:\/\/betatest.opajaap.nl\/wp-admin\/admin-ajax.php
into
https:\\betatest.opajaap.nl\wp-admin\admin-ajax.php
Have you tried disabling Output Buffering in the Meow Lightbox’s Settings?
Are you going to fix the issues identified in this ticket?
Stepping on other plugins’ toes is not acceptable.
Plugins are overriding parts of WordPress by definition.
Make sure you read my previous answer here, as it’s important. But the culprit is not who you think it is 🙂
Your suggestion of disabling the Output Buffering option within Meow Lightbox performance did resolve the conflict Jordy.
My point is that this setting is ENABLED by default, and therefore, steps on other plugins’ toes by altering their code.
Wouldn’t changing the default of this option improve compatibility between your plugin and others sharing the same parts of WordPress?
