WPIntell

Source evidence

Don’t translate values

Translate Gravity Forms x Polylang · support · 2024-07-11T15:38:00+00:00

complaintsentiment
highseverity
1.0relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

8 / 36 rows with source links

22.2% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
edelcambre unresolved
Hello, First, thank you so much for this plugin. I am used to Polylang and switched to WPML because it had a Gravity forms integration, bust WPML is such a nightmare… So i switched back and tried your plugin and it does exactly what I need. The only thing is that I don’t want the values to be translated, only the labels, so that all appears in original language in the admin. I edited the code modifying the white and black lists in the GravityFormsPolylang constructor, in order to black list the “value”, but maybe in the next version you could use a filter on white and black list to avoid this ? I also had to edit the code to avoid a fatal error (PHP 8.2) : Fatal error : Uncaught Error: Return value of GravityFormsPolylangInitialize::translateStrings() must be an instance of mixed, array returned in /Applications/MAMP/htdocs/cinelatino/wp-content/plugins/translate-gravity-forms-x-polylang/gf_pll.php on line 31 I just erased the “mixed” type from the line. Thanks again, Etienne Hello, thank you for your feedback! The PHP Fatal error has been fixed in the latest version. I will think about what I can do for the value translations. Would a settings page where you can select which field types should be translated work for you? Hello, Thank you! I realise I did not reply, sorry. A settings page would be great but as far as I am concerned, a filter to the blacklist array in the GravityFormsPolylang constructor would do the trick. Thanks again! Etienne

Comments

2 shown
Sibren 2024-10-28T10:56:00+00:00

Hello, thank you for your feedback! The PHP Fatal error has been fixed in the latest version. I will think about what I can do for the value translations. Would a settings page where you can select which field types should be translated work for you?

edelcambre 2024-11-26T13:58:00+00:00

Hello, Thank you! I realise I did not reply, sorry. A settings page would be great but as far as I am concerned, a filter to the blacklist array in the GravityFormsPolylang constructor would do the trick. Thanks again! Etienne