My implementation required that nodes that were created not be published initially, due to some workflow that needed to occur before publishing the node. Category_Menu was creating menu items for these items not when they were published, but when they were created.

This is my initial crack at the problem. Unfortunately, it does require modifying one of the database tables, just to be aware.

  • Adds a setting per container to decide whether to update a node based on its published status or not
  • Adds logic to the category_menu.module to accommodate this change.

Note: This implementation only acts on the published status of a node, a good improvement would be to have conditional menu updates on any property of a node.

CommentFileSizeAuthor
category_menu.patch8.97 KBrichardfullmer

Comments

JirkaRybka’s picture

JirkaRybka commented
Status: Needs work » Closed (fixed)

6.x fixes this. There's no need for extra settings and whatnot - menu items are simply just updated on every node_save(), so they get all the changes you did.

So this only applies on 5.x and below, which are de-facto/fully unsupported versions now, so closing this one. It's 2 years old with no update, so I guess it's OK.