- current delete cycle - not much modules can do during delete cycle, closed system
- undo modification - user can recover the data through an undo interface (data put in a "deleted" table)
- advantages - improved UI, no confirm screen, less chance of critical data loss
- current thing is to only respond to node_delete's calls
- modules should have say so
- possible implementation: deleted table with did, type, table, data, timestamp
- add drupal_delete() and drupal_undo()
- Chris Messina: have a trash can exposed to user
- node delete = admin concept only
- trash for user
- re-use trash concept for SPAM
- Angela's opinion on Form API:
- breaks backward compatibility with 400 contrib module (legacy.inc)
- backwards compatibility until 4.8
- alternative is for small team to fix the contrib module
- Karoly's thoughts - removal of legacy.inc proposed by Gerhard and Karoly, it is possible to make node_hooks work
- it could work, but then legacy modules couldn't use the features of the forms APIs
- Chad - developers are saying they need more time, just got servicable docs in the last week
- Adrian - if we enable legacy, old validation won't work with new validation system
- Need to discuss in the other room and come to a conclusion by the end of DrupalCon
Original publication
This post was originally published on October 19, 2005 on The Standard, the Raincity Studios blog, credited to “Roland Tanglao”. This post reflects the context and tools of its time; some links and services mentioned no longer exist.