@callmeandy,
If you code has been added correctly and is working you should see your taxonomies listed in with the categories.
OK so my appologies – I was all set to give you grief and I find I did not change the “my_taxonomy_type” element; feeling daft now.
So it is subscribing as it should. As a matter of interest however for a possible improvement, I use three taxonomies that I want your plugin to work with, the first two of which are hierarchial.
Because I have something like 200 terms between the three it would greatly benefit from visual seperation of the seperate Taxonomies and being kept in Hierarchial order.
That aside it likes like I will be using it for the foreseable,
thanks for your efforts.
@callmeandy,
The code to display the categories and / or custom taxonomies makes use of the get_ancestors() function in WordPress should should list hierarchy for each taxonomy that has a parent.
Is this not working for your custom taxonomies? Is should be something like:
Parent » Child » Subchild
If it doesn’t look like that can you let me have your custom taxonomy registration code and I’ll see if I can figure it out.
As for separating them into different groupings, that’s not possible at the moment. I’ll have to have a think about if and how that could be done within the current code.
Hi,
I think it is possibly working the way you intended
For instance a part of the localities taxonomies shows:
Asia » Tajikistan
Africa » Tanzania
Asia » Thailand
Africa » Togo
Oceania » Tonga
North America » Trinidad and Tobago
Africa » Tunisia
Asia » Turkey
But what I was thinking of as an improvement (of course just an opinion) would be to have child below parent:
Africa
======
Togo
Tunisia
Asia
====
Tajikistan
Turkey
Thailand
etc
On a function I wrote (very raw and not shared) I have got it to brake down the codes as above by doing more specific queries and looping over the iterations required in order to produce output segmented according to hierarchy. I wonder could the same not be done per taxonomy. My function was quite complex as it was also counting posts per tax across all nodes on a multisite. So I think this should be a breeze. That said the method is probably not overly efficient.
I’ll have a look at this myself when I get time but for now I’m hard pushed with a deadline being put back already for “launch” next friday and still loads to do. So I will live with your solution. Efforts much appreciated and thanks for coming back to me on this.
