By John Bryan on
Specific example is MySQLDumper but have encountered this annoyance before when I need to run non-drupal software/pages on the same domain/site.
How do I get Drupal not to process a particular path and instead let the path reach the software installed there. For example how do I get http://www.mysite.com/mysqldumper/index.php to be processed by the file /mysqldumper/index.php and not result in a Drupal created "page not found" page. I definitely do not want to integrate this into Drupal by creating a MySQLDumper module when I only want to use this for a one-of migration task - a single sql dump.
Apologies if there is a pre-existing page/tip/guide on this but my searching has not happened to unearth it.
Comments
Drupal generally works
Drupal generally works because either you entered only a domain name (or domain name and query term such as ?q=my/path) - and index.php is the default Directory handler - or, when viewing specific pages, because the path you entered does not exist as a file on the server and therefore either the rewrite rule at the bottom of .htaccess steps in and diverts my/path to index.php?q=my/path.
However in your case the actual path will exist therefore Drupal will not go near it. The only possible issue is if anything in Drupal's .htaccess file interferes with msqldumper, but you can override anything in Drupal's .htaccess by a suitable .htaccess file in the mysqldumper folder.
gpk
----
www.alexoria.co.uk
gpk
----
www.alexoria.co.uk
Mysqldumper page not found
Since uploading my drupal database to my webserver was not possible caused by timelimits and max filesizes I was forced to look for other solutions. So I also ended up with mysqldumper. I found it in node/43024. It worked fine. Once logged out the path is indeed lost. But since this dumper worked really nice it would be great if we could override this in the msqldumper .htaccess. How can we do this?
Johan