Timeline for The 'drupal' way to implement delete button UI: part 2
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:47 | history | edited | CommunityBot |
replaced http://drupal.stackexchange.com/ with https://drupal.stackexchange.com/
|
|
| Apr 22, 2015 at 2:01 | vote | accept | Kevin Ard | ||
| Apr 21, 2015 at 5:44 | answer | added | AKS | timeline score: 0 | |
| Apr 21, 2015 at 3:09 | comment | added | Kevin Ard | There's other validation going on in rm*. Eg: does this user own this item, etc. That's the part that got redundant | |
| Apr 21, 2015 at 3:02 | comment | added | Kevin Ard | Yeah, basically. Drupals different from other frameworks, and most of what I know comes from classic OOP and js. So I was wondering if I'm trashing the way drupal works :) The switch router seemed to be a little more maintainable to me. In practice, there are far more of these methods, and they're all identical except for the actual crud they call. My cpd would go crazy over that. Is there reason to bypass the switch and call crud directly? If I were to keep it as is, I'm sure I'd reduce it to a single menu registry and pass two arbitrary values - essentially bypassing hook_menu when it comes | |
| Apr 21, 2015 at 2:54 | comment | added | Chris Rockwell |
Are you just asking for a review of the code? Why do you route through bluenose_app_rmelement() instead of calling the correct callback in hook_menu()?
|
|
| Apr 20, 2015 at 20:40 | history | asked | Kevin Ard | CC BY-SA 3.0 |