Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I have a view that displays a list of nodes and I configured internal nodes to redirect traffic from the actual node path to the view and it does the job.
The only problem is now the node can not be deleted or edited. I have the add and delete links displayed in the view but if I click on either of them I just get redirected back to the view. I can't get to the edit or delete form.
Is there a way to allow the forms to display.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | internal_nodes_node_permissions.png | 60.55 KB | 13rac1 |
Comments
Comment #1
13rac1 CreditAttribution: 13rac1 commentedTo confirm: you want to access the node edit as a user who doesn't have the "access [node-type] node view" permission?
Comment #2
xanderol CreditAttribution: xanderol commentedI guess the way the module works it wouldn't make any sense.
I was just looking for a way to direct traffic from the node to a view which displays a list of the nodes. But I still want the ability to delete or edit the nodes.
Unfortunately once a user creates a node they can not edit or delete it since the module restricts access to the display of the edit and delete form of the node also.
Comment #3
13rac1 CreditAttribution: 13rac1 commentedIt makes sense, I've just not had that use case before. I've changed this to a feature request.
Comment #4
mcartmel CreditAttribution: mcartmel commentedHi, I have the same situation as xanderol. Subscribe +1
Comment #5
jphelan CreditAttribution: jphelan commented+1 from me as well
Comment #6
mstrelan CreditAttribution: mstrelan commentedYep me too. My nodes display in a views table display with an edit link, and there is never a good reason for the node to be visible on its own, not even to the content editors.
Comment #7
13rac1 CreditAttribution: 13rac1 commentedAny suggestions for the Admin UX to do this? Additional permissions? Actually, using the permissions already provided by node.module is probably ideal. If you have edit on a content type, then you can edit the content type. That makes sense!
Comment #8
13rac1 CreditAttribution: 13rac1 commentedI committed code(and tests!) to do this using the node.modules permissions for 403/301. Result: When a user has node edit/delete permission, they can still use it. It actually already worked as requested for 404. The setting are adjustable at the content type level, but not the node level (imo too long tail.)
Commit: http://drupalcode.org/project/internal_nodes.git/commit/19494f2
FYI I'm going to let this settle a bit, then make a new release.