Button glitches and unable to Translate

  • Resolved rhyd123

    (@rhyd123)


    10 months, 3 weeks ago

    Hello,

    So I’ve recently been working on a website that has the free version of this plug in installed. Worked like a charm until I made the website live. The original and default language of the website is Welsh, and the desired translated text were to be in English. This website also uses plug ins such as WooCommerce and Elementor and this plug in had no issues.

    However, when the website was made live, the website refused to translate to english and all the button such as “Add to cart” were converted to a code-like text, saying stuff like “gettext” etc. I have since deleted this plugin, as well as attempted to try different methods in hope of fixing this, such as clearing cache and cookies. I am currently in the process of developing the translator again, but was wondering what could have been the potential cause, and what workarounds would have worked. Any response would be greatly appreciated. Thank you.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • detailscloud

    (@detailscloud)

    10 months, 3 weeks ago

    I am facing the same problem in all the sites where the plugin is installed, codes like #!trpst#trp-gettext data-trpgettextoriginal=4576#!trpen#Expired#!trpst#/trp-gettext#!trpen# appear and the source language text appears in both interfaces, meaning the translated text does not appear

    detailscloud

    (@detailscloud)

    10 months, 3 weeks ago

    The strange thing is that there has been no departure for a whole day on this ticket.

    Plugin Support Anca

    (@ancavictoria)

    10 months, 3 weeks ago

    Hello,

    Could you please let me know if you are using the JetElements for Elementor plugin from Crocoblock?
    If so, this is a known bug introduced in their latest version, which is expected to be resolved soon by their team.
    In the meantime, it is necessary to roll back to a previous version of their plugin.

    If you are not using this plugin, you need to identify the original string, the strings from the default language that become broken in the additional language, and add them in the Exclude Gettext String feature from TranslatePress Settings → Advanced tab → Exclude strings & pages. Leave the domain textbox empty first (the domain can be found in parenthesis below the actual string when you select it in the list of strings from Translation Editor). This should get rid of the #trpst wrappings. If not, please add the text with the domain, and a new field also with only the domain, and check again.
    Please, clear your cache to avoid versions overlapping.

    You can add woocommerce in the domain field without adding any strings and check if the issue persists.

    Kind regards,

    Anca

    Thread Starter rhyd123

    (@rhyd123)

    10 months, 3 weeks ago

    Hello,

    Thank you for the reply. The main plug-ins that I am using for my website are: Blocksy Companion, Code snippets, Elementor, Essentials, Jetpack, Performance, Starter Templates, Templately, WooCommerce. Hope any of these helps.

    Would you mind further explaining the steps required to complete the second debug in your response. I’m rather new to this and would prefer maybe a more clear, step-by-step guide for myself to follow. I can find the mentioned page, however I am unsure as to what exactly do I need to fill in? Do I need to manually put in every translation for the website or am I understanding it incorrectly? If you could explain, either way, what I need to do that would be most appreciated.

    Thank you very much.

    Plugin Support Anca

    (@ancavictoria)

    10 months, 2 weeks ago

    Hello,

    It is necessary to exclude from gettext the original language strings that appear broken in the additional language.
    To do this, go to TranslatePress → Advanced Settings → Exclude strings & pages → Exclude Gettext Strings, and add each affected string one by one.
    Make sure to click the Add button after each entry and save the changes.

    If multiple strings are affected and they are all generated by the same plugin, you can exclude the entire gettext domain of that plugin.

    In your case, you mentioned that the #trpst warnings appear for the Add to cart button. You can either exclude this specific string or exclude the gettext domain of the plugin generating it (woocommerce), as shown in the screenshot below:

    Please, clear your cache to avoid versions overlapping.

    Kind regards,

    Anca

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Button glitches and unable to Translate’ is closed to new replies.

Tags