Posted by drupalworld on May 9, 2007 at 11:11am
Jump to:
| Project: | Node expire |
| Version: | 5.x-1.0 |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | astoltz |
| Status: | closed (fixed) |
Issue Summary
Hello there and thank you for an interesting module.
Any chance that this "expiring" function could be attributed to one node type and not another?
Many thanks
Drupalworld
Comments
#1
Someone else is doing most development on this project now, but unless things have changed drastically, content is set to expire on a per-node basis, so per-node-type settings would be superfluous, I think. If you discover otherwise, by all means reopen the bug and we'll reconsider. Thanks for the report.
#2
It's allowed to apply to any node type, and has the special inheritance feature for the book type. I could definitely add a feature to allow you to hide the expiration options to a particular node type.
Did you have a particular node type in mind to make sure my code change will work for you?
#3
This feature has been added in the HEAD release.
#4
Hello there,
Thank you very much for prompt answers and actions!
My meaning is: if this module is only per node basis, the users can decide whether a node will expire or not.
If this could be per node node type (and here I mean CCK node types), then the admin can decide that all nodes from a certain type may expire after a certain period of time ( one month from creation for example)
That would be very useful for applications such as classifieds.
Hope you can understand my blabla :)
Thanks again,
Drupalworld