This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Tagged: Compatibility, Not WPML issue
This topic contains 8 replies, has 2 voices.
Last updated by Eran Helzer 1 year, 7 months ago.
Assisted by: Eran Helzer.
Author | Posts |
---|---|
June 26, 2023 at 7:56 pm #13898001 | |
daniel-viktorV |
I translated everything according to the FSE translation instructions. However, when I look at the translation of the home page (on the frontend), only the texts of the "advanced text" block are displayed in the translated language, the "advanced heading" and the buttons are still displayed in the original language (even though they are translated in the database). |
June 27, 2023 at 10:10 am #13901297 | |
Eran Helzer Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Hi, From reading your chat with Lauren I see that you have tried the usual trouble shooting steps: From the results of these steps, not being able to reproduce the issue on a test site, we can possibly assume that a combination of actions on the original site have caused this issue, and that we are not talking about a simple incompatibility issue. I would like to escalate this to our development team, for that I will need the following: Also, are you using the latest versions of WPML? If not, please update to the latest version and check if the issue persists. In the meantime, I would like to have access to your staging site admin. Maybe I will manage to resolve the issue by myself. If there is anything which you do not want me to change or touch on the staging site, please tell me so. |
June 28, 2023 at 1:08 pm #13910365 | |
Eran Helzer Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Update, Had some issues at first until I realized WPML was registered with an incorrect site key. After resolving that, I started looking around. There is a small issue, I seem not to be set as a translator so I have limited access. Could you add me? Also, if you could provide a Duplicator package in the meantime so when we are ready we can escalate this quickly, that would be great. |
June 29, 2023 at 10:45 am #13916935 | |
Eran Helzer Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
I am sorry, but I forgot to mention. I also need the admin user of the Duplicator package in order to log in. |
July 4, 2023 at 5:53 am #13936947 | |
Eran Helzer Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Update, I have escalated this to our 2nd tier team. |
July 4, 2023 at 11:20 am #13940193 | |
daniel-viktorV |
Thank you, I am very, very much looking forward to it! |
July 6, 2023 at 6:31 am #13955061 | |
Eran Helzer Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Okay, good news. The development team have found the issue. It seems like the WPML configuration in Greenshift was incorrect, thus missing the "Advanced Heading" block. They registered only the Advanced Header block's attributes, which is useful when content is dynamically rendered on the frontend, like so: <gutenberg-block type="greenshift-blocks/heading" translate="1" label="Advanced heading"> <key name="text" /> <key name="textbefore" /> <key name="textafter" /> <key name="headingContent" /> <key name="customAnchor" /> <key name="subTitle" /> <key name="animatedText"> <key name="*" /> </key> <gutenberg-block> However, the block content was already generated in the backend and stored as HTML. Hence, the solution was to update the configuration to also register and translate the HTML content. Final solution, which you can see worked on the test site as well, is this: <wpml-config> <gutenberg-blocks> <gutenberg-block type="greenshift-blocks/heading" translate="1" label="Advanced heading"> <xpath>//*[contains(@class, 'gspb_heading')]</xpath> <key name="text" /> <key name="textbefore" /> <key name="textafter" /> <key name="headingContent" /> <key name="customAnchor" /> <key name="subTitle" /> <key name="animatedText"> <key name="*" /> </key> </gutenberg-block> </gutenberg-blocks> </wpml-config> - Make a small change to the "Front Page" template, so it is resent to translation Now, this solution resolves this issue with the "Advanced Heading", however the same may occur with other blocks of theirs. If your run into any issues, please don't hesitate to reply here. |
July 6, 2023 at 2:25 pm #13961117 | |
daniel-viktorV |
Thank you, I will report this to the developer of Greenshift! Meanwhile, I've run into another problem: New threads created by Eran Helzer and linked to this one are listed below: https://wpml.org/forums/topic/split-greenshift-not-showing-navigation-block-in-translation-editor/ |
July 7, 2023 at 8:30 am #13965911 | |
Eran Helzer Supporter
Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00) |
Well, since this is a separate issue, we need to split it into a separate ticket. Our company policy is to keep it to one issue per ticket, that way every thing is very clear and organized. I suspect the solution will be very similar, however it is still best to split. Me or one of my colleagues will answer your there. |