Download & Extend

Expiration date limit required bug in 6.x-2.02?

Project:Node expire
Version:6.x-2.05
Component:Code
Category:bug report
Priority:critical
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

Apparently we cannot submit nodes without setting an expiration date limit.
I tried:
- Setting just the expiration date on a content type, no other setting
When you try to submit a node you get the following error: "It must expire before 1970-01-01."

- Setting the expiration date and enabling scheduled (un)publishing, no other setting
Same error, even though all fields were filled...

Can anyone confirm?
Ricardo

Comments

#1

Are you using the v1 or v2 of node expire? It sounds to me like you are using v1 but you have v2.02 as the problem version.

Update:
Never mind, I installed 2.02 and I see what you are talking about now.

I noticed that there is a "Default Date" and a "Max Date"

I set them both to something like +45 days and it seems to have liked it.

#2

I can confirm. I have the same problem with the node expire ver. 2.02.

Can not submit new content without setting an node expire in ther workflow settings.

#3

Status:active» fixed

Guys,

im sorry. i deleted a piece of code to make a test and i forgot to put it back before commit. fixed! soon on the next release.

regards,

massa

#4

thx massa

#5

Thanks! Apparently it's fixed on 2.03 but I haven't tried it on a clean install.

Ricardo

#6

Sorry with 2.03 i have the same problem :(

#7

I had the same issue with the 2.03 module as well, but I think i managed to track it down to the node_expire.nodeapi.inc. line 25.

  
    case 'prepare':
      if (!isset($node->expire)) {
       
        //patch code begins, make sure we don't pass an empty variable to the format date function.
        if(!empty($ntypes['default'])){
          $node->expire = format_date(strtotime($ntypes['default']), 'custom', NODE_EXPIRE_FORMAT);
        }

      }
break;

otherwise the format_date function passes a default value of '1970-01-01'.

#8

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

#9

I'm getting this also. Anyone else?

#10

Status:closed (fixed)» active

Hi, it's work fine when i create new content, but when i trying to edit existing content i get 1970-01-01 as default value

#11

Hi, I posted a solution here.

Hope this can help somebody.

#12

Thank You, Tororebelde!
Your solution work fine for me. :)

#13

Nevermind! ;D

#14

Status:active» closed (fixed)

Take a look at this.

http://drupal.org/node/405608.

#15

Version:6.x-2.02» 6.x-2.05
nobody click here