Upgrade and .htaccess file

If you can’t get WP to edit it from in the permalinks section, you can just edit it manually on the sever. But since you’re saying that you did that and it’s not working … where’s WP installed?

That is, mine’s in /public_html/ but some people have it in subfolders.

Your .htaccess file should be in that same folder, unless you’re doing the old ‘run WP out of a subfolder, but pretend it’s in root’ trick.

It’s in /public_html/ but not named ‘wordpress’… would that have screwed it up?

I added the stuff they said to, was I supposed to delete anything in there too?

Nah, you can have WP installed anywhere ??

As for deleting things from .htaccess, generally you don’t have to, but you MAY have a conflict. I’m assuming all this was working before, so you shouldn’t HAVE to change anything.

I just looked at another file similar and it just has

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /concord/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /concord/index.php [L]
</IfModule>

And of course the particular URL in the REQUEST.
The Perm is 644

So what is wrong with this?
I knew someothing was wrong when I could not update it via the control panel… what a pain in the butt!

I should have been able to go from .1 to .2 in a snap.. dammit.

Another one on the same server looks like this and is 644 and works.
(I don’t know why it says FRONTAGE, I don’t use that yuck!)

# -FrontPage-

IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*

<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName xxxxxx.org
AuthUserFile /home/xxx/public_html/_vti_pvt/service.pwd
AuthGroupFile /home/xxx/public_html/_vti_pvt/service.grp

try this:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /concord/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

I think you’re double-defining concord in there.

Another file on the SAME server has 644 and looks like this:

# -FrontPage-

IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*

<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName somedomain.org
AuthUserFile /home/username/public_html/_vti_pvt/service.pwd
AuthGroupFile /home/username/public_html/_vti_pvt/service.grp

But that looks like it’s only for FrontPage… with the vti stuff and all.. It doesn’t even have WP in there.

EUREKA!!!!!!!!!!!!!!

I got it to work.

I uploaded a BLANK file, set the permissions for 777, fixed my permalinks which TOOK without giving me that bizarre ‘please edit your file now’ and then I fixed the permissions back to tight again.

WHEW.

It filled in its own directions for WP.

?? ?? ??

Now it will be interesting to see if when 2.9.3 comes out I can update from within the controls.

I could just delete it again before I do?

I’d probably copy it to backup.htaccess and see if it’s fine.

That’s very odd, though. Normally you don’t have to worry about that once it’s set. Did you run any plugins that might have played with it?