mikep

Or where’s the FAQ for the forum?… I see the same questions being asked again and again. And answered likewise by helpful people. However, the answer is so often already there if you search well enough. So how about a static page for the current FAQs? (kept updated) As in ‘please look there first before you ask a question here’?

None I could see in 1.5. I didn’t bring through the print.css from 1.2.2 to 1.5. I just deleted the reference to it from the upgraded index.php for my theme. Everything validates fine. I don’t see a problem in not having one. Who prints stuff anyway?

This is a valuable resource. What I’ve learned to do is search for stuff very thoroughly first, then post a clear question if I cannot find an answer. I’ll post my solution too, if I’ve worked things out. And then I’ll offer advice based on my experiences. What could be easier than that?

The suggestion from Podz for a testblog is a good one. That’s how I upgraded from 1.2.2 to 1.5. I set up a testblog on a PC (xampp and Linux – you can do this in Windows too) and then ran through the upgrade process several times until the problems were solved. I upgraded the live blog knowing that test upgrades worked faultlessly. You can also experiment with a clean install of 1.5 and an empty database.

Why not set set up a local version of WordPress on your PC and learn what’s going on with that? There are some instructions here https://www.tamba2.org.uk/wordpress/xampp/ (thanks to Podz). Xampp is for Windows or Linux. Start with a clean copy of 1.2.2 and an empty database. If that behaves OK, then drop that database and restore a copy of the live database from your host for local testing. That way, you leave the live database safely alone until you know what the problem is.

My thanks, Podz, for the excellent guides you’ve written. Very useful.

Both on here. See admin options/discussion to change. And look at this https://www.tamba2.org.uk/wordpress/ to test trackbacks/pingbacks.

Doh. The answer was in these forums all along.

in wp-settings.php

change ‘foreach ($current_plugins as $plugin)’

to ‘foreach ((array)$current_plugins as $plugin)’

Another one line edit does the trick.

Whether the plugins are deactivated or activated, I see this error message on a test 1.2.2 to 1.5 upgrade (xampp Linux). It *appears* to make no difference to the success of the upgrade either way. Anybody else got experience of this?

It’s not hijacked (as they usually are). This one used his real IP address. I have complained to the ISP and sent my findings. I know who he is, where he is, his company, and the business directory he’s trying to promote up the page rankings. So if anyone has seen this IP, say so here!

You do want to try and get his IP and preserve all the files he uploaded. In the UK, this activity would be a crime under the Computer Misuse Act. Good hunting!

All you need is xampp (on Windows or Linux – I’ve used it on both but prefer Linux). A new install of WP 1.5 takes way less than five minutes once xampp is running and an empty db is created. It also makes a lot of sense to test away from the live blog. I now have a test 1.5 that I can restore a live 1.2.2 database into and then upgrade (switching plug-ins off first). I’m keeping it roughly in sync with the live blog. Great for testing 1.5 on real data.

Running a test version of 1.5 on Linux; when I mark spam as spam rather than delete, it’s stored in the database but is not displayed. I’ve looked with phpmyadmin and I can see it there. Will there be any functions (other than using phpmyadmin) to clean it out? I see that davidchait’s plug-in is one option. On gmail, you can mark stuff as spam so gmail ‘learns’ and sticks it in a spam folder with 30 day deletion, any plans to do something like that? You might use the IP, e-mail, and urls for blacklisting.

Whatever you decide to do, back up the db first. Twice. And keep the copies safely on one side. Hopefully somebody out there reading this will give you an easy answer. All the issues I’ve had with WP1.5 have been one line edits. This may be another one (or maybe a setting).

Bkpatton: Make sure you’re backing up the database regularly while this is sorted. There is a test WP 1.5 install at https://www.opensourcecms.com – look for CMS-Blogs and select WordPress – which is worth playing with. It’s something to do with being logged in or not.

Your blog tells me this: “Logged in as . Logout ??” Even if I do, the comment fields don’t appear when I go back to the blog. So look at login and cookie issues (does exactly the same in Firefox and Internet Explorer).