daavisr

Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)

  • Hello,

    I tried to replicate your environment locally, using WordPress 6.6, PHP version 7.4 and Elementor, but did not see any CPU usage issues. However, as this plugin is a fork of TranslatePress, I found similar issues reported on their forum. It seems the issue comes from some element which is being overdetected and constantly retranslated by plugin. The suggestions are:

    • Remove duplicate entries from database (WEB-T – eTranslation Multilingual -> Advanced tab)
    • Disable Dynamic translation (WEB-T – eTranslation Multilingual -> Advanced tab)
    • Disable Gettext translation (WEB-T – eTranslation Multilingual -> Advanced tab)
    • Identify the HTML node that contains that overdetected text and use Advanced Settings option Exclude from dynamic translation to input the JS/CSS selector for that node. To identify which node/page is affected, you can try:
      • opening different pages, static or dynamic content, see if there is any difference;
      • check browser’s Developer options -> Network tab. If there are requests to etm-ajax.php, click on this request, inspect the content. It should contain details about node ID.
      • Temporarily disable Elementor, check if there is any difference.
    • Check sources bellow, download the suggested add-on for TranslatePress. Then edit the PHP file inside, replacing every ‘trp’ occurrence with ‘etm’. Install this add-on, see if it helps.

    Sources:

    • This reply was modified 4 weeks, 1 day ago by daavisr.
    daavisr

    (@daavisr)

    Hi!

    Can you describe the issue a bit more – is the page always partially translated or just on the first time loading it? Are you using eTranslation as MT provider?

    As the plugin depends on external MT service (e.g. eTranslation), it has a translation timeout built in, so that page is still loaded in case if MT service is not working or is very slow. In such cases page will be translated partially or not at all. When plugin receives translations from eTranslation, it will update them in background and they will be loaded on the next page refresh. The default value for this timeout is 10s. You can increase this timeout (or disable it by setting its value to 0) in Advanced settings -> eTranslation timeout.

    I checked the link you provided, and it seems that everything is translated now. If there are more issues with the plugin, please let us know.

    • This reply was modified 1 month ago by daavisr.

    Hi!

    Thank you for reporting this issue. Unfortunately, I was not able to replicate it on local environment. I do see a little higher CPU usage when the plugin is translating text, which is expected. But after translation, CPU usage goes back to normal. Can you give more details of your specific environment:

    • WordPress version;
    • PHP version;
    • MySQL version;
    • Shared hosting provider name/plan;
    • List of other plugins used in the website?

    Thread Starter daavisr

    (@daavisr)

    Forgot to mention – I am using TranslatePress latest (2.7.6) version.

    Hi, Leo!

    For eTranslation integration to work, it needs to be able to send translations back (HTTP POST) to this route: {{WEBSITE_URL}}/wp-json/etranslation/v1/document/destination/123, in this case: https://bloodpressure.me/wp-json/etranslation/v1/document/destination/123.

    I have tested making such request to your website, and it returns error message “No route was found matching the URL and request method.” Looking at this issue online, there could be multiple causes and ways to solve it:


    The message usually indicates that the REST API on your site is not working as expected. This might be due to a conflict with another plugin or the currently active template. You could try disabling the other plugins one by one and see if this would resolve the issue. Restrictive .htaccess rules may also be responsible for this behavior so we recommend carefully inspecting any existing .htaccess files.

    @dimodi

    Please try the suggestions mentioned and make sure other plugins or themes are not interfering with REST API access.

    Best regards,

    Davis

Viewing 5 replies - 1 through 5 (of 5 total)