Uncomment RewriteBase in .htaccess

Slightly better help text.

I've never had to use this option before, I would think this would make sites in subfolders much more complicated.

Robin

Whether or not RewriteBase is required seems to depend on configuration options outside the .htaccess file. I know of three hosting providers that require RewriteBase to be set explicitly for Clean URLs to work, regardless of where you install Drupal. But I also heard of other hosting providers that do not require it. I'm confused.

I would much rather see better documentation in the event that Clean URL support cannot be detected by the installer.

-1 on changing .htaccess.

Robin

+1 for better documentation

While the current documentation gives a thorough overview (if there is such a thing), my guess is that many users are overwhelmed by the number of pages on that topic.

However, before I say -1 to my original proposal, can anyone give an example Apache configuration where Drupal is installed in a subdirectory an Clean URLs work out of the box?

Better documentation is always welcome, but isn't there something automatic we can do to improve the clean-url-activation? Like detecting VirtualDocumentRoot vs DocumentRoot and/or detecting whether we're in a subdirectory or not. And based on these detections, make suggestions to the user or even alter .htaccess?

I know this works out of the box on my setup on CentOS 5. I can get you a copy of the httpd.conf if you wish.

Making suggestions to the user during installation: +1
Altering .htaccess during installation: -1 .htaccess must not be owned by the user who executes the webserver. Therefore, altering .htaccess during installation only serves test and development installations. I don't think it's a good Idea to add additional code for that case.

I can get you a copy of the httpd.conf if you wish.

Please do so.

I'm not aware of many support requests for this, so marking won't fix.