|traversal||# Posted on April 28, 2016 at 9:33 am|
I’m a bit unclear as to what “custom_name” is, is that the name of a taxonomy? If so, then there won’t be any property on $wf->the which corresponds to that.
You can access an object for the custom taxonomy with the function WOOF::taxonomy:
So in your case something like:
$tax = $wf->taxonomy(“custom_name”);
If you need that to be more generic, so that you can get the taxonomy object for the current template (assuming you’re on a “taxonomy” page, you should be able to just call taxonomy “without” the argument:
$tax = $wf->taxonomy();
Let me know if that helps!
Masterpress 1.3.6 is a compatibility release. It resolves an edge case with shared fieldsets not working for MySQL 8 when the fieldset is limited to more than 1 post type or taxonomy or excluding any post types or taxonomies.