mikep

bkpatton: Look at the source of your faulty displayed page in a browser…I see a wp-comments.php reference still in there for the form. Did you change index.php?

xinxin: I agree we can manage the problem but felt I ought to try some offensive measures (I got six open proxies closed recently). The spammer is now doing it direct, AFAIK, so I’m complaining to the ISP/host. Yes, I know he’ll move and pop up again but let’s make things difficult for a day or so. Take a look at what netaloid.com is try to do about the p*ker spammer too.

I did that. Very carefully. And then checked it, twice. Just swapping the comments.php file did the trick.

I agree with iJeff1 to some extent. I had this problem and simply used the new 1.5 comments.php instead of the old renamed 1.2 version. However, if you’d changed comments. php for whatever reason, then the advice was good. But I still don’t know what it was that caused comments not to be displayed after the upgrade. I’m also using Linux and xampp for testing 1.5; my live blog is still 1.2.2. That way, I can sort out such problems without too much grief.

Cracked it. Comments-popup must contain the line
‘@import url( <?php bloginfo(‘stylesheet_url’); ?> );’ to refer to the style. And I replaced the old comments.php with the new 1.5 version. Now for more testing… I like what I see in 1.5!

Hmmm. This is one of my issues too. I’m currently testing 1.5 with Linux/xampp and solving it is on my to-do list. Also, my comments pop-up isn’t styled. It feels like a simple mistake or two somewhere, so I’m going to go through the changes again very carefully line by line.

I had some spam on p&ker yesterday…same ruse with suspended-for-spam.com. And this time the spammer wasn’t using an open proxy…it was direct from him at 216.195.44.106 (this address was seen in open proxy access logs previously).

What’s the IP giving you the problem? Is it one IP or many? Time to do some digging and complain to the upstream ISP.

I’m now getting comment spam directly from 216.195.44.106 rather than via open proxies. (see my earlier post above) Words include chinese, yellow, monkey, ape and p*ker.

I had login problems with xampp and Windows when testing 1.5. I switched over to Linux (still using xampp) and the login problems disappeared. Strange.

And I’ve now installed1.5 under Linux where I don’t see those login issues…I can now play with 1.5 and test the upgrade from 1.2.2 without worrying.

I have hit some WordPress issues now…to do with logins as mentioned elsewhere in the forums. However, xampp is a superb tool that I’m enjoying.

Right, gone further now. Using Podz excellent 1.2 > 1.5 instructions, I upgraded the local copy of WordPress to 1.5 with no hitches. I can now play with 1.5 without disturbing the live blog on my host. Cool.
Podz – any comments on uploading 1.5 from the local copy? The 1.2.2 hosted database is growing, of course, so at some stage that’ll have to be dumped and restored into the 1.5 version before uploading/restoring. What issues are there to think about?

hillbilly: this is what works for me. Click the xampp control panel icon or browse to c:\apachefriends\xampp\xampp-control.exe and click that. Then in the panel, start apache, start mysql. Then fire up browser to https://127.0.0.1 All should be well. Follow Podz’ instructions when setting up a copy of WordPress. I dumped a working copy of WP from my host, restored that under htdocs. Also dumped the database and restored. Do all the changes Podz mentions to the SQL (before restoring) and wp-config. It will work.

I’m very impressed with xampp. I backed up from my host and restored a local copy of 1.2.2 and the database following Podz excellent instructions. It will be useful for 1.5 migration. When I’ve tested 1.5 out thoroughly, are there any issues to watch for in reversing the process i.e. upload the local working copy of 1.5 and database (latest) to the host? Now I can run WordPress locally for testing/evaluation/tweaking, I’d much prefer to work that way.