Opened 9 years ago
Last modified 8 months ago
#21734 reopened enhancement
Completely remove global terms
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Future Release | Priority: | normal |
Severity: | normal | Version: | |
Component: | Networks and Sites | Keywords: | needs-refresh |
Focuses: | multisite | Cc: |
Description (last modified by )
Attachments (4)
Change History (21)
#2
@
9 years ago
- Keywords has-patch added
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.
#5
@
9 years ago
21734.2.diff resurrects global_terms_enabled() and adds TODO for where the code for installing the plugin should go.
#6
@
9 years ago
- Keywords needs-testing added
- Milestone changed from Awaiting Review to 3.5
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)
#7
follow-up:
↓ 8
@
9 years ago
Why is the change in get_blog_permalink() needed?
$link = set_url_scheme( get_permalink( $post_id ) , 'http' );
#8
in reply to:
↑ 7
@
9 years ago
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.
#9
@
9 years ago
- Keywords punt added
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.
#10
@
9 years ago
- Keywords punt removed
- Milestone changed from 3.5 to Future Release
If it doesn't block #5809, I'm fine with it.
#12
@
8 years ago
- Keywords needs-refresh added; has-patch needs-testing removed
- Milestone Future Release deleted
- Resolution set to maybelater
- Status changed from new to closed
I don't think this matters right now
#13
@
6 years ago
- Milestone set to Future Release
- Resolution maybelater deleted
- Status changed from closed to reopened
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.
#15
@
6 years ago
Yep, we'll hopefully have a plan for WP.com after next week, which will guide how we remove it from Core.
ticket:12666#comment:8