anonfx

I’m surprised we haven’t gotten more discussion on this matter. Accuracy should be something that has been tested and results shared with those using the plugin.

My Analytics and WP.com Stats numbers don’t line up either, and the discrepancy more than the number of people who are blocking Javascript. (Analytics reports Javascript support so I can see those numbers… of course that begs the question: how does it report a browser without Javascript support when it takes Javascript to run the Analytics script?)

I decided to not be lazy test the timestamping for pages in 2.5.

With a new page, setting a time in the future will postpone the page from going live (or being published) until the set time.

When making edits to an existing page, the edits show immediately, regardless of timestamp.

I agree with etsell. I completely understand the purpose of pages, but being able to set a future time on a timestamp for a page would allow that page, or it’s edits to go live at a certain time without the need to do it manually would be time saving. For example, on one of my client’s web sites, I’m using WordPress as a CMS and so I have far more pages than posts. It would be helpful to make a page about some special event at any time and be able to tell it to go live at a specific time in the future without having to leave it unpublished, then remember to publish it when I want it live.

WordPress 2.5 has timestamp option when editing pages, but I’m unsure how they affect the publishing of the page. I haven’t done any testing with it yet, and theres little to no documentation on the unique features of 2.5 as of yet.

Ok, so I think I have a workaround. I set the left margin for the drop down at -400px and the top margin increased by 10px or so. I’m not sure how well it’ll work in the long run, but seems to be ok right now. Now, I just gotta figure out how to make the drop down wider so the test doesn’t wrap strangely.

Also… the same bug occurs whether I let the theme’s CSS control it or the plugin’s optional CSS.