Completely remove global terms

[scribu]

It's an obscure WPMU feature that 1) hasn't been maintained 2) hardly anyone uses and 3) slows down development on the regular taxonomy code:

#5809 #18609 #18617

There isn't much code to remove, but the idea is to not have to worry about "global terms" anymore at all.

[ocean90]

ticket:12666#comment:8

[scribu]

21734.diff​ takes care of the raw code removal.

To be completely back-compat, we'd need to automatically install a plugin, when upgrading a WPMU network which had global terms enabled.

[wonderboymusic]

whoops - I added a patch at basically the exact same time

[scribu]

21734.2.diff​ resurrects global_terms_enabled() and adds TODO for where the code for installing the plugin should go.

[wonderboymusic]

Patch refreshed to accomodate plugin, which is now here: ​http://plugins.svn.wordpress.org/global-terms/trunk/global-terms.php (first rev, needs love / testing)

[scribu]

Why is the change in get_blog_permalink() needed?

$link = set_url_scheme( get_permalink( $post_id ) , 'http' );

[SergeyBiryukov]

Replying to scribu:

Why is the change in get_blog_permalink() needed?

That was from ticket:19420:blog-perma-set-url-scheme.diff​ on #19420.

[nacin]

Not sure I have the stomach for this right now. It's fairly unobtrusive code that we've not needed to maintain or touch since we disabled global terms by default in 3.0.

[scribu]

If it doesn't block #5809, I'm fine with it.

[wonderboymusic]

I don't think this matters right now

[pento]

Global terms is a buggy hell hole, and I think term splitting broke it, at least on WP.com.

Because no-one in their right mind uses it, let's remove it, and auto-install ​the plugin on upgrade.

[DrewAPicture]

@pento Is this still in pursuit?

[pento]

Yep, we'll hopefully have a plan for WP.com after next week, which will guide how we remove it from Core.