I have drupal 6.10 installed and rules 6.x-1.0-beta5. I imported rule in the readme file to unpublish expired content. I set up a content type with +1 week as the default expiration date, but users can change that, of course. The expiration date in the content creation form is correct, but when I attempt to edit any content with an expiration date, the edit page automatically changes the expiration date to yesterday and then I cannot save changes until I change the date to something in the future.

Also, even though I have the rule set, none of my nodes set for expiration ever unpublish.
I had phpFreeChat installed for awhile and that seemed to really mess up the dates for expiration, always setting it to 1969-12-31, but I have since unistalled that module.

I would appreciate any assistance as to what might be going on.

Comments

pgrayove’s picture

pgrayove commented

I wanted to update that it does not set the date to yesterday when editing a node with expiration, instead it takes one day off of the expiration date every time the node is edited. So, if the expiration date is set to 2009-04-23, the next time the node is opened for editing, the expiration date will be set to 2009-04-22.

pgrayove’s picture

pgrayove commented

Update: the nodes are unpublishing upon expiration, but if a node with expiration is edited, it does still take one day off the expiration date in the edit form. The expiration date must be reset each time the node is edited.

joemaine’s picture

joemaine commented

I don't have phpFreeChat installed but the dates for expiration, are also always setting to 1969-12-31

giggler’s picture

giggler commented

mine also shows as 1969-12-31 even if I leave the Expiration Date Limit blank. If I put in 2039-12-31. it says you have to use the PHP strtotime format.

I've also try to just not give roles the permission to see the date, but when you do that, it's as if no date is set and it will say you must set a date value and the node does not get published.

EDIT: setting the Expiration Date to 2037-04-27 gets accepted..but setting it to 2038-04-27 and up give "This values should be in PHP strtotime format."

fletch11’s picture

fletch11 commented
Priority: Normal » Critical

I'm getting this also but can't tell if this module is still being maintained. Appears to be a critical bug, since most users wouldn't want all nodes to have an expiry date.

regards, ian

joel-2’s picture

joel-2 commented

We're seeing this as well.
Date is preset to 1969-12-31, and drupal won't accept the submit as a valid date.

Are there any known workarounds or patches?

Joel

barckhoff’s picture

barckhoff commented

I am having a similar issue. I currently have Drupal 6.11 installed. Also using the "copy & paste" rules in the README.txt file.

I've enabled the Node Expire for a custom content type, set to expire after one month. All the other content types should not have the expiration. This is true for all except the Image content type, which defaults to 1970-01-01, even though when I view it in admin/content/types there is no default date set.

Also, the date that I set for my custom content type gets saved as one day earlier than the one I selected.

Hmmm...

barckhoff’s picture

barckhoff commented

OK, I just did a bit more searching and found this code change that fixes the 1970 default date in the content type which shouldn't have it.

http://drupal.org/node/405608#comment-1580518

Hope this helps others! Still searching for a fix for the -1 day "feature"...

barckhoff’s picture

barckhoff commented

It appears that my -1 day error was server specific, but I was not able to pinpoint the issue. Perhaps a PHP configuration issue.

vikramy’s picture

vikramy commented

Closing this.. Please reopen if you still have issues.

Also take a look at http://drupal.org/node/405608..

vikramy’s picture

vikramy commented
Status: Active » Closed (fixed)