Server Side caching doesnt work well with TranslatePress

Any updates? Its a very crucial thing. Thank you

Hi,

Most of the time, these broken strings, #trpst, 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.

Regarding #TRPLINKPROCESSED appearing in the slug:
1. Why does the #TRPLINKPROCESSED still appear?
– They appear because we failed to complete the stripping.
– There are some themes (themify — has caching). It caches the page_id. We don’t change the page_id and it’s possible that the page_id is being served. If it was caching on the URL it would take into account the language parameter. Solution: removed the cache from the theme.
2. What works?
– Compatibility test — there are other plugins that read HTML like TP and it’s possible to break our code, and those will throw #trpgetext and #trplinkprocessed will appear.

Hello @alexcozmoslabs ,

You are giving a generic explanation without even trying testing the links i gave you in the first post. This is unacceptable. The solution you provide is completely irrelevant with the issue im having.

If you had tested my links, you should have known that the real issue is that when im in greek language and press the home button, it reverts back to the english one. This is have nothing to do with other plugin conflicts. This is due to compatibility issues with the NGINX cache. I as saw in the forum, there are similar issues.

Please provide a solution.

• This reply was modified 1 month, 3 weeks ago by paourissi.

Hi,

Just a reminder that this is a free forum with voluntary support. We’re doing our best to help whenever and however we can, so it wouldn’t be fair to judge the way we assist others.

Please understand, even though they are general recommendations, they apply specifically to the reported problem. This type of bug is most often generated by compatibility with other codes, so compatibility testing is mandatory in this case.

Best Regards,

Hello @alexcozmoslabs ,

I really appreciate your help but DO NOT suggest solutions without even bother seeing the problem because its a waste of your time and mine.

I have disabled every plugin and the problem remains BECAUSE its a cache problem. You can check it if you actually click on the links.

I suggest you close this thread and i go to another multilanguage plugin with a greater suppport unless you have a real solution.

Thank you.

Hi,

We don’t have any cache system implemented in our plugin. The fact those links are cached, it has to do with factors external to our plugin.
We can look into it in detail if you want, but you will have to open a ticket directly with us on the site, https://translatepress.com/support/ask-a-presale-question/.