WordPress.org

Make WordPress Core

Opened 10 years ago

Closed 10 years ago

#12663 closed defect (bug) (fixed)

Hierarchical taxonomies mixed up, not global when global terms enabled in multisite

Reported by: sillybean Owned by:
Milestone: 3.0 Priority: normal
Severity: normal Version: 3.0
Component: Multisite Keywords:
Focuses: Cc:

Description

I'm creating a custom post type and taxonomy for a university site. I had tested the plugin successfully on a single site. On the network, I created a subdomain site to test things a bit, then turned on global terms and network-enabled the plugin. When I went to create a new College term, weirdness occurred.

The list of Colleges was initially blank, as you would expect. When I entered the first one (Architecture), what appeared in the Colleges list on the right was Uncategorized. I deleted that and tried again. This time Blogroll appeared. I deleted that and tried a third time. This time I did get Architecture with the slug architecture-3.

Uncategorized and Blogroll still appear under both sites' categories and link categories. On the subdomain site, the Colleges list is blank again.

Change History (7)

#1 @nacin
10 years ago

  • Milestone changed from Unassigned to 3.0

#2 @wpmuguru
10 years ago

Global terms wasn't implemented for custom taxonomies.

Before I do anything with this, does anyone have a preference for whether custom taxonomies are included or excluded?

#3 @wpmuguru
10 years ago

I have a patch for this that passed initial testing. I'd like to test it more extensively before committing.

#4 @wpmuguru
10 years ago

(In [13925]) rework syncing of global terms, see #12663

#5 follow-up: @gazouteast
10 years ago

quote "Before I do anything with this, does anyone have a preference for whether custom taxonomies are included or excluded? "

Yes please.

#6 in reply to: ↑ 5 @wpmuguru
10 years ago

Replying to gazouteast:

quote "Before I do anything with this, does anyone have a preference for whether custom taxonomies are included or excluded? "

Yes please.

The original comment was in error. They were not excluded from global terms.

#7 @wpmuguru
10 years ago

  • Resolution set to fixed
  • Status changed from new to closed

Closing this pending someone reporting an issue.

Note: See TracTickets for help on using tickets.