Opened 15 years ago
Closed 15 years ago
#11510 closed feature request (wontfix)
Multiple Categories / Slugs
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | low | |
Severity: | major | Version: | 2.9 |
Component: | Taxonomy | Keywords: | category subcategories |
Focuses: | Cc: |
Description
Hi, I posted many messages for more than a year of the forums (http://wordpress.org/support/topic/229543?replies=13 and http://wordpress.org/support/topic/340552?replies=9) concerning category management. It appears WP 2.9 doesn't fix the bug which has been reported on several tickets:
Sub categories automatically append a dash followed by the name of the parent
http://core.trac.wordpress.org/ticket/10712
Child categories error out as duplicates even if slugs and parent categories are different
http://core.trac.wordpress.org/ticket/9335
I still can't create duplicate categories/slugs and I don't want to hack Wordpress core files, which is the solution provided on ticket #9335...
It's a major issue when you use Wordpress as a CMS and there are a lot of comments and messages about it. Wordpress is the best blog platform but this bug is ruining any attempt to use it as a real CMS.
What can I do if I want to work with these categories:
Books
- News
-- Fantasy
-- RPG
- Reviews
-- Fantasy
-- RPG
Videogames
- News
-- Fantasy
-- RPG
- Reviews
-- Fantasy
-- RPG
Any help? <:)
Change History (7)
#2
@
15 years ago
- Milestone changed from Unassigned to Future Release
- Priority changed from high to low
#4
in reply to:
↑ 3
;
follow-ups:
↓ 5
↓ 6
@
15 years ago
Replying to Denis-de-Bernardy:
Doh. Low priority. So what do we do until a solution is found? Can you guys propose a 'fix', maybe using taxonomies? So we can manage our multiple categories like:
Each main category gets a taxonomy name and a whole new category list
Child, sub and so on are managed through the new category list
So each main category works independantly, like it was a 'site'.
Could that be an intermediate solution you could provide? I'm looking to solutions here...
#5
in reply to:
↑ 4
@
15 years ago
- Component changed from General to Taxonomy
- Owner set to filosofo
Replying to Alkorr:
Replying to Denis-de-Bernardy:
Doh. Low priority. So what do we do until a solution is found? Can you guys propose a 'fix', maybe using taxonomies?
there is none, short of not using the taxonomy api. basically, the way the taxonomy api is designed, a term lives by itself, and it can be part of several taxonomies... once. the abstract way to say this is: the taxonomy API is hugely wrong in that it amounts to modeling nodes, rather than node links as it should.
I've set low priority simply because it seems rather clear to me, based on core dev discussions, that changing this is low priority indeed. Changing the way it works requires significant schema and API changes, I don't see this happening anytime soon.
#6
in reply to:
↑ 4
@
15 years ago
Replying to Alkorr:
Each main category gets a taxonomy name and a whole new category list
Child, sub and so on are managed through the new category list
So each main category works independantly, like it was a 'site'.
Could that be an intermediate solution you could provide? I'm looking to solutions here...
Having multiple category taxonomies like that is the best solution. The only thing you're missing is the admin part: post boxes for each category set and a category management page for each.
I think both of those can be build into a plugin.
didn't that idea get clearly ruled out by Matt or a core dev recently (i.e. "We're not changing the taxonomy tables any time soon" or similar statement)