• Resolved Paul

    (@paulschiretz)


    Hi there,

    Since the last update, strings show up as ‘undefined’ in the visual translation editor. if i take a look at the gettext editor i can translate strings as usual.

    I do get a js error in the console:

    TypeError: Cannot read properties of undefined (reading 'de_DE')
        at language-boxes.vue:164:1
        at Array.forEach (<anonymous>)
        at s.updateLanguages (language-boxes.vue:163:1)
        at s.selectedIndexesArray (language-boxes.vue:125:1)
        at ir (vue.common.prod.js:11:20764)
        at Lr.run (vue.common.prod.js:11:27412)
        at Yt (vue.common.prod.js:11:17908)
        at Array.<anonymous> (vue.common.prod.js:11:21776)
        at dr (vue.common.prod.js:11:21208)


    I tried on a staging setup all seems to be good there.
    Any ideas?

    All the best,
    Paul

    • This topic was modified 3 years, 5 months ago by Paul.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Anghel Emanuel

    (@anghelemanuel99)

    Hello there,

    Thank you for letting us know about this!

    Since this looks a lot like a conflict with some other code, the first/next recommended step is the conflict test (ideally in a staging environment):

    ​​Briefly disable all other plugins and enable the default Twenty Twenty-One theme. Please also disable all add-ons. If this fixes the problem, as it probably will, enable everything one by one, checking each time to see when the problem returns.

    Please let us know when you find the conflict so that we can take a look and see what we can do about it.

    Kind Regards,

    Thread Starter Paul

    (@paulschiretz)

    Hi, as the site is a webshop and you know it’s holiday season i couldn’t to the test on the live site. But i replicated the test on a staging site and it seems to be working fine… the only plugin i haven’t configured in my test enviroment was sitekit from google.

    what i get from the error message is that some node couldn’t be read in your vue js script, so i guess your trying to parse something that has been changed by some plugin or theme. From the error, can you point me to what node might be missing or changed?

    What is really odd is i can edit strings that come from my theme just fine but string from plugins for instance woocommerce just give me the error and undefined as a result…

    Any pointers are welcome, i’m quiet savy with code so also happy to fire up a debugger…

    Thread Starter Paul

    (@paulschiretz)

    Hi again, @anghelemanuel99

    I searched a bit further and it is definitly not a plugin conflict, i now managed to reach the same result without anything installed except translatepress. It seems my database tables have somehow become unreadable for the visual translation editor cause if i start from scratch it works but as soon as i import my database the undefined strings start popping up. BUT the translations and the gettext editor just work fine!

    So how to we go about this is there any way i can recreate the database tables and only import my translations from a backup? Or are you able to repair the tables or the Visual Editor if i send an sql dump?

    All the best,
    Paul

    Thread Starter Paul

    (@paulschiretz)

    Hi Again @anghelemanuel99 solved the issue myself. Sorry to bother you.

    Translatepress added some tables in the db after 2.3.7 and i changed hosting providers some time ago so the tables had a different String COLLATION utf8mb4_unicode_520_ci and utf8mb4_unicode_ci therefore the db update did fail to generate the missing original_Ids.

    In case anybody needs to solve something similar:

    Downgrade to 2.3.7, set the COLLATION in phpmyadmin or similar. upgrade to the newest version did the trick. ALWAYS KEEP A BACKUP OF YOUR DB!

    All the best,
    Paul

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘translation editor not working’ is closed to new replies.