Dražen Duvnjak
Supporter
Languages:
English (English )
Timezone:
Europe/Zagreb (GMT+01:00)
|
Hello,
please go to WPML > Settings > Custom XML configuration and add next code:
<wpml-config>
<gutenberg-blocks>
<gutenberg-block type="core/embed" translate="1">
<key name="url" type="LINE" />
<xpath>//figure/div</xpath>
</gutenberg-block>
<gutenberg-block type="core/video" translate="1">
<key name="id" />
<xpath>//figure/video</xpath>
</gutenberg-block>
</gutenberg-blocks>
</wpml-config>
Make a small change to the default language page and re-translate, save.
It should work fine, I have just checked on Sanbdox.
- hidden link
Regards,
Drazen
|
T4ng
|
OK, indeed, it seems to solve the issue.
Unfortunately, these adjustment seem to be managed by the code in our environment, and I couldn't get it working from there.
I'll double check with the developer once he's available.
By the way, will this be fixed natively in the next WML release, so that we won't need to maintain this custom setting from the WPML Settings > Custom XML configuration?
Thanks
|
Osama Mersal
Supporter
Languages:
English (English )
Arabic (العربية )
Timezone:
Africa/Cairo (GMT+02:00)
|
Hi,
1) Please let us know if the custom XML fixed the issue on your site.
2) I'm unsure if that XML will be included in the next release, but when you add it to WPML-> Settings-> Custom XML tab, it won't be affected if you update WPML plugins.
Best regards,
Osama
|
T4ng
|
Hi,
Thanks for your reply.
As explained earlier, yes, I tested your solution and it does solve the issue.
However... Obviously, this issue also occurs on a fresh/clean/up-to-date/native-theme environment. Which shows our and environment, and our customizations are not causing it.
Therefore, there's a good chance that we're not the only one of your customers facing it.
For multiple reason, I'd much rather have it solved natively, that relying on a custom setting (even if I'm ok to set it up this way for now).
Is there any reason not to push this fix in WPML in further verions, so that this works for everyone, out-of-the-box?
Thanks
|
Osama Mersal
Supporter
Languages:
English (English )
Arabic (العربية )
Timezone:
Africa/Cairo (GMT+02:00)
|
Hi,
1) On the fresh installation, the custom XML provided by Drazen fixed the issue. If this custom XML didn't fix the issue on your site, I would need to request temporary access (WP-Admin and FTP)
– preferably to a test site where the problem has been replicated if possible –
in order to be of better help and check if some configurations need to be changed.
Your following answer will be private, which means only you and I can access it.
❌ Please backup your database and website ❌
✙ I would need your permission to de-activate and re-activate the Plugins and the Theme and change configurations on the site. This is also a reason the backup is critical.
✙ I also need your permission to take a local copy of your site to debug the issue without affecting your live site.
2) The issue doesn't happen using the Advanced Translation editor, which is the recommended editor.
3) Our 2nd tier support team is aware of the issue, and it will be fixed in the future.
Best regards,
Osama
|
T4ng
|
I don't need assistance on our website.
I just to asked why this solution wouldn't be applied into further versions, if the problem occurs on a clean environment.
By the way, indeed, I use the Classic Translation Editor, and will keep using it.
I was told, in my last WPML ticket, that the Classic Translation Editor was still fully supported, and would remain.
If that's not the case, that'd be the 3rd time I get a different statement from WPML's support fellows on this topic.
Be that as it may, I really hope you guys understand that your Advanced Translation Editor is not a one size fits all tool.
In our case, it's actually very restrictive, and we just can't use it. Indeed, we don't need automated translation through external service, but we do need to adjust some HTML content from time to time. Which the Advanced Translation Editor doesn't offer.
I hope you understand.
|
Osama Mersal
Supporter
Languages:
English (English )
Arabic (العربية )
Timezone:
Africa/Cairo (GMT+02:00)
|
Hi,
I understand that the Advanced Editor is unsuitable for you and that you want to translate using the Classic Editor, which is fully supported.
When the issue is replicated on the fresh installation, we suggest a workaround using XML code to fix the issue, which fixed the issue on the sandbox site.
If this workaround didn't fix the issue on your site, please share access details or a site copy to check the issue on your site.
Our 2nd tier support team is aware of the issue, so it will be escalated to our dev team.
Best regards,
Osama
|
T4ng
|
OK, thanks for your support. I'll check with our developpers for the most pertinent way to add this setting to our environment.
|
