In readme.txt file it is said that "If you have existing hierarchies, be sure to set up the existing database by going to lineage/reset. "

Where to do reset? I tried http://www.mysite.com/lineage/reset, page not found. Also I can not find setting about this in admin backend.

After I installed lineage module, any modification an existing term or adding a new term will put that term to the top level in the hierachical structure. So, I guess I need to reset database, right? But, where shall I do this?

Comments

merlinofchaos’s picture

merlinofchaos commented

Hmmm. In Drupal 5 theoretically you should not need to reset the database as the new hook_enable() allows lineage to do that.

Worst case you can disable then reenable the module to force the reset to run, but I'm kind of curious why you might even have to.

Can you give more detail on what is going wrong with term modification?

huayen’s picture

huayen commented

After I installed lineage module and before I modify or add any terms, I use default taxinimy_tree view (provided by view bonus pack module) to display hierachical taxonomy tree. Everything is ok.

However, as long as I modify an existing term (not at top level) or add a new term to a sub-level, that term always change to or appear at top level. So, I guess lineage module has problem in detect the correct tree structure if the taxonomy structure is altered. So, I tried to reset database hoping lineage can recognize modified tree structure.

Natalie@drupal.ru’s picture

Natalie@drupal.ru commented

I'm having the same problem with the hierarchy not being updated properly. I don't see any "reset" option and disabling module every time I add a term is a bit of a pain in the neck.

Anonymous’s picture

Anonymous (not verified) commented

Another one here.
Table is not updated properly!

wrunt’s picture

wrunt commented
Status: Active » Fixed

I've tracked down the problem, and it's fixed in the latest release (5.x-1.4). If you run update.php after updating to that version then the database will be reset and shouldn't become broken again.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.