• Resolved birtakimseyler

    (@birtakimseyler)


    Hi there,

    You said in another topic that the way TP works right now it detects every char available on the website and parses them.

    For huge websites, it meanshuge database rows of TP and cause translated pages very very slow. It detect every single unnecessary characters also. And exclude selectors also doesn`t help. I filled every single classnames but it still parsing and no idea where that characteres comes from.

    Is there any way to disable parsing entire webpage?

    Thank you!

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

    (@alexcozmoslabs)

    Our plugin needs to parse the entire HTML of a page in order to serve translations, so it can be memory intensive.
    But it usually doesn’t impact speed loading times and you can also cache translated pages, in which case they shouldn’t be processed by PHP at all.
    We recommend you use a caching plugin. Cached pages are not processed on every page load. TranslatePress can be resource intensive with large pages, but it depends on how much html content there is on one page.

    Also, you should check if you have duplicate entries in your database. You can use the Remove duplicate rows option from TP Settings –> Advanced tab –> Debug section to clear them.
    Otherwise, try to disable the gettext translation using the Disable translation for gettext strings option from TP Settings –> Advanced tab –> Exlcude strings section. One reason may be that you could have many gettext strings translated on your site.

    Regarding how you can exclude a page completely from being processed by TP, you can exclude it using the Do not translate certain paths feature in TP Settings –> Advanced tab –> Exclude strings section

    Thread Starter birtakimseyler

    (@birtakimseyler)

    Thanks for reply.
    I exclude all html contents after <body>. It should disable entire content but somehow translatepress still detected somewhere characters and parse them. Some of parsed strings totally useless it parses also url addresses or paths. I would like to make it simply totally disabled. In my case I don′t need it. Is there any function to disable parsing strings? exclude options doesn′t help. It still find somewhere strings to parse it and no idea where.

    Plugin Support Alex

    (@alexcozmoslabs)

    Could you please let me know exactly what did you exclude? Also, please send me the link to the page where strings are still processed.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Disable parsing every single characters’ is closed to new replies.