Plugin Support
Alex
(@alexcozmoslabs)
Hi,
Could you let me know how did you tried excluding the page, kassa?
Also, what error exactly do you encounter after excluding?
Thread Starter
madisk
(@madisk)
and the exact error
“The page isn’t redirecting properly
An error occured during a connection to audiocity.fi.
This problem can sometimes be caused by disabling or refusing to accept cookies”
Firefox
This page isn’t working
audiocity.fi redirected you too many times.
Try clearing your cookies.
ERR_TOO_MANY_REDIRECTS
Chrome
I tried clearing cookies and still same.
https://imgur.com/a/WUngOvK <- how i added the path exclusion
-
This reply was modified 2 years, 11 months ago by
madisk.
Plugin Support
Alex
(@alexcozmoslabs)
Hi,
I’m not a Finnish or Estonian speaker but /kassa/ it’s not your translated slug of the checkout page? If so, you need to know that you have to exlude the slug in default language the exclusion to be taken into account by our plugin.
Thread Starter
madisk
(@madisk)
It’s the same word for ‘checkout’ in both of the languages.
The ‘exclude html element from auto translation’ did the trick luckily.
Now all i need to is to figure out how to remove the /fi language slug from url and im all set.
Plugin Support
Alex
(@alexcozmoslabs)
Hi,
If Finnish is your default language you can disable the Use subdirectory for deafault language option in TP Settings –> General tab.
If is an addional language, the language slug it has to stay in the URL structure due to how our plugin was designed to work.
Kind Regards,
Thread Starter
madisk
(@madisk)
Okey, even if i disabled the part i wanted, it still takes 10 seconds to load the checkout page. Payment gateway dev. says that translatepress is not compatible with with their plugin. (if TP is disabled the page loads fast indeed) but i cant figure out what i need to exclude from translation to make it load fast with it enabled (also cant exclude the page from being translated)
The payment gateway is “MakeCommerce”
Plugin Support
Alex
(@alexcozmoslabs)
Page translation can be CPU intensive. We have to read the entire page as a string and then is transformed it into a big object which is the HTML. That object basically needs to stay in the memory.
The best approach now would be to perform a Database Optimization from Settings –> TranslatePress Settings –> Advanced tab –> Debug. See if this procedure will help.
Another thing you might want to look for, is that we have a listener for Javascript strings that when it detects a text change on the page (say a particular JS script adds a notice), we query the server for a translation.
This ajax call is also fast as it doesn’t go through the normal WordPress ajax, however, it can cause issues when there is a lot of traffic to your website.
The good part is that you can disable this functionality from TranslatePress -> Settings -> Advanced tab –> Disable dynamic translation.
If you want to exclude that page, you can do it by excluding its path with the Do no translate certain paths feature in TP Settings –> Advanced tab –> Exclude strings section.
