Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter gretchenmeyer

    (@gretchenmeyer)

    Doh – I just found an include file at the end of my server config file that sets the AllowOverride back to None for my root directory.

    Thread Starter gretchenmeyer

    (@gretchenmeyer)

    So, I still haven’t figured out a solution yet (but did fix the blank screen that arose from last night’s try). I did try something tonight after reading that the directory defined in the server config file applies to the directory specified and all subdirectories.

    I left my working site in the blog directory, but changed the server config file to:
    <Directory /var/www/apa>
    Options FollowSymLinks
    AllowOverride All
    </Directory>

    instead of
    <Directory /var/www/apa/blog>
    Options FollowSymLinks
    AllowOverride All
    </Directory>

    The site in the blog directory no longer works after making this change. If I add garbage in my htaccess file, the home page still works, which leads me to believe that the htaccess file is not being read. (When I know that it is being read and I add garbage, I can’t even pull up the home page.)

    Does this provide any clues? If there’s anyone with any ideas, I’d sure love to hear them! Thanks so much!

    Thread Starter gretchenmeyer

    (@gretchenmeyer)

    Thanks for the suggestions, Shane. I’d already updated the wp_options table. I tried adding the line you suggested (ErrorDocument 404 /index.php?error=404) and then got a blank screen on my home page. I moved everything back to the /blog directory and am still getting a blank screen. (www.austinpetsalive.org/blog)

    It’s late. Will try again tomorrow.

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