Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi,
before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process.
If your message included code, it might have been trimmed. Could you please try sending it again?
Thank you for contacting WPML support. I'd be happy to assist you on this issue further.
Does the issue exists when translating the slider? Can you attach few screenshots how you are performing the translations so I can help on this further.
yes, the slider is being translated. Actually WPML's interface has recently changed, so I guess it needs to be selected in the dashboard view for translation and then the translation edited in the advanced WPML editor.
Can you provide me urls where this slider is being added?
Further, To debug this issue further, I would need to check your site settings once, for this I would need temporary access (wp-admin and ftp) to your site.
So could you please provide me with those details, you will find the needed fields for this below the comment area when you log in to leave your next reply. hidden link
It’s quite difficult to debug the issue without access to your site. Since you're unable to share login credentials, I’ve set up a temporary public site for testing purposes. You can log in using the following URL:
hidden link
Could you please try installing the slider plugin on this test site and check if the issue persists?
hidden link
<div class="wp-block-gutsliders-content-slider gutslider-697dfc26 nav_inside nav_cc" data-swiper-options="{"slidesPerView":1,[...]
hidden link :
<div class="wp-block-gutsliders-content-slider gutslider-697dfc26 nav_inside nav_cc" data-swiper-options="{"slidesPerView":1,[...]
WPML converts '"' in an attribute string to '"', thus breaking the string structure and the surrounding HTML. Which can be seen by the broken/stalled animation on the translated page.
gutslider's author signaled that he will try to work around WPML's bug, but even if he does, the bug is there and can affect random other attributes.
Thank you for the swift workaround.
I still think this is a basic bug when valid HTML code is transformed into invalid one for non-WPML aware structures, or not?
We generally do not recommend translating that type of content, so I wouldn't consider this a bug. I also tested by adding similar content to the page, and it worked as expected.
I am still confused as to why this is not a bug and what is considered translation worthy and what not.
Which configurations files do you mean that should had been used?
The topic ‘[Closed] WPML alters attribute strings and breaks HTML (and json)’ is closed to new replies.