This topic has 10 replies, 2 voices, and was last updated 10 years, 6 months ago ago by Eva Kemp
How do I permanently delete a product category? I created it originally and then deleted it, but decided to use it again and now it won’t let me use it because it says it’s already in use…
I want to change the misspelled version /patek-phillipe-cufflinks to the correctly spelled:
/patek-philippe-cufflinks
Hello,
As I see patek-phillipe-cufflinks category exist there. Go to Products > Categories, find Patek Phillipe Cufflinks category and edit its title and slug.
Regards,
Eva Kemp.
I tried to change it to patek-philippe-cufflinks and it says that I can’t change it because it is already in use.
You have the same slug “patek-philippe-cufflinks” for page “Patek Philippe Cufflinks”. Unfortunately in WordPress you cannot have two pages/categories with the exact same slug. So you have to change it for the page or the category.
Regards,
Eva Kemp.
I erased the page so that it wasn’t conflicting, but now it still says that “patek-philippe-cufflinks” is in use. I set it as cufflink (without the s) temporarily…
Hello,
Have you removed the page completely, even from the Trash?
Please check.
Regards,
Eva Kemp.
Yes, I permanently deleted it from the trash.
As I see there is already the category Patek Philippe Cufflinks with the slug patek-philippe-cufflink. So you’ve already corrected “Philippe” word, as it had been written “Phillipe” before. Please clarify what you’re trying to change now.
Thank you.
Regards,
Eva Kemp.
I need it to be cufflinks instead of cufflink.
patek-philippe-cufflink = what it is now
patek-philippe-cufflinks = what it needs to be
The reason is such slug “patek-philippe-cufflinks” is used for the category Patek Philippe Cufflinks which is located in Posts > Categories. You need rename it or delete to be able to change it for Products > Categories.
Please make sure you don’t have more similar slugs created.
Regards,
Eva Kemp.
The issue related to '‘Product Category "Already in Use" from deleted category’' has been successfully resolved, and the topic is now closed for further responses