Thread

I’m trying to post an entry in a weblog for shortly after midnight, so that it will show up on the following day. Weirdly, although the date is correct, the calendar seems to be malfunctioning (see attached image). As a result the entries don’t show up—they need to be reposts many hours after the fact to work. They do show up if I show_future_entries though. When I click on the data in the JavaScript calendar, it updates the date in the text box, but if I save it and then click edit again, I find the date is back where I’ve started.

This seems to be a problem since I updated to the most recent build, 20080319.

I’ve cleared out caches multiple times, and I’ve been going through and re-uploading files in case any were missed or corrupted in transfer (including js_calendar.php). No luck…

Does anybody have another idea about what might be going on here?

Thanks.

I’m trying to replicate and failing.  How’s the mismatched date getting in there?  Do you hit ‘Today’ at a little after midnight, or… can you walk me through that?  And then let me know- is the data showing on the frontend the same showing in the date field?  And if you go back and edit it, no matter what time you put in it reverts back?

Also- if the data is showing correctly in the publish form, it should be correctly in there.  Cache is the one I’d suspect.  But- doesn’t look like that’s what it is.  Did you clear out the cache manually?  Via ftp?  Might try that to be sure it’s cleared out.

Lastly- are you running any extensions?

Robin,

I’ve tried multiple ways of setting the date—manually entering it, clicking on the day in the calendar, or clicking the “today” like. Also, I’ve tried clearing the caches both manually and through the control panel.

I am running a bunch of extensions which I haven’t updated with the new upgrade—these are:

Filter By Author (v.1.0)

Textarea Resizer (v.1.0.0)

Simplify Edit Table (v.1.1.2)

Edit Tab AJAX (v.1.2.1)

NoFocus (v.1.0.0)

Tag Submit (v.1.0.1)

Thanks for your help.

centerdesk, I don’t believe the problem is with your extensions.

You mentioned you upgraded to the newest build. Which build/version were you on previously?

If you set the time part of the post to be 1:01 AM, does the date come up correctly then?

Two other factors could be at play here.. DST, and/or Server time.

What are your settings for that?

Hi Sue,

Hmm.. I think I was on the next-to-most recent version, not sure exactly which build. I’ve been keeping up with updates pretty well.

The server is on CDT now (CST + DST). Server time zone in the admin panel is UTC -6, with no offset. The account of the user who is doing the original postings is set for CST as well. “Daylight Saving Time” and “Honor the Daylight Saving Time setting associated with each section entry?” are both set to yes, although I’ve played with turning these on and off to no avail. Setting things to 1:01 (or many other odd times) doesn’t seem to help.

*Sigh*—Any more ideas? Thanks for all your help!

I just did a repair/optimize all tables, and cleared the cache—no difference.

Still, e.g., when I hit “today” the text-version of the date is right, but yesterday is highlighted on the calendar.

Here’s an image of what’s in the database:

...and the template is a pretty straightforward weblog:entries tag:

{exp:weblog:entries weblog="{section_name}" orderby="date" sort="desc" limit="12"}

The only weird thing is that we are only using the entry date in each entry—all other fields are optional, and everything is built off of that entry date (e.g. the filename for the podcast and the title that shows up on the public site).

This is just weird.  Happens with different browsers as well?  And since I’m running out of ideas- try disabling extensions.  Like Sue says, nothing is jumping out at me, but I fail to replicate and it can’t hurt to narrow things down.

If you hit the main ‘Disable Extensions’ tab top right, should disable them all w/out removing them. 

And aside from the calendar borking- is it otherwise working as expected- the dates match the text display, behave as expected, etc?

Hi Robin,

Let me try the extensions, but the main problem for us is thst the entries are not showing up—they can be reactivated some time later in the morning (5:49am worked today - This is a daily podcast.)

centerdesk, I have a similar problem on my primary client’s box, but not with EngineHosting. I haven’t checked on it again recently, but I did notice in the screen shot that the value for dst_enabled is set to n for no.

Can you double check those settings?

Sue,

I’m sorry for the delay in replying here. Time for big-hunting has been elusive lately, but this is indeed something we need to get resolved.

You’re correct that in the database dst_enabled is set to “n” even though under System Preferences > Localization Settings both “Daylight Saving Time” and “Honor the Daylight Saving Time setting associated with each section entry?” are set to yes.

We weren’t hosting this site at EngineHosting until a couple weeks ago—so the probelm has persisted across servers. The site is set to CST.

Another weird thing—if if there was a dst issue, would that just throw things off by an hour? The same problems recur if we set the original time to after 1am.

Does anyone else have ideas about what could be happening here?

Also, let me add that we’ve seen this behavior on at least three different weblogs.

It is hard to detect a real pattern, but maybe we can say this: “one can usually correct
a post-dated podcast by hitting update a second time but only after the time
it was supposed to post.”

The ‘update’ fixing it almost sounds like a cache issue- though doesn’t explain why the wrong date would show in the js calendar.

Next time it happens- if you just go in and clear cache via ‘admin- utilities- clear cached data’- does it show up?