Clrean install:

- Drupal 6.
- Lastest workflow module.
- Lastest workflow extension module.

When saving an already created node (just by pressing save or the buttons to move to a different state) ignores the menu options and saves it under Navigation menu breaking the whole webpage.

Kind regards.

Comments

rdeboer’s picture

Status: Active » Postponed (maintainer needs more info)

Hi Wallack,
Thank you for your report.
I'm sorry, but I do not fully understand what you mean. Would you be able to list your expectations vs the actual events more clearly, as well as the steps to reproduce your findings?
Thank you,
Rik

rdeboer’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
kant’s picture

Version: 6.x-1.0 » 6.x-1.2
Status: Closed (cannot reproduce) » Active

Hi,

I experience the same problem, so I will try to give a little more details.
On a website, I have the following:
- Drupal 6.22
- Workflow 6.x-1.5
- Workflow extensions 6.x-1.2

In workflow extensions settings, I selected "Single action buttons" as the form style to be used.
Now, when editing a node, let's say I want to create a menu link in the "Primary links". I give a name to the menu item and select its parent as the "Primary links" menu root.
If I now click on the "Save" button or any of the workflow submit buttons, the menu item is not saved in "Primary links", but rather in the "navigation" menu (which is the default menu_name option of the menu module).

While searching into the code, I discovered that the menu module adds this callback to the "#submit" attribute of the node form:
menu_node_form_submit

=> what this function does apparently is breaking the parent item selected in node form in two variables: menu_name and plid
I discovered that this function is not called anymore when using Workflow extensions with the "single action buttons" form style. A search in the code led me at the line 362 of the workflow_extensions.module file, where a reference to this function is made in a comment.
It seems that the problem may be in this area of the code.

Hope it helps,

kant

(btw, thanks for this great module)

rdeboer’s picture

Thanks kant,
Just wanted to acknowledge receipt of your detailed issue. Looks like I should be able to reproduce it with your instructions.
It's very late here in Melbourne, Australia, so I won't be able to attend to your issue right now, but it's on my agenda!
Rik

kant’s picture

OK, thank you from Belgium for your quick answer.
Sleep well ;)

kant

rdeboer’s picture

Assigned: Unassigned » rdeboer
Priority: Critical » Major
Status: Active » Fixed

Fixed and committed.
Available in 6.x-1.3.

kant’s picture

That was fast! And it works like a charm.

Thanks again!

kant

rdeboer’s picture

Well you did all the ground work! So I should thank you!
Rik

Status: Fixed » Closed (fixed)

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