Background of the issue:
I am trying to import 6848 glossary terms via the importing glossary button from the back end admin panel. However, I can only see 10 terms in the glossary term item list. The rest of the glossary terms are missing. We cannot check the terms in our database as they are stored on the WPML server. The issue can be seen at: hidden link.
Symptoms:
I expected to see 6848 glossary term items in the listing, but instead, I only see 10 glossary terms.
Questions:
Where are the rest of the glossary terms?
How can I ensure all 6848 glossary terms are displayed?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
I take it you uploaded them via a CSV file? if that was the case, then please take your CSV file and check the column "kind", make sure the elements all have a value of "name".
The value "general" is being deprecated and it's likely it's those elements that are not appearing when you're uploading them.
When you upload them to your system, remember to select the checkbox "Overwrite existing terms" so they get updated.
HI
The issue is that like there is shown 6848 term item as per the screenshot but when I look into the list that is shown only 10 glossary terms item. Why this happen?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Can you try to download this CSV and upload it to your system + make sure you select the "overwrite terms" checkbox, please?
Download link: hidden link
The problem is that most of the elements you had had a type that is no longer in use, so that's why you can't see it and if you download the CSV you'll see only the ones that do appear on the site, the rest are filtered out.
Hey,
I imported the CSV you provided in my local environment; however, it only shows 3920 glossary terms. That means, according to your last response, only 3920 glossary terms are used on the website, with the remaining 2946 glossary phrases being filtered out owing to inactivity. Correct me if I'm mistaken.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hm, can you think of a glossary element that you don't see that should be there, by any chance? this way I can check what's going on because i see 6888 elements in the glossary and given you have 6 languages, that means there are probably many elements missing, indeed.
However, if I don't know which one is missing, at least one, It's impossible for me to determine why it's missing. can you help me, please so I can verify what happened and send the missing ones over?
I also don't understand what you mean here:
... with the remaining 2946 glossary phrases being filtered out owing to inactivity
Inactivity? I'm not sure I follow your logic here. the glossary entries do not have "activity" at all, so whether they are used or not is irrelevant here in this scenario.
... with the remaining 2946 glossary phrases being filtered out owing to inactivity.
The meaning of the above sentence is that there are 2946 glossary term items which are not available on the website, so it's filtered out as you said in the previous reply which is as per the below:
"The problem is that most of the elements you had had a type that is no longer in use, so that's why you can't see it, and if you download the CSV, you'll see only the ones that do appear on the site; the rest are filtered out."
Please have a look at the below glossary term listings which are not imported:
- Coefficient of Friction Fixture
- Drop Weight Impact Test
- Initial Frame Stiffness
- Minimizing downtime
- Save
- Teaser Image Listing Item 1
Where do I need to share the CSV file which is imported in my local environment? I don't want to share it publicly.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello, In the CSV I sent you, those elements exist, they translated to French and some to Japanese, but they don't seem to be translated into other languages (At least not yet), can you confirm that is correct?
If so, Would you:
- Tell me if all the glossary entries have been translated into all the languages
- Allow me access to the site, so I can run some tests and find out why they are not all imported (at least those terms, so I can then figure out if there are others missing)
We can't share our admin access with you. Is there any other option, like a call or Microsoft Teams meeting? Please share with us so we can see via screen sharing.
Please have a look at the below attached CSV.
Link: hidden link
Password: 9876543210
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
we can't have video calls or anything outside this ticket as it's outside of the scope of the support we provide.
However I see something particular. what you sent me and what I sent you are very different. in fact, I uploaded the glossary that I sent you and you can see the results here: hidden link
There are 159 pages of content. but in one of your screenshots you show over 190 pages
Now:
1) Do you have glossary elements without translations on other languages? those will not be imported
2) Did you have a translation of the glossary entry for every single language? because I saw many without any translation
3) Can you go to WPML > Support > Troubleshooting > Your Automatic translation ID is. Send me the code you'll see there so I can match it with the place where I got the glossary (you have also staging sites, etc So I want to see if I took the initial glossary from somewhere else).
4) How do you know the exact amount of glossary entries you have? do you have like a backup somewhere?
I downloaded the CSV that you previously shared (hidden link). I imported this CSV into my local environment and can only see the imported data that I shared with you in a prior reply (please have a look at the attached screenshot). Can you please match the count after importing a CSV that has approximately 8849 rows with the list of imported glossary terms in the WP backend? (hidden link)
I cannot see the results. Please have a look at the screenshot. hidden link URL. hidden link
You can test using the following cases:
To begin with, import the glossary CSV, which has roughly 8848 terms.
Second, whatever glossary imported, simply export via admin panel from glossary tab.
Third, re-import the output glossary CSV and check the counts of the glossary terms.
The Automatic Translation account id is
a1457b28-d728-4bde-9216-299e7e1769b3#JbLMKXjvQM0SU3aaDTwJOwtt
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
hidden link
I uploaded it for the first time and it uploaded everything. there were 1095 pages of entries so a bit less than 3900 entries.
then i refreshed the page and exported the file and it exported less entries, weirdly. interestingly if you do have all the content with values, it does export everything correctly so I guess that's the problem here.
I' asking our devs about this but can you confirm that's the issue you're currently experiencing now?
Yes, correct. In the beginning, whatever glossary terms we've imported appear in the notice panel at the top of the header, as shown in the screenshot at "hidden link". Each time When I exported the glossary terms CSV from WordPress Admin, it did not include the correct amount of glossary word entries. When I import the CSV and look at the listing of the glossary terms item, it sometimes only shows 10 items; however, they are shown in the notice panel with the same count, such as 6918 at the top of the header, as shown in the screenshot at URL "hidden link", but when I look at the glossary listing, it only shows 10 items. So, there are issues with import/export on both sides, as you previously sent the CSV with about 6889 glossary term items, but when I import it into my local environment, the listing only has 3890 glossary entries. Please provide a solution as quickly as possible, as our website is already live.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
I managed to recreate that on our end and I'm working with our devs to understand why this is happening (it seems to happen only with sites with a lot of glossary entries) and how we can fix it. I hope I can give you better updates today :).
