Hi
In a first time could you delete all the strings which contain *html and script*.
Then save your changes and check if the other strings translation are correctly saved.
Does it works?
Thread Starter
mdugre
(@mdugre)
OK this may sound like a dumb question but, since I’m FAR FROM BEING a guru when it comes to this and to avoid any mistake here, by HTML, I take it you mean all strings containing any kind of HTML formatting such as the below, correct?
<h1><img class=”alignleft size-full wp-image-845″ src=”http://www.datatelcom.com/wp-content/uploads/2014/11/TreeView128.gif” alt=”TreeView128″ width=”200″ height=”200″ /></h1><h1></h1><h1></h1><h1><span style=”color: #000000;”>Member Options</span></h1>
And by script, you mean strings such as this one, right?
%%title%% %%page%% %%sep%% %%sitename%%
Please confirm.
Cheers,
Marc
Your link is broken.
%%title%% %%page%% %%sep%% %%sitename%%
No.
This kind of strings which content html, script, here an example: http://fr.tinypic.com/view.php?pic=xanx4i&s=8#.VVX2K7yKE0w
EDIT: Could you give me the list of all your plugin? There is certainly a conflict with one of them and I would like to find it.
Thread Starter
mdugre
(@mdugre)
Ah, OK re: broken Link. Thanks for pointing it out. Took it directly from Polylang’s string translation pages. Wouldn’t surprise me if there were a few like that link
Re: scripts, from your example, I can tell you I have none on my site.
Plugin Author
Chouby
(@chouby)
Hi!
You are not the first to get issue with strings translations containing html tags. Up to now, this is not something I could reproduce.
As suggested by @chrysl, please switch to Twenty Fifteen, de-activate all your plugins except Polylang. Then re-activate them one by one, trying to save a string translation with html tags each time, until you find the conflict source.
Thread Starter
mdugre
(@mdugre)
Hello Chouby,
Thank-you for the suggestion however, so far, it looks like the problem was between the chair and the keyboard.
I’ve uninstalled Polylang and reinstalled it. After doing that, I ended up with only 2 pages of string translations. I’m now redoing things and will let you know what the results are.
Hopefully, everything will be OK now.
Cheers,
Marc
Thread Starter
mdugre
(@mdugre)
Hi Chrystl,
Never saw that you requested a list of the plugins I use, here you go
Black Studio TinyMCE Widget
Custom Sidebars
Easy Google Fonts
Gmedia Gallery
POLYLANG
Post Duplicator
Profile Builder Pro
Regenerate Thumbnails
Social Media Feather
Ultimate Product Catalogue Plugin
User Login Log
Visual Form Builder Pro (VBF Pro)
VFB Pro – Form Designer
Wordfence Security
WordPress Access Control
WordPress SEO
WP Edit
FYI, Here are a few examples of strings on Page 1 that if I translate, BOOM, everything reverts back to the original English version.
<i>profile-builder-pro wppb_user_emailc_default_registration_email_subject A new account has been created for you on {{site_name}}
English : A new account has been created for you on {{site_name}}
Français: A new account has been created for you on {{site_name}}
profile-builder-pro wppb_user_emailc_default_registration_email_content <h3>Welcome to {{site_name}}!</h3> <p>Your username is:{{username}} and password:{{password}}</p>
English : <h3>Welcome to {{site_name}}!</h3><p>Your username is:{{username}} and password:{{password}}</p>
Français: <h3>Welcome to {{site_name}}!</h3><p>Your username is:{{username}} and password:{{password}}</p>
profile-builder-pro wppb_user_emailc_registr_w_email_confirm_email_subject [{{site_name}}] Activate {{username}}
English : [{{site_name}}] Activate {{username}}
Français: [{{site_name}}] Activate {{username}}
profile-builder-pro wppb_user_emailc_registration_with_admin_approval_email_content <h3>Welcome to {{site_name}}!</h3> <p>Your username is:{{username}} and password:{{password}}</p> <p>Before you can access your account, an administrator needs to approve it. You will be notified via email.</p>
English : <h3>Welcome to {{site_name}}!</h3><p>Your username is:{{username}} and password:{{password}}</p><p>Before you can access your account, an administrator needs to approve it. You will be notified via email.</p>
Français: <h3>Welcome to {{site_name}}!</h3><p>Your username is:{{username}} and password:{{password}}</p><p>Before you can access your account, an administrator needs to approve it. You will be notified via email.</p>
wordpress-seo breadcrumbs-404crumb Error 404: Page not found
English : Error 404: Page not found
Français: Error 404: Page not found</i>
Foregoing all the translations on Page 1 I also still have the same problem I initially reference. Meaning as soon as I translate things beyong page 3 of the sting translation tables, BOOM, everything reverts back to the original English version
As suggested by @chrysl, please switch to Twenty Fifteen, de-activate all your plugins except Polylang. Then re-activate them one by one, trying to save a string translation with html tags each time, until you find the conflict source.
Did you find the conflicting plugin?
Thread Starter
mdugre
(@mdugre)
Hi Chrystl,
As far as I can tell, the conflicting problem is Profile Builder (Pro) and has to do with custom fields. Some translations are happening BUT others are not. As far as those that do not, when hitting the save button, all translated strings revert back to the default English version.
After trying many things including switching to the 2015 Theme and then reverting back to Customizr
1. Where I was allowed (some being locked), deleted all PB Pro entries in Polylang’s string translation table
2. In PB Pro’s managed Field option, deleted ALL custom fields (this also deleted all extra fileds added in wp-users)
3. Now recreating all custom fields and testing them in Polylang as I go.
Painful process but, I don’t see any other way of finding out which custom field is causing everything to reset.
Thread Starter
mdugre
(@mdugre)
OK, here’s what I have so far and it’s ALL related to Profile Builder
Customs fields
1. All INPUT type fields are compatible with Polylang WITHOUT the need to implement the plug-in described on http://www.cozmoslabs.com/docs/profile-builder-2/developers-knowledge-base/support-themes-plugins/shortcode-add-support-polylang-plugin/
2. Special fields such as select, radio button and others are problematic. The label is translated BUT, the selection/content don’t show up for translation. They CAN be translated with the plugin described on http://www.cozmoslabs.com/docs/profile-builder-2/developers-knowledge-base/support-themes-plugins/shortcode-add-support-polylang-plugin/ AND using code like <span lang=”en-CA”>Username</span><span lang=”fr-FR”>Nom d’utilisateur</span> BUT you get funky results when displaying.
3. Translating ANY PB strings such as the below resets ALL the strings to the set default language
profile-builder-pro wppb_user_emailc_default_registration_email_subject A new account has been created for you on {{site_name}}
English : A new account has been created for you on {{site_name}}
Français: A new account has been created for you on {{site_name}}
profile-builder-pro wppb_user_emailc_default_registration_email_content <h3>Welcome to {{site_name}}!</h3> <p>Your username is:{{username}} and password:{{password}}</p>
English : <h3>Welcome to {{site_name}}!</h3><p>Your username is:{{username}} and password:{{password}}</p>
Français: <h3>Welcome to {{site_name}}!</h3><p>Your username is:{{username}} and password:{{password}}</p>
Fields with special formatting such as the below CAN be translated BUT, pardon my French, it’s a pain and a half and more often than not, resets all the strings to the set default language
<h1 style=”text-align: center;”><span style=”background-color: #bff8fc; border: 1px solid #506ef4; padding: 2px 5px; border-radius: 3px;”>Demande d’accès à la section membre</span></h1>
Thread Starter
mdugre
(@mdugre)
Well it’s confirmed. Any fields with a type other than INPUT are problematic. As per the initial post, doing any translations of those field’s content causes the translation string table to revert back to it’s default state, English in my case.
Here’s the reply I received from the Cozmoslabs’ (authors of Profile Builder) support people
“The plugin is indeed working for inputs only.
I’ve added a ticket in our issue tracker and hopefully we’ll implement this in the future, but for now, there really isn’t much we can do.”
Hopefully, they’ll figure it out and solve the problem. Profile Builder’s a great plug-in and compatibility with Polylang can only make it better and more attractive to users 😉
