Closed (works as designed)
Project:
Scheduler
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
19 Apr 2010 at 18:15 UTC
Updated:
1 Apr 2011 at 17:04 UTC
Jump to comment: Most recent file
Comments
Comment #1
eric-alexander schaefer commentedIt does. What date format are you using and what is the date/time you entered?
Comment #2
myst.riven commentedI am experiencing the same thing and have a similar question. In the past, I had trouble putting a custom date format, so my setting has the default right now: Y-m-d under Scheduler module settings.
When I enter 2010-05-03 today (today is May 3rd), it comes up as an error and asks me to enter a future date.
If I enter tomorrow's date, the node can be saved and I can see it under Content Management > Content > Scheduled
I know that tchopshop wants to unpublish at a later hour. As I check my site's schedule, it's showing as Tue, 05/04/2010 - 00:00
Can you please explain to us on how you would do it? Thanks.
Comment #3
eric-alexander schaefer commentedThe time is always 00:00:00 if you do not enter a time because your date format omits it. If you enter todays date 00:00:00 will always be in the past. What do you expect? When should the node be published? If you want to publish today at a later hour you need a date format with time and you need to enter a later time.
Comment #4
klonosGood catch Eric! How didn't I think of that?
How about then in such cases 'forcing' the time to be set to 'now' (perhaps even now + 1sec). I mean store the date+time as a timestamp no mater what format was chosen as display. In other words, convert to full date+time every time, even if chosen format omits time.
Comment #5
eric-alexander schaefer commentedYou can just omit the scheduling date if you want to publish now.
Comment #6
klonosYes... I realize now that perhaps it was a long day for me when I posted my comment. Perhaps I should have gotten some sleep before posting :D
Comment #7
eric-alexander schaefer commentedComment #8
jyee commentedI'm receiving the same error when trying to publish at a later time in the current day.
My scheduler settings date format is Y-m-d H:i:s and uses the Date popup field
On my node add/edit form I select today's date using the popup and it correctly populates 2011-03-17. In the time field I've entered 14:00:00
When running date('Y-m-d H:i:s') in php, it tells me that it's currently 2011-03-17 13:42:41 ... so that means the info i've entered should correctly be in the future.
If I change the time to 17:00:00, the time is accepted. After playing with the time a bit more, it appears that the time must be +3 hours or more in the future.
edit: forgot to set the version when I submitted. This is with 6.x-1.8
Comment #9
jonathan1055 commentedHi,
Is this something to do with your sites timezone and/or server timezone. Could you give us details of what timezone you are working in? Also can you go to the timecheck tab on the admin scheduler settings, and post a screen shot or tell us the time details it shows.
Jonathan
Comment #10
jyee commentedtimecheck screenshot attached. One interesting thing to note is that it's set to UTC -7, although with daylight savings time in effect, it probably should be -6.
Comment #11
eric-alexander schaefer commentedThere are different time zones involved:
- The time zone of the server OS.
- The default time zone of your drupal installation.
- The user time zone (if user configurable time zones are enabled).
Please check if they are all three set to the correct values. E.g. since you appear to be somewhere in the americas your servers OS should be set to where the server is, the drupal default time zone should be where you are and the user time zone should be where the user is.
Comment #12
eric-alexander schaefer commentedWell, it was probably to clear why I was mentioning the americas: Large countries like the Canada, the US or Brazil have more than one time zone. That's why I guess that user configurable time zones are enabled in your installtion.
Comment #13
jyee commented@Eric Thanks. I'd completely forgotten about user time zones. That appears to have solved the discrepancy.