By Thomasr976 on

I successfully installed Drupal 5.1 on XAMPP for Windows Version 1.6.1. This version has PHP 5.2.1 instead of version 4 that earlier posts refer to. I have tried following everything on http://drupal.org/node/43545 but nothing works. I also tried making changes per http://drupal.org/node/137190 which dealt with a Drupal 5.1 issue.

Before making changes to the files referred to in the above urls I have closed Apache, made changes/saved them and restarted Apache so that the changes would take. When I go to administer/clean urls, I run the clean url test, but it fails. I get no errors, just the XAMPP page saying that I have successfully installed XAMPP.

Any help would be appreciated. Please be specific since I am a newbie and am ready to resort to toes and elbows so I can get on with it.

Tom

⋅ Categories: Drupal 5.x

Comments

mokargas’s picture

mokargas commented

Make sure mod_rewrite is on and installed (ensure theres no # in front of it in HTTPD.CONF)

also it might pay to set up a seperate local server, ie not on localhost/ but say drupal/

pobster’s picture

pobster commented

Make sure you have this in your httpd.conf file;

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#
AccessFileName .htaccess

It's required to let apache know that it can use a .htaccess file. Then you need to let apache know that it can override its settings using that .htaccess file, how you do this depends on how you've set everything up? Look for;


Options Indexes FollowSymLinks
AllowOverride All
...
...
.

It's the AllowOverride All which is important.

Forget about the comment above saying to set up on a separate local server, it's irrelevant (no offence... but it is!) Obviously yes you need to uncomment the mod_rewrite rule though.

Pobster

mokargas’s picture

mokargas commented

Yeah you're right it isn't strictly relevant, but when developing it pays to seperate out your sites so you have less to look at

Thomasr976’s picture

Thomasr976 commented

Thank you! I was able to get it to work following both of your instruction sin a separate local server.

kyleb’s picture

kyleb commented

Wow Pobster, thank you so much! I was almost about to give up on drupal heh... I read all the other articles, but none of them said anything about:

AccessFileName .htaccess

Again, thanks a bunch!

-Kyle

pobster’s picture

pobster commented

Absolutely not a problem, glad to help!

Pobster

--------------------------------------------
http://www.justgiving.com/paulmaddern
--------------------------------------------

tm’s picture

tm commented

Don't recall seeing the "AccessFileName" reference before; learned something new, thank you.

Sounds like a candidate for a comment to the "Setting up Clean URLs" Handbook page (http://drupal.org/node/54832). Maybe the "meat" of this comment thread as a comment there, or as child-page? Something like this should not be buried in the forums.

mokargas’s picture

mokargas commented

Definitely agree!

dman’s picture

dman commented

Because you referred directly to the doc page you expected to find it in, it was easy to review and update it a bit. Thanks, that's how the documentation project can move forwards!

Done!

.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/

.dan. is the New Zealand Drupal Developer working on Government Web Standards

tm’s picture

tm commented

thank you!

mokargas’s picture

mokargas commented

Thanks mate!

pobster’s picture

pobster commented

Merm... That handbook page isn't correct (well it both is and it isn't!) these two lines;

Options +FollowSymLinks +Includes
AllowOverride All

Are never 'out on their own' they're only valid with directory permissions and would look more like this; (example)

<Directory "/var/www/localhost/htdocs">
  Options Indexes FollowSymLinks
  AllowOverride All
  Order allow,deny
  Allow from all
  <Limit GET POST OPTIONS PROPFIND>
        Order allow,deny
        Allow from all
  </Limit>
  <LimitExcept GET POST OPTIONS PROPFIND>
        Order deny,allow
        Deny from all
  </LimitExcept>
</Directory>

It's not clear to a non-technical handbook reader where those two lines should be. I feel after reading that page they'd more than likely just add them to the end of httpd.conf when they should only be present as I've shown above. The directory permissions are not always in your httpd.conf file either, you could need to set them in vhosts.d/00_default_vhost.conf instead.

Pobster

--------------------------------------------
http://www.justgiving.com/paulmaddern
--------------------------------------------

dman’s picture

dman commented

True enough, those two should not just be there. I tried to add a paragraph explaining they should be uncommented where found, but I also wanted to avoid copying anything irrelevant or installation-specific there. Those LimitExcept things (?) for example are distracting.

There are dozens of valid, and different ways you can glue a conf file together, and leading by example on one hand will cause confusion on the other. Although I can guess what it means, none of the distros I've worked with had a 'vhosts.d'. On Debian and Apache2 this year I'm guessing that's like /etc/apache2/sites-enabled

If you can add a handbook-worded paragraph or to to clarify anything on that page, please comment there directly.

.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/

.dan. is the New Zealand Drupal Developer working on Government Web Standards