By jaku ayala on

Hi,

I have a Drupal installation on my computer, and a separate folder called "welcome" with a file "index.php" inside it. When I type "www.domainname.com/welcome" or "www.domainname.com/welcome/index.php", the site shows "page not found".

So it seems Drupal looks for a Drupal-generated page named welcome or welcome/index.php.

Is there a way to make drupal at directories outside the system?

Thanks

⋅ Categories: Drupal 5.x

Comments

jaku ayala’s picture

jaku ayala commented

The last phrase should read "look at directories outside the system"?

Thanks

cog.rusty’s picture

cog.rusty commented

In which directory is drupal installed and where is the welcome directory?

For example is it like this?

/home/user/public_html/drupal/index.php
/home/user/public_html/welcome/index.php

or like this?

/home/user/public_html/index.php (Drupal here)
/home/user/welcome/index.php

or something else?

In the second case, 'welcome' will never work because anything above public_html is out of the web.

jaku ayala’s picture

jaku ayala commented

Actually it's:

home/user/public_html/domainname/index.php
home/user/public_html/domainname/welcome/index.php

So the folder domainname contains all the drupal folders and files. The welcome folder is inside the drupal folder, sitting beside the files, includes, misc, modules folders.

It looks like this:

domainname
-- files
-- includes
-- misc
-- modules
-- other drupal folders and files
-- welcome (the folder I added)

I'm trying to do this because sometimes I need to quickly build a page that won't last long (i.e. sales letter-type for a limited offer) and would rather not integrate the page with the drupal system.

Thanks again!

cog.rusty’s picture

cog.rusty commented

I see... Normally Drupal does that for any path which is not a real readable directory or file. Try for example:

http://www.domainname.com/blahblah
http://www.domainname.com/yadayada

This is normal, and is caused by the last block of lines in Drupal's .htaccess which make Clean URLs to work. The problem will disappear if you rename Drupal's .htaccess, but then Clean URLs won't work.

But this is supposed to leave existing files alone, except if it can't read them and can't verify that they are there. Is that subdirectory protected in any special way, or are its reading permissions too strict? Permissions 755 for directories and 644 for files should be OK.

----------

You can also try something else: In the last block of rewrites in Drupal's .htaccess, comment out these two lines by putting a # in front

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

and replace them with

RewriteCond %{REQUEST_FILENAME} !-U

This is slightly slower, but it should detect and leave alone any files and directories without exception.