[wp-trac] [WordPress Trac] #35848: WordPress 4.4 Handling Custom Taxonomies and Tax Queries Correctly
WordPress Trac
noreply at wordpress.org
Sun Feb 21 21:08:30 UTC 2016
#35848: WordPress 4.4 Handling Custom Taxonomies and Tax Queries Correctly
-------------------------------+------------------------------
Reporter: vrazer | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Query | Version: 4.4
Severity: normal | Resolution:
Keywords: reporter-feedback | Focuses:
-------------------------------+------------------------------
Comment (by vrazer):
We were able to determine a bit more information on this. All I can say
for sure is that the behavior that changed between 4.3 and 4.4 is somehow
also tied to the 'public' status of the registered taxonomy. By that,
what I mean is that setting the status of the taxonomy to public fixes
this problem (which is obviously the intended result of that parameter).
At least, that is the case with the Types plugin and how it registers
custom taxonomies. We are seeing this same behavior with the More Types
and More Taxonomies plugins (completely separate plugins). Oddly, the
problem with taxonomies constructed by the More Taxonomies is one where
the taxonomy IS set to public but still has this same issue. The issue
occurred in both cases at the onset of WordPress 4.4 with prior settings
working fine in 4.3. With Types, there was a functional fix by changing
settings. With More Taxonomies, there was not.
Additional research into this has us questioning whether the issue is not
as much of a new bug in WP 4.4 as perhaps a bug in 4.3 (and prior) that
was fixed in 4.4. I wish I could say more specifically what set of
symptoms was creating this, but all I know for sure is that the problem
involves the use of Custom Types with Custom Taxonomies built by plugins
(which do use the register taxonomy function correctly). The settings
used in these plugins (which are passed to register_taxonomy) all appear
to be correct. If we are able to better track down this issue, we will
report back with specifics. In the meantime, I'm going to have to assume
that the issue is actually a bug that was fixed in 4.4 that manifested on
some sites as if a bug had been introduced (perhaps due to some
inadvertent reliance on that bug).
--
Ticket URL: <https://core.trac.wordpress.org/ticket/35848#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list