This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is that when the user uses the [wpml-string context="my own context" name="my own stringname"]mystring[/wpml-string] shortcode the context and name attributes don't show up correctly in WPML String Translations. This only happens if they are used in the Visual Editor cell in Layouts.
Solution:
Unfortunately we don't have a solution at this time. However our development team has been aware of this issue and is currently working on fixing this.
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 |
|---|---|---|---|---|---|---|
| - | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | - |
| - | 13:00 – 18:00 | 13:00 – 18:00 | 13:00 – 18:00 | 14:00 – 18:00 | 13:00 – 18:00 | - |
Supporter timezone: America/Jamaica (GMT-05:00)
This topic contains 7 replies, has 2 voices.
Last updated by 6 years, 8 months ago.
Assisted by: Shane.
Hello,
I'm not sure what you mean with copy and paste, can you please clarify?
I'll also make an attempt to clarify the issue. The translation is actually working per se, but I can't make use of the context and name attributes to the wpml-string shortcode. This makes it hard to find what to translate and I believe that the shortcode attributes were working last year.
Please find attached a screenshot where the top phrase comes from [wpml-string context="my own context 1" name="my own stringname 1"]string 1[/wpml-string] in a Layouts Visual Editor cell. You can also see that the attributes are working fine when the wpml-string shortcode is used in Content templates and Views.
