Wordpress modrewrite affecting Autogallery SQL admin area
 

Anyone know how to stop Wordpress mod_rewrite from displaying it's 404 page when trying to access Autogallery SQL? I have installed Wordpress in my root web directory, and whenever I try to access my Autogallery SQL admin login page it just displays the 404 page.

bump for me...come on guys help me out here..this thing is driving me crazy...i've been trying to fix it for awhile now....just wrote JMBsoft a ticket..but would be much faster if someone here knows how to fix it.

100% sure your AGSQL admin page isn't 404?

yup....when i remove the mod_rewrite code for Wordpress in the .htaccess file I get the AGSQL login page fine. When I add the code back it gives me the 404 page again.

keep in mind i'm adding the Wordpress mod_rewrite code in the .htaccess file in my root public_html folder and not the .htaccess file in the "admin" folder of AGSQL.

put:
Rewriteengine off

in .htaccess in the admin area

what does your htaccess file look like?

Easy fix for this. Why don't you ask your host's support if they can take care of it for you?

i just sent them a message....JMBsoftware support was unable to fix this also and told me to contact my server support.

This is not a JMB issue NOR a wordpress issue, but a http request issue :P

Here is the solution:

A) if your server is setup w/ predefined error pages, make sure you upload the appropriate 401 and 403 error pages.

B) if not, define your 401 and 403 error pages in .htaccess.
ErrorDocument 401 /401.shtml
ErrorDocument 403 /403.shtml

These pages must be static and on YOUR server. Once you correctly enter your password, you'll be taken to your protected area.

What happens without these documents is that wordpress serves up it's 404 page because these files don't exist.

These error pages can be filled w/ random babble and should be at least 512bytes if you use IE.

wordpress' mod_rewrite redirects only non existing files to its index.php
so unless something fishy is happening there it should work flawless.

After authentication, yes, until then, HTTP Basic-Auth first sends a 401 to request a password, so if it tries to serve up the error file and it doesn't exist, Wordpress ends up handling the page request.