Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is using the GreenShift Builder with WPML to build and translate their website. While translating the homepage using WPML’s Advanced Translation Editor, the translated version displays the default language content instead of the translated content. Additionally, an error in the backend indicates that the block contains unexpected or invalid content, prompting a block recovery message.
Solution:
We resolved the issue by updating the GreenShift plugin and its add-ons to the latest version. It is crucial to follow the correct WPML translation process and avoid editing the translated content directly in the Gutenberg editor. After these updates and following the proper procedures, we tested the system thoroughly and confirmed that everything is now working as expected.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.

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.

This topic contains 4 replies, has 1 voice.

Last updated by justinb-4 3 weeks, 4 days ago.

Assisted by: Itamar.

Author Posts
June 6, 2025 at 12:42 am #17112703

justinb-4

Background of the issue:
I am using the GreenShift Builder along with WPML to build and translate our website. I am trying to translate GreenShift element blocks using WPML’s Advanced Translation Editor. I’ve recorded a video explaining the issue in more detail: hidden link. The issue can be seen on this page: hidden link.

Symptoms:
While translating the homepage, the translated version continues to display the default language content. In the backend, there is an error stating that the block contains unexpected or invalid content, prompting a block recovery message.

Questions:
Is the GreenShift element block fully compatible with WPML?
Is an additional configuration, such as a custom configuration file, required for proper operation?

June 8, 2025 at 3:27 pm #17116493

Christopher Amirian
WPML Supporter since 07/2020

Languages: English (English )

Timezone: Asia/Yerevan (GMT+04:00)

Hi,

Welcome to WPML support. I will answer this question before the ticket is assigned to one of my colleagues.

Tis might be a compatibility issue with the Greenshift plugin and WPML that needs more investigation.

To be able to report the compatibility issues we need to replicate the issue on a clean installation.
I created a clean installation of WordPress, WPML, and all necessary WPML add-ons.
You can access the WordPress dashboard using the link below:
hidden link

Kindly follow the steps below:

- Install Elementor
- Install the necessary Greenshift plugins.
- Add a sample page and use the widget
- See if you can replicate the issue.

This will help us to report the probable issue to the compatibility team and solve the possible problem faster.

June 11, 2025 at 6:53 am #17124081

justinb-4

Hi,

Thanks for your response.

We’ve installed the Greenshift plugins on the sandbox environment and created a new page. We then copied the section from our dev site into this new page and attempted to translate it. However, we were unable to use WPML AI in the sandbox. When we tried to connect it to our existing WPML account, we encountered an error.

I’ve explained the situation in detail in the video linked below—please take a moment to review it.

hidden link

Our goal is to enable WPML AI in the sandbox so we can reproduce the issue we’re seeing on our live site, particularly with the Greenshift link element. It seems that the error only occurs for this element when using automatic translation. When translating the same block manually without WPML AI, there is no error on the greenShift link element in the original language.

Please let us know if you need any additional information. I’d be happy to provide anything required.

Thanks

June 11, 2025 at 4:00 pm #17127094

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I'll continue to help you with this issue.

I activate a "Dummy" automatic translation engine on the sandbox, so you should be able to proceed with testing this case.

Regards,
Itamar.

June 12, 2025 at 1:57 pm #17130465

justinb-4

Hi,

We’ve resolved the issue. It appears that updating the Greenshift plugin and its add-ons to the latest version, along with following the correct WPML translation process (without editing the translated content directly in the Gutenberg editor), has addressed the problem.

We’ve tested it thoroughly, and everything now seems to be working as expected. We truly appreciate your support and assistance throughout this process.

Thank you!