htaccess file - Permalink "error" - is it real? (2 posts)

  1. gbclayton
    Posted 7 years ago #

    Friends, I'm a WP and UNIX newbie - and I've read all the permalink docs and 70-80 forum posts - and I am really confused by this error message:

    If your .htaccess file were writable, we could do this automatically, but it isn’t so these are the mod_rewrite rules you should have in your .htaccess file. Click in the field and press CTRL + a to select all.

    Is this an erroneous error message - or is there something I'm missing?

    My pages and posts all seem to have permalinks (check out http://www.garybclayton.com and /leadership/blog) that work from any browser on all machines to which I have access. I have links from posts to pages and they work just fine.

    I'm running 2.7 installed in my html directory with leadership/ as my home-page home and the nominal .htaccess file installed in the html directory. It seems to work, yet WP tells me I should change the .htaccess file to:

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

    So, I've learned to change permissions, access the .htaccess file and change the contents as directed. End result: no access to anything but my home-page. I walked through all this with godaddy and they tell me I did all the mechanics correctly.

    What am I missing? Do I really have a permalink error - or is there a WP>Settings>Permalink error?

    Is there another way I can test my permalinks to identify whether I have a real error?

    [my goal is to spend less time on technical setup and more time building my site, I hope someone can help clear this issue up]

  2. gbclayton
    Posted 7 years ago #

    Here's an addition:
    Today, I was successful in adding a valid sitemap.xml.gz file and Google and MSN indexed my pages successfully. The message that is still on my Settings>permalinks page is looking more and more like a WP error.

Topic Closed

This topic has been closed to new replies.

About this Topic