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

philsward’s picture

philsward commented

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.

bennos’s picture

bennos commented

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.

brmassa’s picture

brmassa commented
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

bennos’s picture

bennos commented

thx massa

rbl’s picture

rbl commented

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

Ricardo

jmaties’s picture

jmaties commented

Sorry with 2.03 i have the same problem :(

vik.nowak’s picture

vik.nowak commented

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'.

Status: Fixed » Closed (fixed)

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

fletch11’s picture

fletch11 commented

I'm getting this also. Anyone else?

zarudnyi’s picture

zarudnyi commented
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

japicoder’s picture

japicoder commented

Hi, I posted a solution here.

Hope this can help somebody.

zarudnyi’s picture

zarudnyi commented

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

gunjam’s picture

gunjam commented

Nevermind! ;D

vikramy’s picture

vikramy commented
Status: Active » Closed (fixed)

Take a look at this.

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

punithapary’s picture

punithapary commented
Version: 6.x-2.02 » 6.x-2.05