Support » Plugin: Transposh WordPress Translation » Stored Translations

  • Resolved steeleweed


    I installed this plugin and set it for English, French, German, Spanish and Russian. My hosing company’s “site monitor” reported “malware” and gave me a link to what the tech called a ‘deformed’ page. It was the Russian translation of one of the blog posts. I found 25 posts with the Russian translations were stored in the database.

    Why were translated versions stored in the DB instead of the posts being translated on request?

    here were no translations into French, German or Spanish, and I had previously translated into each language to make sure everything was working.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Update:
    On this particular site, Russian was the last of the five languages I specified.

    On another site using this plugin, Italian was the last language I specified and that site has 25 posts in the DB translated into Italian.

    Seems we have a pattern here, eh?

    Plugin Author Ofer Wald


    Yes, we have a pattern here, but it is probably not what you think,

    First, when posts are translated, their translations are being saved to the database, not as posts, but in a different table, this plugin is not a javascript on the fly translation solution. It never claimed to be that, and actually it claimed the exact opposite, whatever.

    Second, regarding 25 posts, that are deformed, my guess would be that there is some issue at the tool of your hosting provider. Not that I can really have a clue about what is wrong with it and why, since you have not provided any information about the type of “Deformation”.

    Again, transposh can’t, has no code that can, save posts to your database. I truly suggest you find the correct culprit or provide more useful information.


    Re “Deformation”: Given the paranoia about Russian hacking, I suspect his ‘malware monitor” triggered on the Russian and I imagine the tech did not recognize Russian script and just considered it garbage. If he’d looked at my other site and seen 25 in Italian, he might not have considered that “deformed’ – but his ‘monitor’ might not have triggered on Italian as it did on Russian.

    I understand the translated data is in a ‘different table’, in one website: 25 posts translated to Russian and in the other 25 posts translated to Italian. Your response implies that someone requested at least 25 Russian translations (maybe you only store the last 25?) on one site and 25 Italian translations on the other site. One of these sites is known to a fair number of people, being an archive of a blog that had 1100+ members. The other site is known to only a handful of people. I visit both sites and gotten translations into French, Spanish and German, yet I to not see those translations in your table.

    Plugin Author Ofer Wald


    Hello Again,

    I don’t store 25 posts, because there is no such object as posts, the translation table is rather simple, original string, target language code, translated string, date of translation, source of translation (afair).

    You can’t really have pages translated unless the <prefix>_translations table exists and contain something, unless you are in a really rare situation, with some misconfigured protection on admin_ajax. If you see the posts in the original content, and than they change to a target language and do this everytime this might be the case, but than – how would his tool find translated pages at all?

    Again, not enough information,


    I have inactivated the plugin on my sites and deleted it.
    Your tables are still in the database – the Delete didn’t clean that up.


    Ii it safe for me to delete these two tables Will it break the site?

    Plugin Author Ofer Wald



    Yes, those are the tables, naturally they cannot be removed on deactivation/deletion because it will break a lot more than it will fix.

    Feel free to remove those tables if you decided not to use Transposh


Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Stored Translations’ is closed to new replies.