xrlq

It just turned an apostrophe into a slash and an apostrophe. Any way to turn this off?

If I put it at the very top, it screws things up. This doesn’t, but doesn’t seem to fix anything, either:
<?php
include_once(ABSPATH.WPINC.’/link-update-xml.php’);
/* Don’t remove this line. */
require(‘./wp-blog-header.php’);
?>

Same problem here.

I second Marky’s request.

Interesting idea. I tried commenting that sectino out instead, just to be on the safe side, but so far so good.

Yes. That wasn’t the problem, but I did figure it out. For one reason or another, the information that the Permalink page now tells me to put in the .htaccess file is not the same information that it originally told me to use when I chose the same permalink structure on version 1.0.2 (I use 1.2RC now). So I copied the suggested code and pasted it over the previously-suggested code in .htaccess, and it seems to be working now.
John262: You should probably do that, too. Hard-linking the files in the meta area will solve the specific problem I identified before, but leaves a separate problem unsolved: you’ll still get the pointer to https://www.yourdomain.com/feed/rss2/ in the headers, which aggregators like Bloglines rely on to find your RSS feeds. By changing back the original code and making the appropriate fixes to .htaccess, https://www.yourdomain.com/feed/rss2/ will work, as it should.

Yup, that fixed it. Thanks.

OK, I found a section that said:
#commentform textarea {
width: 100%;
}
Changing the width to 75% seemed to make it fit on my browser. Is it better to leave it that way, or to remove the width reference altogether? And if the latter, is the surrounding #commentform….{ … } still needed?

I’m not familiar with that file. I did chmod wp-content/link-update-cache.xml to 666, per the instructions.

What is “the css?” I didn’t find a width reference in the main index file or the comment template. Is it somewhere else?

1.2 – but I had the same problem with 1.0.2 before.

OK – I got the blog back. For some reason, I still got the 500 error when attempting to display, but once I logged in and posted a new message, the 500 error went away and the blog returned. Then I deleted the test entry and the 500 error came right back again. Go figure.

This time I moved everything to a separate directory, and tried installing from scratch. That got me this error message:
“You appear to already have WordPress installed. If you would like to reinstall please clear your old database files first.”
If I clear the database, I’ll lose approximately 1,500 entries. Are there any other alternatives?

Also, both times upgrade.php warned me it would take a while, but ran rather quickly before telling me everything was done.

I did, this time with the 5-8-04 build. Then I re-ran upgrade.php. No changes – still the same 500 error.