Delinstalling and Removing languages won’t work

  • Resolved toremo

    (@toremo)


    4 years, 5 months ago

    Hi

    when we deinstall the plugin the languages don’t show up anymore but the tables dd not get cleaned up and all translation strings are still in the database. Isn’t there a propper way to clean up all those translations which aren’t needed anymore after the plugin had been deinstalled i.e. because the customer likes to use i.e. another plugin or he simply don’t need a translation anymore.

    Could you please explain how to REMOVE a language so it can be replaced with another language. That is another scenario which causes problems.
    1. The site by default template contains 2 languages (so we can show that the templates are translatable
    2. The customer is native in another region (Vietnam) and needs to change the default language (English in our case) and mostly he also needs to change the second language – (in our case by default spanish) – to Chinese or sometimes English. As the plugin provides only 2 languages we need to delete the default ones from the template and clean up those strings.

    HOW? They seem to be still in the database after we change the languages.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter toremo

    (@toremo)

    I read meanwhile that the problem with losing translations got solved in Pro version but that does not seem to be correct as we tested it today.

    https://youtu.be/WC2ftBOH8CE

    1. You can translate any string and text splitted up in paragraphs and everything gets stored in 5 tables inside the database. While a divi site instantly produces about nearly 400kb and the wordpress Gutenberg only site ony about 90 kb.

    When translating stings in a multisite all translations get storeed in the subsite directory, Unfortunately there is no way until now to build up an own translation repository so that people working with multiple sites in a multisite could easily use the main translation repository and then only copy the necessary strings by an export of a subsite to a subsite.That would even make the problem with losing the translations even with other plugins as this is always a headache and having a centralized translation repository in a multisite or a network of wordpress sites which connect to the users repository in one main site via API. (just an idea).

    But without that you will have to redo all translations where you made corrections. Besides that sometimes you have translations which have to stay like they are even you have to change at one place the original wording or vice vers you have a wording with two or more meanings and it needs to get translated multiple times differently. That is simply not working!

    Example original German

    Wir teilen mit
    1. Person 1
    2. Person 2
    3. Dem Personal

    translated to English

    We share with
    1. person 1
    2. person 2
    3. Dem Personal

    Wir teilen mit
    1. Der Brief ist nie angekommen
    2. Das Telefon ging nicht

    We will tell you
    1. The letter never arrived
    2. The telephone was broken.

    Google has problems with this too if you set the paragraphs like shown.

    – – – And there are many more examples like that.

    I like the way to create in Frontend fast a new translation but losing it means loing time and creating lots of headaches and usually in texts there are mistakes which you discover first when you have actually already finished the translations and by looking over the original again. Suddenly you switch a word (better grammar) or you change a word for better SEO – and your translation is gone – bye bye – unless you nw still the original string as only than you will be able to recover the lost translation. On the other side a Translation once done can be reused all over the site without need to translate it again – but that is only true if no space, no sign actually no other sign had been added to the string – it must be 100% identical.

    A real game changer it woudl be if it could be used all over a multisite installation by defining one page (not Page 1 as that often gets already used for other stuff) so that you can create your own translation repository for you and for your customers i.e. even by getting and collecting all those strings fro translation services as long as they are free (on a regular base for example)

    A merging tool would also be great – i.e a way that you will be able to merge all trabslations into one database of a defined subsite or “Master Site – wenn single translations – while in Multisites it would be easy to merge in single installations the connection needs to be done via API. But that would really be a game changer as you could build up your own translation repository.

    I like that it is susing only 5 tables as i.e. WPML uses tons of tables and it is always a headache too to move those tables to new domains or new sites etc. but the main point of having translations is that those translations need to be correct!!

    I hope you can fix that until 1.7.6 – Thanks!we tested 1.7.5

    • This reply was modified 4 years, 5 months ago by toremo.
    Thread Starter toremo

    (@toremo)

    Any News? or a feedback if a fix is coming?

    Hello,

    We deeply apologize for the delayed response.

    There has been a great load on our support team in the past few days, but such a long reply time is very uncommon.


    {Q}     when we deinstall the plugin the languages don’t show up anymore but the tables dd not get cleaned up and all translation strings are still in the database. Isn’t there a propper way to clean up all those translations which aren’t needed anymore after the plugin had been deinstalled i.e. because the customer likes to use i.e. another plugin or he simply don’t need a translation anymore.
    {A} The ability to delete everything (database included ) is a tracked feature and will be available in the future versions of TranslatePress – but, as there are other features more requested that require prioritization??, I can’t give you a timeframe for when will this be implemented.

    Thank you for understanding.

    If you want to change the language you can easily do that from the Translatepress general settings. this way you will have 2 new tables with the new language in your db. and if in the future you want to go back. you’ll have your already made translation ready to go.

    But if you want to delete the table from a particular language you will need to go to the database and search for trp_

    As for the suggestions, we really appreciate them, if enough users will ask for them surely it will be a feature.

    Kind regards,

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Delinstalling and Removing languages won’t work’ is closed to new replies.