Opened 9 months ago
Last modified 5 months ago
#21734 new enhancement
Completely remove global terms
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Taxonomy | Version: | |
| Severity: | normal | Keywords: | has-patch needs-testing |
| Cc: | kawauso |
Description (last modified by scribu)
Attachments (4)
Change History (15)
wonderboymusic — 9 months 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.
comment:3
wonderboymusic — 9 months ago
whoops - I added a patch at basically the exact same time
21734.2.diff resurrects global_terms_enabled() and adds TODO for where the code for installing the plugin should go.
wonderboymusic — 8 months ago
comment:6
wonderboymusic — 8 months 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)
Why is the change in get_blog_permalink() needed?
$link = set_url_scheme( get_permalink( $post_id ) , 'http' );
comment:8
in reply to:
↑ 7
SergeyBiryukov — 8 months 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.
- 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.
comment:10
scribu — 8 months ago
- Keywords punt removed
- Milestone changed from 3.5 to Future Release
If it doesn't block #5809, I'm fine with it.
comment:11
kawauso — 5 months ago
- Cc kawauso added

ticket:12666#comment:8