I am having issues with {root_node_lft} as this value appears to change when new nodes are added. So I have a page where I am calling all the children of a certain node - but whenever a new node is created the node in question gets it node_lft value changed and thus errors are thrown as it can’t find any children! Anyway of having it so these values can be fixed?

I’ve added a new parameter for the nav if you can grab a fresh copy from GitHub,

Your opening nav tag can look like this:

The new parameter being root_node_entry_id, simply pass the entry id of the entry you’d like the nav to start from. (This assumes that an entry is only used once in the tree though.)

Its nearly 1am here, so if there’s any bugs caused by this I won’t be able to look at it till the morning,

Iain.

Version 0.4 is up, some changes to the UI for access to editing entries, viewing taxonomy urls and editing node properties.

I’ll need to do some testing for IE I think, I see IE8 is ok with the UI changes I’ve just done.

Hopefully I will be working on some of the feature requests in the coming week…

Out of interest, has anyone deployed in a production site?  Just curious

I’ve done 2 sites so far

I’m using Taxonomy 0.35. When I add new template groups, I notice they don’t show up in the taxonomy template → entry dropdown. How do I get newly created template groups to show up?

You need to set which templates are available to publishers via the tree properties…

Or have I misunderstood?

Thats what I was looking for.

Can I use Taxonomy for my site menu.

For example.

I’ve created a parent node called Root with no URL or templates selected.

Then I create child nodes under root

Home
About
Services
- Design
- Logos
- SEO
Portfolio
Contact

Is this a practical use of the Taxonomy module? Will I be able to create breadcrumbs if I were to do this?

I’d probably question the use of Taxonomy for a site of this size, but certainly yes it will work.

I don’t see anything that would be particularly tricky to do out of the box so to speak, eg having templates for all your main top level items and using categories to serve up services.

There are several ways to skin a cat however, but generally I make the top/main navigation fixed, - hardcoded into an embed/snippet, therefor not available for clients to edit.

I’d be using Taxonomy for subsections such as ‘About’, or even to order entries within the Services section.