as mentioned the workaround for this case works, thank you again.
Nevertheless there is a bug where WPML accidentally messes the structure of string attributes whether they should be translated or not. You created a workaround for a specific case, but the bug will strike again, or has already done so in other existing cases (reported or not).
Remember this issue is already a old before I hit on it and debugged it until I found the cause.
I attempted to replicate the issue again with post contents I am unable to reproduce it with it, can you provide me another example if you have where I can reproduce the issue?
This isn’t a bug in WPML. It’s because the plugin needs to add a WPML integration (with the XML file), but they don’t have that yet. The plugin author should fix that.
Without the integration, we can run into problems like this.
so WPML is breaking otherwise valid HTML/CSS unless a plugin adds WPML compatibility code?
AFAIK WPML was doing its best until now to not randomly break plugins. Now there is a new requirement that only WPML compatible plugins are admitted which is a huge restriction - I am not even sure what percentage of the plugin have WPML compatibility code.
This is not about this specific plugin - it is about every plugin that does not have WPML compatibility code, which is the majority. The debugging of this issue took various people weeks and moths to conclude it even had to do with WPML. I'm sure there are other issues where WPML might have struck and people are still debugging.
So far, we’ve only received a report from you. I’ll keep an eye out for similar issues in other plugins and let our developers know if I find anything. That way, we can try to prioritize it and see if we can do something about it.
Unfortunately, I’m afraid we won’t be able to move forward with this at the moment.
Thanks again!
The topic ‘[Closed] WPML alters attribute strings and breaks HTML (and json)’ is closed to new replies.
