rustindy

The index.php file at the root folder is only 95 bytes long, and should show as being 5 lines long in a text editor (or 1 really long line in Notepad because it sucks). If you’ve uploaded that file and verified that it remains 95 bytes long on the server, then somewhere in some file is a blank line that shouldn’t be there.

Usually it’s a plugin file that causes that problem. Try removing them one by one and see if it starts working. If it does, then the last plugin you removed has a blank line in it at the top or bottom that needs to be deleted before it’ll work properly.

Or you can go the easy route 🙂

Use the Firefox browser with the Web Developer extension installed. In the CSS menu then, you’ll see an option called “View Style Information” – click that, then hover the mouse (now a cross-hair cursor) over the bit of text that’s ticking you off to find out what classes it’s part of. Then head to your stylesheet and change what needs changing.

Remember that CSS is applied based on two main things: the order the browser gets the information (so if you’re styling H3 twice, the second one will override the first), and the specificity of the information (so since #content p is more specific than just p in your stylesheet, it is given precedence regardless of what order the browser receives the info).

Your questions aren’t dumb, but without a link to the site, it’s more difficult to help.

As for the last two questions regarding the | character – that should be changeable in the template files. Probably in index.php in the theme folder.

IE has some badly broken CSS rendering code. It’s the evillest browser on the planet, IMHO. Firefox (and other Gecko browsers), Safari, Konqueror, etc. all have their own problems rendering CSS too, but nowhere near as many problems as IE on Windows and Mac.

IE is a badly broken browser – flaky standards support and some truly evil rendering bugs make it a sort of hell for developers to code standards-compliant sites any more complex than 1 column with no margins.

Plus using it is sort of like bending over and…. well, let’s just say that because of it’s massive integration with the Windows system, it’s chock full of security holes. Using IE is a good way to catch just about every virus/trojan/backdoor there is.

Plus Firefox (and most other Gecko-based browsers like Mozilla and Konqueror) support things like built-in popup blocking, tabbed browsing – you know, stuff that’s hard to live without once you get used to it 🙂

add the line
margin: 0;
to the BODY section of your CSS and see if that clears it up 🙂

Because you’ve modified the WP 1.2 files, there are a couple of extra steps to take.

Follow these instructions http://www.tamba2.org.uk/wordpress/upgrade/upgrade_ca.html to the letter and it *should* work for you (thanks to Podz for putting them together).

I have to say I have noticed a pattern with problems around here – a *LOT* of people have decided to skip running the upgrade.php file. Skipping that step will cause errors like IE6 trying to download the pages, invalid argument errors, and headers already sent errors. Please DON’T forget to run /wp-admin.php from your browser after you’ve copied the 1.5 files to your host. It really is an important step.

I’ve been running WordPress with Apache 2, PHP5 and MySQL 4.1 since the alpha stage with no problems (aside from bugs in the alphas, natch).

Peering through some of those posts, a couple of things spring to mind.

If WP is consistently sticking a \ in front of " characters, check to see if “magic_quotes” is on or off in your PHP config. I believe it’s behaviour changed between PHP4 and PHP5, so try setting to the opposite value and see if that gets fixed. PHP5 also has a PHP4 compatibility mode, but my understanding is that it’s not great and can cause it’s own problems. If you’re running PHP5, then PHP4 compatibility should be turned off.

PHP4 and MySQL 4.1 don’t get along well without a little hacking on MySQL, so it’s not a recommended combination. People with login or certain installation problems might be experiencing a symptom of this configuration.

If you’re running Apache under Windows, it can run either in the system account or an account you specify. If you’ve installed Apache with it’s own Windows username (or if your host has), this might be a simple permissions problem that can be solved by elevating the Apache user’s permissions on the folder containing the htaccess file. Windows can also have difficulties with files that only have an extension for a name (like .htaccess), so that might be a problem if the latest updates and versions aren’t installed.

Good luck 🙂