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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 14:00 9:00 – 14:00 9:00 – 14:00 9:00 – 14:00 9:00 – 14:00 -
- 15:00 – 18:00 15:00 – 18:00 15:00 – 18:00 15:00 – 18:00 15:00 – 18:00 -

Supporter timezone: Asia/Dhaka (GMT+06:00)

This topic contains 5 replies, has 1 voice.

Last updated by Prosenjit Barman 2 months, 3 weeks ago.

Assisted by: Prosenjit Barman.

Author Posts
November 15, 2024 at 2:28 am #16405501

charleneR-2

Background of the issue:
I am trying to translate the text in a form that is loaded with a shortcode on a page of my site hidden link.

Symptoms:
I don't know where to look for documentation on translating text in forms loaded with shortcodes.

Questions:
How do I translate the text in the form that the shortcode displays?

November 15, 2024 at 2:32 am #16405577

charleneR-2

In this documentation, https://wpml.org/documentation/support/language-configuration-files/translate-custom-shortcodes-with-wpml/. I see that each language will need to use the number in the shortcode that corresponds with that language. I don't know where or how to find which numbers to use for this shortcode because the english shortcode does not have a number. [yith_ywraq_request_quote]
The original language page with messed up versions in other languages is: hidden link

November 18, 2024 at 7:27 am #16413004

Prosenjit Barman
Supporter

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hi There!
Thanks for contacting WPML Support. Sorry for the delay in responding due to the weekend.

I understand your concern. Upon closely reviewing the form, I noticed that the default form from the "YITH WooCommerce Request a Quote" plugin is being displayed on the frontend. if translation support is added in the Form strings, you should be able to translate the form from string translation. Please follow the steps below.

- Please go to "WPML > Theme and Plugins Localization"
- Select the "YITH WooCommerce Request a Quote" plugin and scan the plugin for strings.
- Once the Scaan is completed, go to "WPML > String Translation"
- Search for the String that you want to translate. If that appears in the result, add the translation by clicking the "+" icon.
- If you're not seeing the string in the list, please consider following the instructions outlined in this guide: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/

I hope the information above will help in solving the issue. Feel free to let me know if you need further clarification or assistance. I'll be happy to help.

Best regards,
Prosenjit

November 20, 2024 at 11:14 pm #16426771

charleneR-2

I have a question while looking at the WPML > String Translation page - Some of the items have a blue document icon and some do not. Rolling over it says "view in source". Can you briefly tell me why there is a difference. Also, I only want to translate the text that appears on the front end and not any of the administrative text. Is there an easy way to know which items those are?

November 20, 2024 at 11:22 pm #16426775

charleneR-2

Also, it appears that none of the strings that are in the Yith request a quote form are listed in the string translation window. Those are the ones I need. For example, the phrase "Send the request" and "First Name", "Last Name" etc. Where can I find those strings?

November 21, 2024 at 4:14 am #16427221

Prosenjit Barman
Supporter

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hi There!

Thank you for the update. I'll do my best to explain.

The blue document icon in the WPML > String Translation page indicates strings that are linked to a specific source, such as a plugin, theme, or widget. Hovering over the icon and seeing "view in source" means that clicking it will take you to the page or area where that string is used. This makes it easier to locate and understand the context of those strings.

Why Some Items Have the Icon and Others Don’t:

- With Blue Icon: These strings are registered by WPML from a source that WPML recognizes and can link to directly, such as a specific theme, plugin, or widget.

- Without Blue Icon: These are strings that WPML couldn't associate with a specific source or location. They might be custom-added strings or administrative strings that aren’t tied to any particular frontend element.

To focus on translating frontend text and avoid administrative or backend strings, skip strings under the `admin_texts` domains, as these typically pertain to settings or backend options. Instead, copy the specific text you want to translate from the frontend and search for it in the String Translation section. If it appears in the results, translate only that particular string. This is the only possible way to identify and translate the frontend strings.

Regarding the missing strings: As mentioned in the YITH Requests a Quote documentation, scanning the plugin is necessary for the strings to appear in String Translation. Could you confirm if you’ve scanned the plugin by following the steps provided in my earlier message?

It's also possible that those strings have been recognized but not registered yet for translation. Please try the following steps:
- WPML > String Translation
- Click on the blue link at the bottom of the page: "Translate texts in admin screens »"
- Look for the strings you want to translate. Here you should find all strings associated with your theme/plugin options.
- If you find the string, check the checkbox for the string.
- Click on the button "Add to string translation" button.

Now, all your selected strings should appear in the String Translation panel for translation.

I hope this explanation clears things up for you. If you have any further questions or need additional clarification, feel free to reach out. I'm here to help!

Best regards,
Prosenjit

The topic ‘[Closed] content of a page that is both text and a form loaded with shortcode’ is closed to new replies.