Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Sorry…I misremembered the install and was thinking the .htaccess is different for a /blog install. Now that I look again, it’s standard. Here’s mine from a working /blog install (with the sitemaps plugin also working):

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

    I followed the special instructions here: http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

    That requires copying and modifying a few files up a level – .htaccess and index.php. I notice on your site that you also have /blog in your permalinks (that’s were sitemaps gets it’s urls). With this install method, the /blog won’t exist at all in your permalinks.

    Hi Wesg,

    I also have a few WP installs at /blog/. I’m not sure what you mean by complicated mod_rewrites – WordPress handles an install at /blog out of the box (so to speak) and writes the mod_rewrite rules in the .htaccess file for you to get rid of the /blog. If you hand wrote the mod_rewrite rather than let wordpress do it for you, that may be affecting your permalink structure.

    What’s your General Options look like? WordPress should read http://www.yoursite.com/blog and Blog address should read http://www.yoursite.com. That sets the mod_rewrite (and your permalinks) to hide the /blog. From there, the sitemap plugin should work fine.

    You can also set a custom location for a sitemap under Options -> XML Sitemap. I have mine set to the top level of the server as it will default to /blog.

    Hope that helps.

    I’m not clear how you are handling redirects from the .net to the .com? Is this perhaps an overeager modrewrite problem?

    I have the same error in an install I manage where the blog url is herblog.com but the wordpress install is at herblog.com/blog. The standard WordPress .htaccess is overeager and doesn’t redirect the ?p=x&preview=true url correctly.

    I’ve seen reports of the same setup and problem as I have, but unfortunately I don’t have a solution yet.

Viewing 3 replies - 1 through 3 (of 3 total)