iamnino

I’m having these issues too. I am on brand spanking new rackspace hosting with 1 webserver and 1 database server and WordPress version 2.5.

1. I can’t schedule a post for anything under an hour. If I do, it immediately publishes.

2. For anything scheduled over an hour, it will count down as expected, hit 0, not publish, keep a status of scheduled, then count up. So If it’s 12pm and I schedule something to post at 1 pm. It won’t publish. Then if I checked it at 2pm, It would tell me it will publish in an hour. Then at 3pm it will tell me it will publish in 2 hours. Etc. Etc.

My client is flipping out because this is a tool they heavily use. I’m stumped.

I would have done that in normal circumstances. However, you’re assuming that everything is fine on the original hosting, and that this is simply a leisure transition from one hosting to another. Well it wasn’t.

The hosting was shit, due to what I expect was internal network problems of their own or shitty hardware. At times, it would take between 30 seconds to a minute before the browser would even reflect the change in the page title from the site you were previously on. My client didn’t want people still visiting the old site REGARDLESS if their dns had propagated or not.

That being said, I had to redirect to the ip address of the new hosting (which is running as it should) and if I had the Blog address (URL) set to the domain name, it would have sent them right back to the crap hosting, putting them into a redirect loop.

I still stand by my opinion that that this should be an OPTION to turn on and off, and I will thank-you kindly if in the future you would get more details about a situation before casting insults, showing contempt, and using a condescending tone towards somebody you don’t even know.

Still need help here.. I have new comments coming in, and nothing shows up until I do a search based on something in the comment. I’m having to moderate via phpMyAdmin. Bogus!

I’m still not game. I think it should be an option. My client’s site doesn’t require users to be logged in to comment. Actually you can’t login unless you’re a writer. So moot point there.

As for bookmarking a site correctly? Are you kidding me? I don’t care if they bookmark https://www.blah.com https://blah.com, or the ip address. It all goes to the same place.

As for you thinking it’s JUST one query. It’s not about that it’s the BAM BAM 2 db connections. You realize there is such a thing as max connections to your db right? If that’s maxed, then woops wordpress will not connect to the db. When you have thousands of visitors a day, connections add up quick.

Want another reason I think it’s lame? I just had a client switch hosting. The client wanted a 301 redirect to the new site. However I couldn’t put the domain into the Blog address (URL) because the 301 redirect had to redirect to the IP. What does this mean? For somebody who’s dns hasn’t switched yet. They would be redirected to the new site only to be redirected back again and are now in an endless loop between wordpress. Also, since wordpress hard codes image urls, it means that means that new stories written under the domain name instead of the IP won’t show up for people with the incorrect dns, because it will be looking for those images on the other domain, where they won’t exist.

Ultimately it should be an option. Not something forced.