• Resolved thalakus

    (@thalakus)


    Hello together,
    I’ve seen that my translated homepage (German to English) has in the database entrys like “trp_dictionary_de_de_en_us of 26 MiB
    and “trp_original_strings” of 12 MiB.

    Is there a option in the plugin to clear all NON USED entrys by Translatepress?
    Because when I changed the original text I also changed the translation but the former text is still saved.

    Thank you in advance!
    Best regards

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter thalakus

    (@thalakus)

    Now I checked the trp_dictionary_de_de_en_us and found some things out:

    -1. there are many many entries in the “original” row that aren’t translated – for example guest book entries that I haven’t and won’t translate.

    -2. that there are also older strings from former “crawlings by Translatepress” that don’t exist anymore.

    So my question:
    Is there a good and reliable solution to change that without destroying the whole database?
    Or is it necessary that translatepress gathers all strings on a page.
    And what can I do with the renewed entries, that I have updated but both versions (the old and the new) still lay in the Database?

    Best regards and thank you very much in advance!

    Hello,

    It’s possible that you have duplicate entries in your database. You can use the Remove duplicate rows option from TP Settings –> Advanced tab to clear them.

    There isn’t an option to clear all Non Used entries.

    When you access a page (in a translated language, or using the Translate Page button, TranslatePress gathers all strings that can be translated from that page and those string will be added in the wp_trp_* tables in your database.

    You can delete the old entries if you are no longer using them, but you will have to do this manually. There shouldn’t be two identical strings with different translations so figuring out the old strings shouldn’t be impossible.

    Best regards,
    Cristian

    Thread Starter thalakus

    (@thalakus)

    Hello Christian,
    thank you for your info!

    Should I run all 3 of those options or just one specific?
    Remove duplicate dictionary rows
    Remove duplicate gettext rows
    Remove duplicate original strings

    Best regards
    Lukas

    Hello Lukas,

    You should run all 3 of those, but as specified on that page, make sure to first backup the database.

    Best regards,
    Cristian

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