I have been playing around with the 6.x-1.0 release and while I love what the node expire does, It appears that any time I edit a node, the expiration time is reset to '1 Day' instead of my default setting of '2 months'. It basically is not holding the default setting.
Default Setup:
Expiration Type: Expire after last update
Expiration Time: 2 Months
Expiration Date: +3 Months (default setting & "shouldn't" be used because of the set Exp. Type)
-------
I personally would like to use the Expiration Type of 'Expire on Date' but it seems that the whole 'default date entered is in the past at the node post time' issue is keeping me from re-editing a post. I would love to have a content type setup for users where a node will expire after say, 2 months (+2 months) but they can edit the node at any point between the node creation date and the expiration date but not have permission / access to physically change the expiration date. I guess I don't really understand the statement of: 'default date entered is in the past...' and why it is causing me issues, when I have the expiration set to the future... ??
I realize this is a separate issue from the initial one but still one that I wouldn't mind having some clarification on :)
Thx for porting this to D6! I've been waiting about 6 months for something along the lines of this module!
Comments
Comment #1
mattbk commentedI seem to be having the same issue.
Comment #2
brmassa commentedGuys,
bug fixed on 2.0 version.
regards!
massa
Comment #3
brmassa commentedim proud to say that its now integrated!