Upgrading

***BIG WARNING***
You must disable any old copy of Taxonomy Treemenu. And UNINSTALL it too, if you see the option offered.

You must also remove and UNINSTALL any version of Taxonomy Router. It is not needed now (tested and confirmed as not necessary).

When you do this, you will destroy old menu information. Sorry, I'm not going to write the code to rescue that data. Because, first, most people are hanging on to see when this module comes good; second, treemenus are very easy to build; third, the move to Version 5 would involve a huge piece of code to upgrade data. If you don't want to destroy your existing data, don't upgrade.

Install the new BETA. And maybe post your thoughts (about how requesting destruction of user's data is irresponsible?).

About Version 5

One of those Question and Answer posts people make when they can't figure out how to say it properly...

Another Version!
Drupal recommendation - new stuff, new Version. Several module authors do not stick to this, for reasons of sanity. I do, therefore...

And another BETA!
Either the module just doesn't work very well for users (Version 4) or it changes too fast (most every other version). Sigh. One of them will stabilise. I keep hoping.

Why BETA this time?
I'm in a big development cycle. I write, build, and as I do, there's more to test, and without the full module in place, it's hard to test. So I drew a line round some functionality, and I'm putting it out.

If functionality looks unfinished, now you know why.

Why should I try it? Version 4 of this module was an unpleasant mess.

I always tried BETAs because I might help out?

Also, if you at all interested in this module, this version is going to supersede everything that went before. Comprehensively. It may be an BETA, but it has the simple delivery of Version 1 and 2, but the advanced features of Versions 3 and 4 are there, though not enabled yet.

That's more promising, but a bit retrogressive.
Have a look at the admin form. And maybe install the Advanced Help module (if you havn't got it already).

I'm still a bit wary.
You're not an BETA person then. Hang on until others try it for you.

Will you be around to help?
I'll do my best (which has not worked out recently)?

Comments

rcrowther’s picture

Title: Version 5 BETA - Notes and install instructions » Version 5 - Notes and install instructions

Version 5.1 is out.

Install

For those with V5 BETAs
Despite the raise in release number (due to several new features),

DO NOT DESTROY YOUR DATA
DO NOT DISABLE OR UNINSTALL THE MODULE

You can if you like, but,

V5.1 IS A DROP-IN REPLACEMENT FOR THE EARLIER BETAS

Also, none of the code is critical functionality or bugs. There is no need to upgrade if you don't want to.

AFTER YOU HAVE DROPPED THE NEW VERSION IN, DO A MENU REBUILD AND CACHE CLEAR.
Otherwise your site will not be quite up to speed.

About V5.1

V5.1 has been tested, at least superficially, on a working site, and all seems good in that (small) context.

For new stuff that lead to Version 5 reaching Version 1, best see cvs. Some new features include,
- internal 'just links' term theme.
- A LOT of theming help
- Custom term lists in internal theme retain treemenu extended URLs
- Node counts are back.

The bug squashing is code which might not be best called bugs (they don't break anything), so much as superficially considered functionality given a closer look (there is lots more of this to do...).

rcrowther’s picture

Version 5.2.

Bugfix of 5.1. Highly recommended, especially if you see the 'call by reference is depreciated' message.

A drop in replacement for all V5s.

rcrowther’s picture

Version 5.3

Same notes as for 5.2

rcrowther’s picture

Install Version 5 Rev 4

A drop in replacement for Version 5 modules. If you have V5.3 and it's working, no need to upgrade.

about

Adds a huge new help file with an options summary of dubious authority (untested).
Now respects a hook which makes it work rather good with Taxonomy Redirect.
The menu overview page has been tidied up to work better with Taxonomy V5 in general.
And I tried to do something about that admin css.

After much craziness in the past, several new features were slipped in here without a version upgrade. If the changes are a drop in replacement, I plan to continue like this (or we'll be in double figures by autumn, at this rate)