Can you please ask the developers to clear the glossary again. We took the CSV file that you provided and of the 2807 rows, 2600+ rows actually uploaded into the system. However upon further inspection the CSV file was incorrect as there are Chinese glossary items that are in English.
Please confirm when the glossary can be cleared again. We'd like it done as soon as possible.
Thanks in advance.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
Our devs are deleting it 🙂 you should see it cleared in a few hours, though. I'm sorry it couldn't be faster.
By the way we're already testing the fix for the issues where the import and update is not working correctly it should be fixed for your site very soon (In a week, probably).
Thanks Alejandro,
We had issues connecting the credits from our hidden link and hidden link yesterday around this time, we eventually got it reconnected but I'm still seeing the glossary with 2600+ items in it. Did our connection of the two sites for the shared credits bring back the glossary?
Or was the action still pending from your dev team?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
We checked 3 times between yesterday and today and found out that the glossary entries were all deleted, we thought you had deleted them manually this time.
You mentioned that "... we eventually got it reconnected" what do you mean by that? they can only be disconnected if someone manually did it from your site, since we can at most connect them, never disconnect them :(.
At this point, can you please go to WPML > Support > Troubleshooting and send me the Automatic Translation ID, please so I can locate the correct place where you have your glossary, so we can delete it.
Ok just checking back in on this, but it looks like our glossary on both sites are cleared out now. I'm not reading any data in there now.
Previously we cloned production to QA, and through the confusing wizard screens on QA, we some how had QA connected twice to production in the "connected sites" feature. (Documented in our bug here: https://wpml.org/forums/topic/multiple-connected-sites-created-when-cloning-a-staging-environment/). We deleted both QA connections and had to create a new QA site key before we were able to reconnect the two sites (QA and production) so that they would share auto translation credits. That's what I meant by reconnecting them. Should I be concerned the production site is still being read as inactive?
Our automatic translation id for production is:
0c6173be-2de0-42d1-975b-03b0e24c5873#NhVM4r1VJwqTNnA6Psc9Qwtt
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
about the site that appears as inactive, on our end it seems the latest migration was to a QA site on july 24th, this tells me that when the migration banner appeared, you selected the "no" option (At one time, at least).
Anyways, linking it back with the QA will make it so all those domains will share the same information so you shouldn't have issues with it,
We are going to improve this workflow by WPML 4.8 to make it easier to understand but we'll also take care of part of the workflow so it should be easier to handle as well :).
We're also testing many things on the glossary front so you'll be able to work better, faster and with an easier interface.
OK sounds good.
You can close this ticket as we've since recreated our site keys and credits are working as expected. Additionally the glossary is confirmed to be cleared out on our production and QA systems.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Ok!
Just so you know, between tomorrow and Next month we'll release wpml 4.8 Beta version.
The actual release should be more or less in the second week of august and that version will contain a lot of changes to the glossary (Improved import/export/update and also better deletion of entries, including sorting and bulk delete but these 2 might come a bit later, in that month).
Just so you're aware since you'll probably find that useful 🙂
