TranslatePress incompatible with WP Grid Builder?

  • Resolved Serefor

    (@serefor)


    3 months, 3 weeks ago

    Hello,

    I have a problem with TranslatePress and WP Grid Builder filters.

    I use WP Grid Builder to display a column of filters on WooCommerce category pages.

    In the main language (Spanish) everything works correctly.

    When switching to the secondary language (Portuguese) and applying some filter some text strings appear broken with this look:

    #!trpst#trp-gettext data-trpgettextoriginal=4858#!trpen

    Screenshot: https://www.dropbox.com/scl/fi/qednxhnln3zc02a9vxcj4/Captura-de-pantalla-2024-08-05-180231.png?rlkey=61260shg7mz0lzbvc054fmmzl&st=zsodn7k6&dl=0

    I have tried activating the debugging and diagnostics options in the “Advanced” tab of TranslatePress but have had no luck with any of them.

    I’ve also tried activating the visual editor on this page and it doesn’t load, so I can’t edit those strings either.

    I have tested with the Health Check & Troubleshotting plugin, leaving only Breakdance Builder (so I can have the template where it fails), TranslatePress, WP Grid Builder and WooCommerce and the problem is the same, I rule out an incompatibility between other plugins, if it exists it has to be between these 4.

    I would appreciate any help with this.

    Thank you very much in advance!

    • This topic was modified 3 months, 3 weeks ago by Serefor.
    • This topic was modified 3 months, 3 weeks ago by Serefor.
    • This topic was modified 3 months, 3 weeks ago by Steven Stern (sterndata).

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Alex

    (@alexcozmoslabs)

    Hi,

    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 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 domain, and a new field also with only the domain, and check again. Please, clear your cache to avoid versions overlapping.


    Kind Regards,


    Thread Starter Serefor

    (@serefor)

    Hi Alex,

    Thanks for your reply.

    I was able to exclude the problematic strings and fix the problem.

    I didn’t understand why those strings weren’t working properly when the rest of the site was, but the important thing is that it’s fixed.

    Thanks a lot for your help.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.