Add to Plone a view for changing (cheating!) creation and last modification date
You are a site administrator? Maybe you already saw use cases below.
Use case one
“Hi, I deleted an importan content created yesterday. I created it back but for $INTERNAL reason I need that this content seems created yesterday, before 02:00 P.M.”
Use case two
“Hi, I accidentally modified an old document… or better: the change was needed but for $INTERNAL reason I need it seems again ‘old’ ad before. Can you restore the last modification date to January 2008?”
The collective.datehacker product add to Plone a simple new view that you (the site admin? a smart user? every users in the portal) can use to change two of the most untouchable date inside Plone contents: the modification date and the creation date.
If you are trained enough, you can change those dates in few lines of code, but maybe:
- you don’t know how to write code
- you are lazy
- you don’t have an account with Manager permissions
- none of above, but you are sure that, sooner or later, someone will ask again for the same change.
Also this product can be useful after some big-migration activiti to Plone. May be that you or your users need to be able to restore some creation/modification date after the process.
No much to say, just call an URL like http://myplonesitehost/mycontenttype/hackdates then you can use the user friendly form
The form can only be called from users that behave the “Hack content’s dates” permission.
You can call the hackdates views where you want.
- Register someway, somewhere, the hacking operation
- Test on Plone 4 (it must work, but is untested)
- Initial release
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size & hash SHA256 hash help||File type||Python version||Upload date|
|collective.datehacker-0.1.0a-py2.4.egg (15.7 kB) Copy SHA256 hash SHA256||Egg||2.4||Jan 17, 2011|
|collective.datehacker-0.1.0a.tar.gz (16.4 kB) Copy SHA256 hash SHA256||Source||None||Jan 17, 2011|