‘This String is Not Ready for Translation Yet’ Error”

  • Resolved minamt

    (@minamt)


    1 month ago

    Hi,
    I’m encountering an issue with the visual translation editor. Whenever I select a string, I receive the message: “This string is not ready for translation yet. Try again in a moment…” and am unable to proceed with translating the text.

    Here are the troubleshooting steps I’ve already tried:

    1. Disabled All Plugins except TranslatePress to rule out any plugin conflicts.
    2. Switched to the Default WordPress Theme (Twenty Twenty-Four) to check if the theme was causing the issue.
    3. Tried Incognito Mode and a Different Browser to rule out any browser caching or settings interference.
    4. Purged All Caches from both my caching plugin and my browser.

    Despite these efforts, the issue persists. I’d appreciate any guidance on additional steps or configurations that might resolve this.

    Thank you in advance for your support.

    Best regards,

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

    (@alexcozmoslabs)

    Hi,

    Thank you for letting us know.

    Could you please check also the Google Console while running the Translation Editor? What error is rendered there?
    You should also ask your host if there are some server-related restrictions.

    Best Regards,

    Thread Starter minamt

    (@minamt)

    Hi,
    All I’ve found in the console about Translatepress is this message: Notice: TranslatePress trp-ajax request uses fall back to admin ajax.

    Thread Starter minamt

    (@minamt)

    Hi,
    I’ve tried it on another website hosted in the same server, it worked fine.
    in the settings menu it is showing me this error: ” TranslatePress encountered SQL errors. Check out the errors.”
    Here are the errors:

    Why are these errors occuring

    If TranslatePress detects something wrong when executing queries on your database, it may disable the Automatic Translation feature in order to avoid any extra charging by Google/DeepL. Automatic Translation needs to be manually turned on, after you solve the issues.

    The SQL errors detected can occur for various reasons including missing tables, missing permissions for the SQL user to create tables or perform other operations, problems after site migration or changes to SQL server configuration.What you can do in this situationPlan A.

    Go to Settings -> TranslatePress -> General tab and Save Settings. This will regenerate the tables using your current SQL settings. Check if no more errors occur while browsing your website in a translated language. Look at the timestamps of the errors to make sure you are not seeing the old errors. Only the most recent 5 errors are displayed.Plan B.

    If your problem isn’t solved, try the following steps:

    1. Create a backup of your database
    2. Create a copy of each translation table where you encounter errors. You can copy the table within the same database (trp_dictionary_en_us_es_es_COPY for example) — perform this step only if you want to keep the current translations
    3. Remove the trouble tables by executing the DROP function on them
    4. Go to Settings -> TranslatePress -> General tab and Save Settings. This will regenerate the tables using your current SQL server.
    5. Copy the relevant content from the duplicated tables (trp_dictionary_en_us_es_es_COPY for example) in the newly generated table (trp_dictionary_en_us_es_es) — perform this step only if you want to keep the current translations
    6. Test it to see if everything is working. If something went wrong, you can restore the backup that you’ve made at the first step. Check if no more errors occur while browsing your website in a translated language. Look at the timestamps of the errors to make sure you are not seeing the old errors. Only the most recent 5 errors are displayed.

    Plan C.

    If your problem still isn’t solved, try asking your hosting about your errors. The most common issue is missing permissions for the SQL user, such as the Create Tables permission.Logged errors

    These are the most recent 5 errors logged by TranslatePress:1last_errorUnknown character set: ‘utf’disable_automatic_translationsYesurlhttps://mywebsite.pro/wp-admin/options.phpdetailsError creating gettext strings tableslast_queryCREATE TABLE wp_trp_gettext_ar( id bigint(20) AUTO_INCREMENT NOT NULL PRIMARY KEY, original longtext NOT NULL, translated longtext, domain longtext, status int(20), original_id bigint(20), plural_form int(20), UNIQUE KEY id (id) ) DEFAULT CHARACTER SET utfdate_time2024-11-03 10:46:40timestamp17306308002last_errordisable_automatic_translationsYesurlhttps://mywebsite.pro/wp-admin/options.phpdetailsError creating regular strings tableslast_querySHOW TABLES LIKE ‘wp_trp_dictionary_en_us_ar’date_time2024-11-03 10:46:40timestamp17306308003last_errorTable ‘chroua_reporg.wp_trp_dictionary_en_us_ar’ doesn’t existdisable_automatic_translationsYesurlhttps://mywebsite.pro/wp-admin/options.phpdetailsError creating regular tableslast_queryCREATE INDEX block_type ON wp_trp_dictionary_en_us_ar (block_type);date_time2024-11-03 10:46:40timestamp17306308004last_errorUnknown character set: ‘utf’disable_automatic_translationsYesurlhttps://mywebsite.pro/wp-admin/options.phpdetailsError creating gettext strings tableslast_queryCREATE TABLE wp_trp_gettext_en_us( id bigint(20) AUTO_INCREMENT NOT NULL PRIMARY KEY, original longtext NOT NULL, translated longtext, domain longtext, status int(20), original_id bigint(20), plural_form int(20), UNIQUE KEY id (id) ) DEFAULT CHARACTER SET utfdate_time2024-11-03 10:46:40timestamp17306308005last_errorTable ‘chroua_reporg.wp_trp_dictionary_en_us_fr_fr’ doesn’t existdisable_automatic_translationsYesurlhttps://mywebsite.pro/wp-admin/admin-ajax.phpdetailsError running get_string_rows()last_querySELECT id, original, translated, status, block_type FROM wp_trp_dictionary_en_us_fr_fr WHERE original IN ( ‘Video Placeholder’ )date_time2024-11-03 10:45:19timestamp1730630719

    • This reply was modified 3 weeks, 4 days ago by minamt.
    Plugin Support Alex

    (@alexcozmoslabs)

    Hi,

    Could you confirm you are using the latest version for our plugin? If so, but the issue persists, please follow the mentioned debugging steps from the error message and let me know. See if the process will help.

    Plugin Support Alex

    (@alexcozmoslabs)

    Hi,

    Since 5 days have already passed without a reply we will be marking this topic as “Resolved”. Do not hesitate to open another ticket if you still need support regarding this topic.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.