My hosting provider can't set the computer's date correctly

If the node type has an nid then scheduler will join with it. I don't know how CCK could affect this operation.

The timezone is stored with the publish/unpublish time (Drupal has a timezone setting itself and if no timezone is entered on the node edit form then that is used). I've been around the houses on timezones and fixed a number of previous issues/problems in teh past. The timezone has been stable for some time now and your report is the first problem for a while. So I'll need more info (like what is the raw table data for a node, in the {scheduler} table).

I have the same problem - The timezone is disregarded by scheduler. Wheather I set the timezone included with scheduler, or I use the site's timezone (GMT +0400), scheduler still doesn't notice it. Now I have to set publishing dates/times to server date/time (GMT -0700). So if I want something to be published at midnight, I'll have to set it to my time minus 11 hours, (e.g. instead of 2007-07-30 00:00:00 it has to be 2007-07-29 13:00:00). By the way I use drupal 5.1 and scheduler 5.x-1.4 and the fields are CCK fields.

This is the raw table date from the scheduler table:

nid  publish_on    unpublish_on      timezone
854  1185753600    0                 14400

Please try version 5.x-1.6 (just released). You do not need to run update.php after installing this. Please note, all I did in this release was add the "scheduler/timecheck" URL for your sites. If you go to that URL it will show you your servers time setting. All servers should be set to UTC and have offset's applied (see http://uk.php.net/manual/en/function.time.php).

If your server's internal chronometer isn't set to UTC (London GMT) then your server is misconfigured and it's that that needs fixing, not scheduler.

Note, the raw data show below indicates to me the server's clock is set incorrectly as the data in the database tables is correct. Some Unix System Admins are lazy when it comes to setting up Unix and just use "local time" when setting the Unix clock. The correct way to setup Unix is to set it to UTC (GMT) and then configure what timezone the machine resides. Some don't bother and then you end up with a server that just doesn't return the correct time.

Note, the raw data show below indicates to me the server's clock is set incorrectly as the data in the database tables is correct. Some Unix System Admins are lazy when it comes to setting up Unix and just use "local time" when setting the Unix clock. The correct way to setup Unix is to set it to UTC (GMT) and then configure what timezone the machine resides. Some don't bother and then you end up with a server that just doesn't return the correct time.

I think this would be the problem, because I'm having this (time) problem somewhere else as well. As for scheduler timezone problem it still persists, however, I think I can live with setting the time to the server time. Thank you for your help.

If the server's time is setup incorrectly it will affect many things, not just scheduler. The solution is to get the server's time to be set correctly and it solves all the problems.

If you need a around specifically for scheduler you can hack it up and add it in if you want to. If you don't have the ability to do that yourself you could always commision it to be done on a fee basis (if that sounds offensive then think from my and other contributors point of view, scheduler is free but people are happy to pay for sloppy workmanship on companies/hosters that cannot even get the date right on a computer and I for one am not about to start doing more free work to cover someones elses laziness or incompetence ;)

Failing that, you could always talk to the people you are already paying (and therefore you are their paid customer) and DEMAND they get the basics right.