We can successfully upgrade to the 3.2 revisioning and 3.2 module_grants modules with no obvious problems however if we attempt to upgrade past that point submenutree no longer displays any menu items, its difficult to say what is causing the problem but our developer advises some possible causes of this problem:

a) how Revisioning modifies menu items,
or
b) the callback method changes from revisioning 3.2 and 3.3 which perhaps has caused a conflict in our case. e.g. http://drupal.org/node/796470

Upgrading to more recent releases also had the same problem for us.

Something appears to over writing the the menu items that submenutree creates.

Comments

rdeboer’s picture

rdeboer
Location Melbourne
commented

The version numbers you mention are old. Did you make a typo in version numbers?
Try upgrading to Revisioning 6.x-3.11 and Module Grants 6.x-3.6 and don't forget to execute /update.php.

richardhayward’s picture

richardhayward commented

We also tried upgrading to the latest version with the same problem. We'll double check and respond again in a couple of days.

richardhayward’s picture

richardhayward commented
Title: Upgrading 6.x-2.7 to 6.x-3.2 » Upgrading from 6.x-3.2
Version: 6.x-2.7 » 6.x-3.2

To clarify because maybe it wasn't clear in the original description:

  1. Our live site has 2.7 which was installed in 2009.
  2. We have upgraded to 3.2 on our development version last week, I've updated the version number in this issue to reflect that.
  3. We can't upgrade to 3.3 or any higher version without menu items being lost from the submenutree.
  4. We have also tried upgrading to 3.11 with the same problem.
  5. We've followed your instructions during the upgrade process.
rdeboer’s picture

rdeboer
Location Melbourne
commented

Which submenutree?
There must be something special about your install, as this problem hasn't been reported before.
Can you think of any modules that may cause interference with Revisioning?

richardhayward’s picture

richardhayward commented

Its the Submenu Tree block items that don't display (http://drupal.org/project/submenutree).
Can't think of any modules that might be interfering, and more testing has already been done on this.

rdeboer’s picture

rdeboer
Location Melbourne
commented

Ah, ok, so if you disable the submenutree module, does the problem go away?

richardhayward’s picture

richardhayward commented

Yes, that's correct. Issue posted in Submenu Tree #879528: Possible conflict with Revisioning module.

rdeboer’s picture

rdeboer
Location Melbourne
commented

Hi Richard,
Ok, so it's Revisioning in combination with Submenu Tree's block items.... It would be helpful if you could outline the steps of a simple reproduceable test case, as Submenu Tree has a few modes of operation and I prefer not to waste time trying them all in order to reproduce an error that I haven't seen myself.

step 1 Install Revisioning (with Module Grants downloaded but disabled for the purpose of narrowing down the culprit code).
step 2 Install Submenu Tree
step 3 Describe point by point how you create the simplest tree that causes the error to show.
a.....
b....
c...

Then I have something to go by.
Rik

richardhayward’s picture

richardhayward commented

Hi Rik, thanks for your help yesterday. In #879528: Possible conflict with Revisioning module, we described a conflict with the Submenu Tree which has now been resolved, and we believe will also resolve this issue. The fix required making the Submenu Tree module node page view detection more robust to work with modules such as Revisioning that menu_alter() the node/% page callback. We will go ahead and deploy our upgrade as planned and will advise you of the outcome! Regards, Richard.

rdeboer’s picture

rdeboer
Location Melbourne
commented
Status: Active » Closed (fixed)

Trust your issue was solved via the Submenu Tree module, i.e. not a Revisioning problem?

richardhayward’s picture

richardhayward commented

Rik thanks for this, we are still in progress. We need to upgrade Pathauto and Token which stopped working after we upgraded on our test server. After that we'll apply the upgrade again for hopefully final testing. Cheers, Richard.