Timeline for How to prevent accidental clicks in the Save button when saving a node?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 5, 2013 at 10:24 | vote | accept | chefnelone | ||
| Apr 5, 2013 at 10:23 | vote | accept | chefnelone | ||
| Apr 5, 2013 at 10:23 | |||||
| Apr 4, 2013 at 10:57 | answer | added | chefnelone | timeline score: 1 | |
| Apr 3, 2013 at 12:41 | answer | added | Interlated | timeline score: 0 | |
| Apr 3, 2013 at 11:39 | comment | added | Interlated | There is an autosave module, although my experience with it is mixed. However, there is a form_id generated with every form load. This should be used to prevent duplicates. | |
| Apr 3, 2013 at 10:03 | comment | added | chefnelone | I also thought of rule being fired just before saving the node. | |
| Apr 3, 2013 at 9:48 | comment | added | Alfred Armstrong | Yes, I'd go for your option 2, either by using the Rules module or writing a custom validation handler which performs the appropriate checks. I suggest you carry out some experiments to determine the best logic so if someone accidentally presses save twice they don't see a worrying error message. | |
| Apr 3, 2013 at 8:27 | answer | added | prathk | timeline score: 0 | |
| Apr 3, 2013 at 8:00 | history | asked | chefnelone | CC BY-SA 3.0 |