If a user does not have permission to "Administer Nodes", any nodes they create through the Node Repeat sequence do not take on the Author of the original node (instead staying blank and thus showing up as Anonymous). This creates a multitude of issues arising from the original creator no longer having "ownership" of the subsequently created nodes. I've noticed this behavior in ALL recent versions of Node Repeat.

My guess is that this is because of the Publishing function? Since Node Repeat offers the option to publish or unpublish the nodes on creation, it must take on the 'administer node' role during it's process, but regular users who have been given permission to creation repeating nodes will generally not have this permission, thus creating the issue.

I know there are some mods out there that allow you to override this permission and will investigate this when I have time. This is something that should definitely be addressed either within Node Repeat or in conjunction with another module as most installations of this will not involve only Administrators creating repeating events.

Comments

Negs’s picture

Negs CreditAttribution: Negs commented

Yes, this is also a problem for me. Any guidance on a fix? What are the mods that can be done to work around this if the function won't be added to the module?

gagarine’s picture

gagarine CreditAttribution: gagarine commented
Version: 6.x-2.x-dev » 6.x-3.x-dev
Assigned: Unassigned » gagarine

I agree is a major bug. Let me take a look asap.

MacaroniDuck’s picture

MacaroniDuck CreditAttribution: MacaroniDuck commented

This bug actually forced me to pull the mod from production. If you can get this fixed, I can get it back into production where it will get more extensive testing.

Morn’s picture

Morn CreditAttribution: Morn commented

. Subscribe

memelissaann’s picture

memelissaann CreditAttribution: memelissaann commented

Old issue, I know, but thought I would comment with my solution anyway.

You can use rules to set the author of nodes to the acting user when a node is saved. I have my rules set up with the following configuration and it works well for my purposes.

Event >> After saving new content

Do >> Set the content author >> Content: created content >> User, who is set as author: acting user

With this rule set, the author of the repeat nodes is set to whoever triggered the nodes to be repeated.

HTH