• Resolved tobiaswinter

    (@tobiaswinter)


    Currently, Translatepress is incompatible with the Glossary Plugin by codeat.

    Problem:
    On translated pages, Glossary terms will never be found.

    Cause:
    Glossary uses a secondary Query to obtain all posts of type “glossary” and get the terms to look for using \get_the_title(). Unfortunately, Translatepress adds the filter wrap_with_post_id which adds <trp-post-container data-trp-post-id=’1617′> to the title.

    Workaround:
    “Disable post container tags for post title” in Translatepress’ Advanced settings tab fixes this. But I don’t know if I break other things if I leave this enabled?

    Fix:
    I hope Translatepress will implement a fix for that. More information here: Detailed description

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

    (@alexcozmoslabs)

    Hi,

    Thank you for reporting this.

    Due to the fact that you are the first user that reports this, from what I know, and also the active installations of the Glossary plugin, plus there is a workaround around this issue, it will not be prioritized.

    Mainly, we prioritize copatibility issues like this, based on the number of requirements from the users. We take your idea into our consideration, but first, we need to prioritize the most required proposals. And also, we have the “Disable post container tags for post title” workaround, which by the way, you can use without worries. just the fact that if you use the search in additional languages it may not take into account titles.

    • This reply was modified 2 years, 10 months ago by Alex.
    Thread Starter tobiaswinter

    (@tobiaswinter)

    Hi @alexcozmoslabs,
    thanks for letting me know. This is perfectly understandable, as I’ve actually other issues with Translatepress with higher priorities.
    Thank you for the information about the effects of the “Disable post container tags for post title” setting. So I know I can use that but I may implement another solution to workaround the issue with glossary.

    Thank you!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Incompatible with Glossary Plugin’ is closed to new replies.