I'm getting some weird behavior from days=n.
I have a "daily index" on my site with my MTEntries set to days=1. Theoretically, that page should always display posts less than 24 hours old. If it's 24 hours and four minutes old, it shouldn't be there, right? If it's 23 hours and 57 minutes old, it should be there.
It almost always works, the lone exception being when there have been no posts during the last 24 hours. On such occasions, I'd like my "daily index" to be blank. However, I'm finding that it will actually show posts that are more than 24 hours old if there were no posts in the last 24 hours. It's like the page just can't stand to be blank.
I haven't actually seen this happen when I was looking directly at the web page, but I know it happens because I have a chron job set up that emails me the "daily index" every day at 10:30 a.m. That is, it emails the web page itself, however it appears at 10:30 a.m. And if nothing has been posted during the last 24 hours, I see that the page (in the email) includes entries more than 24 hours old.
I use the chron job to keep my listserv subscribers current on items posted since 10:30 a.m. on the previous day -- that's why I don't want the page to include entries more than 24 hours old. Works like a charm, except when there haven't been any posts, in which case me and my subscribers get an email that shows posts more than 24 hours old. ...And if it's Monday, the email always contains posts from Friday. That makes no sense because by that point it's been more than 48 hours since Friday. But since nothing was posted on the weekend, it includes Friday posts.
Since my chron job is by all appearances perfectly reliable -- I can see in Outlook that delivery always occurs at 10:30 sharp -- then I have to conclude that days=1 is not reliable when there isn't a steady stream of posts. Correct?
Would the DateTags plug-in be more reliable?
Thanks.