Skip Navigation

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.

Our next available supporter will start replying to tickets in about 6.18 hours from now. Thank you for your understanding.

This topic contains 5 replies, has 2 voices.

Last updated by Mohamed Sayed 1 year, 10 months ago.

Assisted by: Mohamed Sayed.

Author Posts
June 21, 2022 at 5:25 pm #11512561
dannyB-14

When I translate the contact us page: hidden link with the WPML translator, I can translate the content of the page, but the form stays in the default language.

When I edit with beaver builder in order to paste the form's shortcode : [forminator_form id="4225"]
& I publish, it reverts back to the default language...

Same with the Consultation V2 global footer, if I translate it with WPML nothing happens, even though it's properly done...

This is all I'm have a difficulty with, then the site is working fine.

New threads created by Mohamed Sayed and linked to this one are listed below:

https://wpml.org/forums/topic/split-cannot-translate-global-footer/

June 22, 2022 at 8:54 am #11517265

Mohamed Sayed

Hi Danny,
Thanks for contacting WPML support.

1) I checked the compatibility status between WPML and Forminator and found that it's not officially compatible, it's not listed on the WPML compatibility list for the plugins - https://wpml.org/plugin/. This means that our compatibility team has not tested it yet.

The plugin's support suggests creating a different form for each language then replacing the shortcodes on the translated page hidden link

Could you please check if that helps?

2) Please upgrade your MySQL version to 5.6 or above (This is the minimum required MySQL version for WPML). Kindly check here for more details: https://wpml.org/home/minimum-requirements/

3) For better support, we handle one issue per ticket. So I've created a new ticket for the global footer, we can continue the discussion about it here: https://wpml.org/forums/topic/split-cannot-translate-global-footer/

Regards,
Mohamed

June 22, 2022 at 2:05 pm #11520707

dannyB-14

Hi Mohamed,

Thanks for the quick reply, I have 2 separate forms created, 1 for English and 1 for French.

The English one loads on both contact us page, EN & FR, when I replace the shortcode of EN form to the FR one on the FR page, it breaks the translation and reverts everything back to EN...

June 22, 2022 at 2:14 pm #11520759

dannyB-14

the host (WPMUDev) just confirmed that they don't use the mysql, instead we use 10.3.35-MariaDB-1:10.3.35+maria~bionic.

No idea what that means....

June 22, 2022 at 2:14 pm #11520763

dannyB-14

So to run WordPress it actually requires MySQL version 5.7 or greater OR MariaDB version 10.3 or greater.

June 22, 2022 at 6:57 pm #11523423

Mohamed Sayed

Hi,

For the WPML requirements related to DB, MariaDB 10.3.35 should be ok as mentioned in our docs here: https://wpml.org/home/minimum-requirements/#:~:text=Alternatively%2C%20you%20can%20use%20MariaDB%2010.1%20or%20greater.

I've tested the Forminator plugin on my demo site and found the issue, the post type: "Custom Forms (forminator_forms)" is set to "Not Translatable" by default.

Please try the following steps:

- Go to WPML > Settings > Post Types Translation
- Set the post type Custom Forms (forminator_forms) to "Translatable - only show translated items"
- Go to Forminator > Forms
- Delete the form you created for the secondary language
- Switch to the French language from the switcher in the top admin bar
- Recreate the French form
- Translate the page
- Edit the page in the default language with the WP editor
- Switch to the French language from the switcher in the top admin bar
- Replace the shortcode with the french one

The above steps work on my demo site as you can see here: hidden link

Let me know please if that helps.

Regards,
Mohamed

Forminator_settings.png
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.