Drupal 6.22.
I have upgraded Node hierarchy (deleted folder and copied new version) and have had Internal Server Error 500.
Interesting - main page of site works and pages with materials too. But pages with views output and almost all admin links (f. e. /?q=admin) does not work.
I am testing upgrade on test-site so may do some experiments if it is requirered.

Comments

asPagurus’s picture

Addition
Something strange - There is the text in description of 2.1 version: "This release does not contain any database updates and the nodehierarchy folder can be replaced with ease".
But - update.php lunches two updates (nodehierarchy and views integration) 6200 that creates new table, modifies existing table and does someting that i don't understand :)

And it happens if module switched off too.

leisurman’s picture

Same thing happened to me. update Node Hierarchy 6.x-1.4 to 6.x-2.1.
It removed some Views and View Blocks from my pages. My views are not hardcoded into a page. i embed them into the page node. Or i use block views.

I found that if you add an argument to the view, the view will not get removed. But the update has removed view blocks. I had to go into blocks and and the blocks back in.

mcunningham’s picture

+1. How do we get our views back? Thanks.

leisurman’s picture

The way I got mine back was to add an Argument to every View.

Node Hierarchy: Parent Node
Check:Display all values

Action to take if argument does not validate:
Select:Display all values

Let me know if that works for you.

mcunningham’s picture

Thanks for the input. My views already had arguments so that was not the problem. The views required some reworking to work with the new module but I think it's sorted out now.

jbylsma’s picture

Title: Upgrade to 2.1 from 1.4 or 1.3 ruined site » Upgrade from 6.x-1.x to 6.x-2.x breaks Views
Status: Active » Closed (cannot reproduce)

I worked on some Views code for 6.x and committed it to 6.x-2.x-dev at #1263918: Views improvement: documentation, filters, and default arguments. Though I couldn't reproduce the problem, I'm suspecting it had to deal with the NH filters being removed. Please reopen if this is still an issue.