Posted by greggles on October 28, 2008 at 11:22am
Jump to:
| Project: | Killfile |
| Version: | 7.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | thekevinday |
| Status: | active |
Issue Summary
Is it possible to use this for things other than content? I see this as a way we can get our generic recycle bin, if you're willing to provide that ;)
Comments
#1
Hey Greg,
Not at present, but I did write it with that later potential in mind, e.g. naming the existing table and functions accordingly for node-specificity so as to allow room for later genericity (if that makes sense :-))
Which things are you specifically interested in? This, of course, goes back to The Question, i.e. whether everything in Drupal should be a node or not :-)
#2
Greg, I hope I'm not being overly presumptuous, but I've just granted you CVS access to the project in case you wish to collaborate directly on this in some form.
#3
Well, I don't know how much I'd be able to help. My specific case is for Pathauto - I'd like to be able to delete old aliases and have the ability to bring them back if the user changes their minds...
#4
This is a few years old.
Is this still requested?
If so, I can add this to a todo list for a drupal 7 2.x version of killfile after the 1.x is released for drupal 7.
Otherwise I am going to close this in a few weeks.
Is this alright Arto?
#5
I think it would be nice to have still. Updating version, component, and category to better reflect reality.
#6
Okay, then this will be looked into following the stable 7.x-1.x release.
#7
I am thinking the solution is to write a library that handles delete states in drupal and then write two separate modules that use it:
- killfile 7.x-2.x
- killalias 7.x-1.x
Perhaps I should call the library libmafia?
Edit: make that 3 modules:
- killfields 7.x-1.x (see https://drupal.org/node/1059134)