Generated invoice contains

  • Resolved kstavrov

    (@kstavrov)


    2 weeks ago

    Hello,

    I have a WordPress website using TranslatePress.

    • Default language: Bulgarian
    • Secondary language: English

    Invoices are generated automatically by the Bulgarisation for WooCommerce Pro plugin (version 2.7.1).

    Everything works correctly for orders placed in Bulgarian. The generated PDF invoices are displayed normally.

    However, when an order is placed in English, the generated PDF invoice contains many strange strings/symbols (TranslatePress markers) throughout the document instead of clean text.

    I have already tried excluding the invoice URLs and disabling translation for the relevant strings, but the problem still occurs.

    My questions are:

    1. Is there a recommended way to prevent TranslatePress from injecting its translation markers into automatically generated PDF invoices?
    2. Is it possible to completely exclude these PDF documents from TranslatePress processing?
    3. Has anyone experienced a similar issue with PDF documents generated by third-party plugins?

    The invoices themselves are generated by Bulgarisation for WooCommerce Pro, not by TranslatePress.

    Any advice 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)
  • Plugin Support Alex

    (@alexcozmoslabs)

    1 week, 5 days ago

    Hello,

    Thank you for reaching out.

    First, TranslatePress is fully compatible with WooCommerce’s core email functionality. However, third-party plugins that extend WooCommerce by adding custom functionality, such as PDF invoice generation, can sometimes introduce unexpected compatibility issues.

    Regarding your issue, from your description it appears that the translations are breaking only in the translated language. Most likely, the affected text consists of gettext strings coming from the Bulgarisation for WooCommerce Pro plugin.

    We recommend checking whether those strings (in the defautl language form) are available in the Translation Editor —> String Translation Interface and excluding their text domain using the Exclude Gettext Strings feature from TP Settings —> Advanced tab —> Exclude strings&pages section.

    Leave the domain textbox empty first. This should get rid of the #trpst wrappings. If not, please add the string with domain name in the exclusion zone, and a new field also with only the domain, and check again. Please, clear your cache to avoid version overlaps.


    Best Regards,

    Thread Starter kstavrov

    (@kstavrov)

    1 week, 4 days ago

    Dear Alex,

    Thanks for you reply. Just for information with a pro version and AI translation is it possible for these gettext strings to be translated automatically on genereting the invoice?

    Thanks in advance!

    Plugin Support Alex

    (@alexcozmoslabs)

    1 week, 4 days ago

    Hi,

    Yes, these strings should be translatable.
    However, pelasenotice that email translation is fully integrated with core WooCommerce. Third party plugins may require a custom integration for TranslatePress to detect and translate all the strings correctly.

    We have documentation available that explains how third-party plugins can add compatibility with TranslatePress if needed.

    Thread Starter kstavrov

    (@kstavrov)

    5 days, 2 hours ago

    Hello again,

    So I got the personal version of TP and however these strings were translated already. I can see that in the invoice the text is also translated, but around it you can notice random stuff like “!trpst#trp-gettext data-trpgettextoriginal=5153#!trpen”.

    Please check the image attached: https://ibb.co/Z1tgKdq3

    Regards!

    Plugin Support Alex

    (@alexcozmoslabs)

    4 days, 8 hours ago

    Hi,

    As I specified in this thread as well, most of the time, these broken strings appear because of a conflict with other plugins or combinations of plugins. Due to the vast size of the WP market, these issues are difficult to control.
    What you can do in this situation is to identify the original string, the strings from the default language that becomes broken in the additional language, and add them in the Exclude Gettext String feature from TP Settings –> Advanced tab –> Exclude section.

    Leave the domain textbox empty first (the domain name of the string can be found in parenthesis below the actual string when you select it in the list of strings from Translation Editor, or directly when you search for the string in String Translation Interface).


    This should get rid of the #trpst wrappings. If not, please add the text with domain name in the exclusion zone, and a new field also with only the domain, and check again. Please, clear your cache to avoid version overlaps.

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

You must be logged in to reply to this topic.