Sheetnode menu settings: parent item is reset to "Primary links" when user saves his own sheetnode [#1593978]

Dear community,
since the update to the latest Sheetnode version for Drupal 6.x I have this problem with the sheetnodes:
When administrator saves a sheetnode, everything seems ok, but when a user saves his own sheetnode, in the menu settings the parent item is reset to "Primary links". The users do not see this setting when editing their sheetnodes.

Before the update to Sheetnode version 6.x-1.7 I remember that users could also see/edit the taxonomy fields when editing their sheetnodes, but not any more with this version. Along with the update of Sheetnode I also updated Drupal to version 6.26. Perhaps this issue is related to this update, too?

For my site it is important that sheetnodes keep their menu settings, because when they are changed, the sheetnodes disappear from the menus accessible for users. Does anybody have an idea how I could fix this?

Thanks in advance and kind regards,
rapport

Comments

Comment #1

infojunkie

Vancouver

CreditAttribution: infojunkie commented 26 June 2012 at 03:58

Status:

Postponed (maintainer needs more info)

» Active

* Menu issue: I set a test user's permission to "administer menu" and created a sheetnode. I set the menu entry to "Navigation" and gave it a title. The menu appeared.

* Taxonomy: I associated a vocabulary with the sheetnode content type and was able to see this vocabulary in the sheetnode creation form.

Can you reproduce those 2 problems on a plain Drupal installation with just latest Sheetnode 6.x-1.x-dev installed?

Comment #2

infojunkie

Vancouver

CreditAttribution: infojunkie commented 26 June 2012 at 03:58

Status:

Active

» Postponed (maintainer needs more info)

Comment #3

rapport CreditAttribution: rapport commented 13 October 2012 at 20:42

Component:	User interface	» Core
Status:	Active	» Postponed (maintainer needs more info)

Hello infojunkie,

thanks for your reply. I'm sorry for my late answer. I had to abandon Drupal 6, needed to upgrade.
The problem persists in Drupal 7. However, I observed that it does not occur with certain users who have more editing permissions on sheetnodes. It seems to be a permissions-related issue. I will try to find out which permissions cause the behavior in my site and post later.

Kind regards,
rapport