When using the scheduler module, the (unused) unpublish date is getting set to "1969-12-31 19:00:00" upon submit instead of being set to "blank" or null. This is a problem (in my estimation) because the story's meta info gets updated to include ---- 

<META NAME="GOOGLEBOT" CONTENT="unavailable_after: 31-Dec-1969 14:00:00 America/New_York">.

This is incorrect right? Or is googlebot ignoring this?

Comments

AjK’s picture

AjK commented
Status: Active » Postponed (maintainer needs more info)

Just retested and was unable to reproduce this. Can you provide more info (such as timezone etc)

AjK’s picture

AjK commented

btw, sounds possibly like you are not actually running 6.x-1.1 as I had something like that eariler which was fixed in 1.1

Can you check that?

tuxguy’s picture

tuxguy commented

Using Scheduler 6.x-1.1 (confirmed).

System timezone (Default) set to -0500

User Configurable timezones enabled.

My user 1 (admin) timezone set to -0500

Is this enough info?

tuxguy’s picture

tuxguy commented
Status: Postponed (maintainer needs more info) » Active

I think I see my problem, but I am not quite sure what caused it.

My Scheduler table looks like:

nid 	publish_on 	unpublish_on 	timezone
115  	-18000  	-18000  	-18000
750  	-18000  	-18000  	-18000
769  	1203379500  	-18000  	-18000

It appears that if I go into any of my past stories and make an edit (a non-scheduler edit)... It causes the errand entry in the table (the 1969 date).

I am not sure why the timezone is getting written to the table like that either.

Ideas?

AjK’s picture

AjK commented

The timezone field is store in seconds offset rather than hours offset.

Normally, the offset is applied to the UTC times held in the other two fields on retrieval but in your case the calculated values seem to be stored rather than the raw UTC value. Puzzling indeed, I'll take another look later today.

Dranix’s picture

Dranix commented

I have the same. Drupal 6.1 with Scheduler. My timezone is +0100 and the table contains a lot of 3600's.

eric-alexander schaefer’s picture

eric-alexander schaefer commented
Status: Active » Fixed

Fixed in 6.x-1.2rc1

eric-alexander schaefer’s picture

eric-alexander schaefer commented
Status: Fixed » Closed (fixed)