I have been using WordPress since February and have updated the software faithfully on each new release.
I have noticed an odd behavior that has started to occur only in the past two weeks. The usual behavior of WordPress is once and edit is saved or a page writen and saved, the “write post” page refreshes and I have an option to “view site.” However, for the past two weeks this does not happen. The edit and the new post does show up on the site, but the “write post” page goes blank after it thinks for about 30 seconds to a minute. It never refreshes.
This has never happened before and I made no changes to MySQL, PHP or WordPress during this time. I am running this on Windows 2003 Server (not RC2) and I do keep Windows 2003 updated – I am hoping this is not the source of the problem.
I have no idea how to troubleshoot this so I am hoping for some ideas. If it helps, I am not PHP savvy.
]]>help!
]]>Instead of doing this for *every* story I’d like to be able to go to the write post options page and to set a timestamp there and this will automatically set for all new posts.. (so instead of it querying the current time when it loads the write posts screen it will query the set timestamp time and use that)
That way I can edit the timestamp once a week and save lots and lots of work.
This will also have the advantage of not needing the sub-eds as level 5 users as they currently are for editting the timestamp, but should really be level 3..
So how would I go about doing such a thing? I’d ideally like this feature as a plugin but hacking would do too. I’m happy to work on it myself but need a lot of guidance! Or a nice bored person is welcome to have a go themselves
Thanks!!
]]>Is there any plugin or hack out there that might provide that link within the Write Post pg.?
]]>Additionally, when I add a post, it takes ages for the next page (that says it’s been posted) to show up, even though I can see my updated blog immediately. Again, this extended delay doesn’t occur for posting pages, editing themes, plugins, etc., so I’m guessing it isn’t a bandwidth/connection issue. Could the two problems be related?
]]>