We have an issue when trying to update terms. from rest api. In the collection we have an example. Whenever we try to update an existing term we get error that the slug already exists, even we dont put slug on the posting json update. Any ideas why we have this issue? We cant do updates on term for that reason
The error (the messages says that the slug is already been used from another term)
{
"update": [
{
"id": 166,
"error": {
"code": "duplicate_term_slug",
"message": "Το σύντομο όνομα “bibi-lou-en” χρησιμοποιείται ήδη από άλλον όρο.",
Can you please explain little more about the problem? Like is the term relating to a product (I assume) or another post type, how you are creating your API request (i.e. a sample code, remember not to include any credentials) and etc.
As a clue, what happens if you also include the slug? Since you are updating the term, you must have the slug already. Please note that, this is not a limitation of WPML, but rather how WordPress works. Even if you don't explicitly provide a slug in your JSON update, WordPress will automatically generate one based on the term name.
If you're still encountering issues, it might be worth checking if the term you're trying to update has a translation with the same slug, as this could also cause conflicts. If this is the case, you might need to adjust the slug of the translated term to ensure uniqueness.
Even if we provide the slug it still throws an error. The problem is on the translation too. If we do the same thing for the default language it doesnt throw an error and we can update the term as many times we want (with or without the slug) but when we do it for a translation, it throws the error
This link doesnt help. Its for a different problem. The issue we have is with the normal update process. We dont put slug and we get an error. Its on the postman collection we send you as an example in our dev environment. Do you need something more so you can debug the issue?
Plus the link you send us, is from a question we did, so we already know that reply
Hello.
The change worked well.
Please let us know if this change will be included in the next update or not, so we know if we should make it when needed.
Thank you for confirming and glad it worked for you.
Unfortunately there's no ETA so far, however, the issue is with dev team and is in active development.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
