Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
When I click "clone content" I am taken to node/xxx/clone , which looks like a standard node edit form.
However the "view", "edit" etc tabs link to the original node, not the new not-yet-saved node.
I have found this causes confusion for content managers - they end up accidentally editing the original node, particularly with webforms.
I think these tabs should not appear on the node/xxx/clone page until the user saves the new node.
Thanks for an excellent module!
Comment | File | Size | Author |
---|---|---|---|
#6 | 1960600-6.patch | 1.01 KB | pwolanin |
#4 | ux_bug_view_edit-1960600-4.patch | 688 bytes | tripper54 |
nodequeue-tabs.png | 25.74 KB | tripper54 |
Comments
Comment #1
tripper54 CreditAttribution: tripper54 commentedPatch attached - removes these tabs via hook_menu_local_tasks_alter.
Comment #2
tripper54 CreditAttribution: tripper54 commentedUpdated patch for latest dev, with a bit of disambiguation in the comments.
Comment #3
pwolanin CreditAttribution: pwolanin as a volunteer commentedHmm, this is a side effect of using the same path for save-edit and prepopulate.
The patch is wrong for the save-edit case.
Comment #4
tripper54 CreditAttribution: tripper54 as a volunteer and commentedGood catch. Here's the updated patch.
Comment #5
pwolanin CreditAttribution: pwolanin as a volunteer commentedNeed to supply the default for the variable like
Comment #6
pwolanin CreditAttribution: pwolanin as a volunteer commentedActually, I don't even think we need that check there, but we do need it to suppress the token in the path.
Comment #8
pwolanin CreditAttribution: pwolanin as a volunteer commented