Hi,

6.x-1.3 is recommend for use apparently, but its over a year old... I tried 2.x-dev and it worked fine, except it did not embed the child view into the node page.

Question: what version is "really" recommended for a new site? Better to use v1.3, or help debug 2.x? Is a 2.x release expected any time soon?

Thanks in advance,

Comments

bneil’s picture

bneil commented

The latest stable version (6.x-1.3) has some issues with the latest versions of Token and Pathauto: #883604: Fully supporting and integrating PathAuto and Token. We're using the 1.x dev version for now on sites that need it with no issues. So either way you'd probably have to use a dev version if you're using the [hierarchytitlepath-raw] and [fullhierarchypath] tokens provided by this module. Hopefully one of the module maintainers can comment on a release schedule for either version. I'm curious as well.

zeezhao’s picture

zeezhao commented

I have always used 2.x-dev, as more recent and also maybe some bug fixes.

Note that you can change the nodehierarchy_children_list view via:
admin/build/views/edit/nodehierarchy_children_list

jbylsma’s picture

jbylsma commented

I've used the 2.x-dev branch in production environments without any problems. It's been a while since I've touched 1.x, but I remember being impressed with 2.x's behavior when I first was checking it out. There had been a fair amount of discussion on pushing 2.x-dev to stable at #955148: 6.x-2.0 Roadmap but the last update was me in November. That being said, I'd still think it'd be in your best interest to use 2.x.

As for getting the best 2.x, dgorton created a patch (#955148-17: 6.x-2.0 Roadmap ) that incorporated the pathauto fix, the pathauto recursion code, and an uninstall bug. ronan has already patched the pathauto fix in the current dev #883604-61: Fully supporting and integrating PathAuto and Token, so you might get some warnings if you use that patch. I just applied it to a clean site and it's running as expected.

markhalliwell’s picture

markhalliwell
Primary language English
commented
Status: Active » Fixed

Marking as fixed as there is now a 2.0 release. Do not re-open this issue. Thanks!

Status: Fixed » Closed (fixed)

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