unoamigo

Here you go, I think the code is pretty well rounded out now.
New topic area for WP 1.2 statistics, to make things a little less confusing.
Thanks GamerZ for getting the original one out the door!

Yeah, a great chunk of it is already compatible, I’m making it into a plugin that will work simply by adding a line or two of code into your index.php file.
No real point in being forced to duplicate your index file to create a good looking stats page.
It’s also good to support the plugin format of 1.2.

What version of WordPress are you using?
The version GamerZ has out is not yet compatible with 1.2. I’ve almost got a 1.2 version done.

With 1.2 you can create your own functions and use them as PlugIns.
I’m not sure which functions you want to edit. Start with looking in: wp-includes

Sure, put the line break at the start of each post. Course, then you will have one at the top of the page. ?? That might not be so bad depending on how your page is designed.
If you really wanted I’m sure you could go in and edit the PHP to make an exception based on the last post. But that probably isn’t worth the effort.

There are a number of changes in the works for WordPress 1.2, it won’t be released for a little bit yet. It’s rumored for 1.2.
Other people have noted (and I can verify) the lack of a image upload button in the posting page.
As for image editing having a thumbnail generated at all is new to WordPress 1.2. Lots of great individuals are putting an enormous amount of effort into making this product. 1.2 offers a great deal of changes that should make it easier to add in functionality.
Enjoy WordPress!

If you start with a fresh install of WordPress it will tell you an initial password.
What happened when you tried to use the one it gave initially?
Were you never able to login?
You can also change the e-mail address assigned to the user in your MySQL database, then when you use the “forgot password” form you will get a e-mail at that address for sure. If the case is that you haven’t entered a e-mail address in for that user yet (or entered a bogus one).
I’m not certain why your having to use a javascript to get the md5 hash when WordPress will do it for you.

Try, resetting the password, deleting all relevant cookies, and then logging in using the new password.
Solved a similar problem for me.
E-Mails from your domain with the wrong dates, could just be a server side issue – where the dates need to be reset. This could be completely out of your control, ask your host.

Delete your cookies to your site. With Safari I had the problem that it was sending the password stored in the cookie rather than what I was entering.
It would not surprise me if other browsers (IE) also experienced a similar problem.
You will now also probably have to reset your password (again), since you changed it directly in the database.
Lets see what that does for you. ??

You will probably want to contact them and see what their apache settings are.
This assumes your .htaccess file is written correctly. Be helpful to post that here too.

1.2 has a search/highlight plugin that it comes with.
Not sure if there is a hack out there for 1.x, but you could always bump yourself up to the 1.2 beta. ??

I’d be tempted to wonder if your just having a small connection problem. Your web browser times out and resends the data for some reason?
I’ve never experienced the problem you are having, but I have had it fail to reload the post.php page since I never hear back from the server. (with safari)
Give a different web browser a spin for a while and see if it repeats itself. A different web browser will handle time out operations slightly differently.

Well, after going through the database – to make sure the settings were changing properly (they were). On a hunch, I ran the upgrade script again. Oddly enough this solved the problem.
Maybe there is a bug wrapped up in there somewhere. Unfortunately, I don’t know that this will be an easily repeated bug.
Since that seems to be working, maybe in the next couple days I’ll upgrade my site to 1.2. (currently running locally)

Delete the appropriate cookie files and the problem will be resolved. Safari is trying to log you in based on what is in their cookie file, rather than what you type in.

Oh yeah, I’m on the delta release now, I’ve seen this problem for the past several days of nightly releases. Also including the original 1.2 beta release.