• Resolved loyukfai

    (@loyukfai)


    1. I’ve noticed that wp_trp_dictionary_* kept increasing in size, I manually delete entries which are “untranslated” but it’s cumbersome to do it manually from time to time.

    My use case is that, I just need to translate strings once, and subsequent added strings, including user-generated ones, such as those from reviews and comments, need not to be translated.

    Sometimes, I find even URLs are added to these tables.

    Is there anyway to stop TP from adding strings to the tables?

    2. Besides, I don’t translate gettext strings, but there are still 3 wp_trp_gettext tables, I assume they’re from the time whereas I haven’t enabled the “Disable translation for gettext strings” option.

    Is it safe for me to delete these 3 tables now?

    3. Finally, my wp_trp_original_strings is quite small (112 KiB) but wp_trp_original_meta is big (336 KiB). Why is that?

    Thanks a lot in advance.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Cristian Antohe

    (@sareiodata)

    Hello,

    1. TranslatePress usually detects all possible strings. That’s why you see those untranslated strings in the database. It’s usually not an issue and does not impact the functionality of the site. However, you can exclude selectors from translation or add data-no-translation to HTML elements you don’t want translated. TranslatePress -> Settings -> Advanced ->Exclude strings
    2. If you deleted them, they will get regenerated when you save settings. Again, it’s best to simply ignore them.
    3. It usually depends on your website, both are quite small and working as expected form what I can tell. TranslatePress can use lots of database records. This is expected.

    Best Regards,

    Thread Starter loyukfai

    (@loyukfai)

    Thanks a lot for your explanation.

    Is it possible to disable collecting new strings until needed?

    Cheers.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Database Size Maintenance’ is closed to new replies.