Skip Navigation

[Resolved] CRED form translation issues

This support ticket is created 3 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 13 replies, has 2 voices.

Last updated by caroleM-4 2 years, 12 months ago.

Assisted by: Minesh.

Author
Posts
#2231833
toolset.jpg

Hello,

I just noticed two issues with CRED form translations :

1) If the form contains several HTML blocks, only the last one appears in the translation editor and its translation is used for all blocks (see attached screenshot as well as pages hidden link and hidden link). I guess the problem comes from the fact that the visual editor gives all of them the same name (scaffold_field_id) wich I could correct in expert mode but impossible then to switch back to visual editor.

2) If I link two strings in the translation editor in order to have only one in secondary language (for exemple two sentences in English being only one in French), I have to link them again after each change to the source version even if not in that part of the form.

I can do with the second issue if there is no way to fix it but the first one is really annoying as I need to stick to the visual editor in order to allow our customer to edit the form if needed.

Thanks in advance for your help.

#2232061

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Can you please share admin access details so I can check whats going wrong with your setup.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

#2232373

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

As per our support policy, we will handle only one question per ticket. We will handle your 2nd issue one we are done with the 1st issue you reported.

1) If the form contains several HTML blocks, only the last one appears in the translation editor and its translation is used for all blocks (see attached screenshot as well as pages hidden link and hidden link). I guess the problem comes from the fact that the visual editor gives all of them the same name (scaffold_field_id) wich I could correct in expert mode but impossible then to switch back to visual editor.
==>
I checked the issue and yes, I can reproduce this issue and the trick to this issue is once you rename the "scaffold_field_id" to different names like I've renamed as:
=> hidden link

[cred_i18n type="html" name="scaffold_field_id-1"]<p>First HTML block in English...</p>[/cred_i18n]
[cred_i18n type="html" name="scaffold_field_id-2"]<p>Second HTML block in English ... </p>[/cred_i18n]
[cred_i18n type="html" name="scaffold_field_id-3"]Third HTML block in English ...[/cred_i18n]

Once you rename the name attribute to non-unique name (scaffold_field_id-1, scaffold_field_id-2, scaffold_field_id-3) we should save the form. Once you save the form you should resend your form for translation and at that time you will see all HTML blocks string will be available for translation:
=> hidden link

This is the quickest workaround as of now as I've reported the issue to our next level support and they will investigate it and report the issue in front of our Devs but there is no ETA when the fix for this issue will be available.

#2232993

Thanks for the feedback Minesh.

As you can see in my first message, I already thought about that workaround but it's annoying for me as I can't then switch back to the visual editor without loosing all except last HTML block and our customer won't be able to manage the form in expert mode. So let's hope it will be fixed soon and, until then, I'll have to find a way to avoid using more than one HTML block.

As for the second issue, I let you see if you want to do something about it or not because I already lost a lot of time running after workarounds for several other issues and thus won't open another ticket for one I can perfectly live with. I mentioned it only because I think it may be uncomfortable for users that often encounter it due to the type of content they are handling but it's not my case so it's ok for me if you think it does not need to be fixed.

Have a nice day.

#2233099

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Can you please share more details about your 2nd issue:
2) If I link two strings in the translation editor in order to have only one in secondary language (for exemple two sentences in English being only one in French), I have to link them again after each change to the source version even if not in that part of the form.
==>
Actually, what link you are using where you are placing it and what is the issue. Maybe few screenshots would be helpful to understand your issue.

#2233215
toolset.jpg

Sorry if it was not clear enough, probably I did not use the correct words, I am talking about joining strings to translate them together when using advanced translation editor (see attached screenshot).

It's working correctly but each time you edit the form and have to update the translation the strings have to be joined again even if they were not modified.

You can test it on hidden link with the exemple form, I actually joined the four sentences of the notification body two by two but if you edit the form, change a label and update the translation, you will see they are not joined anymore.

#2234195

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Ok I reported the test join issue when using the Advance Translation Editor and our Devs will look at it but please note that there no ETA on it when the fix will be proposed.

#2234261

Thanks for the feedback Minesh. Can you please just tell me if the ticket will stay open and I will get notified when it will be fixed or not ?

#2234857

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

I've split the ticket for the text join issue with ATE:
- https://toolset.com/forums/topic/split-cred-form-translation-issues-ate-doesnt-remember-when-it-previously-joined-strings/

You are welcome to mark resolve this ticket. The above ticket will keep open and I'll get in touch with you when I'll have update on it.

#2234875

Well I am sorry Minesh but it seems I am definitely not clear enough. The issue about which I really would like to be updated when fixed is the one with the HTML blocks because it's much more annoying for me than the text join problem.

But, anyway, if you are sure it will be fixed and want me to mark this ticket as resolved, I will of course.

#2235837

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

For HTML block issue, you will require to use workaround for now and there is no ETA on when the fix for this issue made available.

#2235839

I understand that but the same apply to the text join issue so if I you can keep me updated for one it should be the case for both, no ?

#2235841

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

For join issue I already create a new ticket and I'll update you there. For HTML block issue, for this ticket, the issue is at really low priority and I'm not sure when it will have fix. That is why I ask you to close the ticket.

#2235859

Honestly, I do not understand why this issue has lowest priority. Anyway, ticket closed so everybody will be happy, at least on your side. Have a nice weekend.