Bug 430385
Summary: | clean urls do not work due to inconsistency between drupal.conf and .htaccess file | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Roland Hermans <rolandh> |
Component: | drupal | Assignee: | Gwyn Ciesla <gwync> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 5.7-1.fc8 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-26 00:28:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Roland Hermans
2008-01-27 10:02:09 UTC
Will doing this and pushing it down break any existing sites? /usr/share/drupal/.htaccess isn't marked noreplace, and maybe it should be, but what would the ramifications by of having that option set that way on a site not using it, such as in a name-based virtual host, where drupal is the root, say http://foobar.org/, as opposed to http://foobar.org/drupal? If there's no effect, I'm willing to mark it noreplace, make the change, and make notes in the drupal.conf and the spec. I'd just prefer to make sure that any deviations from upstream have as few side effects as possible. As an alternative, I can at least mark it noreplace, so your personal change wouldn't be wiped out each upgrade. can you test the above and let me know? Enabling "RewriteBase /drupal" in the .htaccess file has an effect on name-based virtual hosts with clean urls enabled. After enabling clean urls the urls have /drupal added to the url, e.g. http://foobar.org/admin/settings becomes http://foobar.org/drupal/admin/settings, and a user will have to login twice. Conclusion: it's not wise to enable "RewriteBase /drupal" on name-based virtual hosts. The next thing I tried was moving the RewriteBase line to /etc/httpd/conf.d/drupal.conf file but without success as it seems to be overrided by the settings in .htaccess. It seems to me that on the one hand there is a Fedora policy not to put the web applications such as MediaWiki, phpMyAdmin and Drupal in the document root and on the other hand to make as little deviations from upstream as possible and somehow we'll have to find the right balance between these two. I see two possible solutions: 1. Don't change .htaccess and document in drupal-README.fedora how to enable clean URLs on a default installation. 2. Set RewriteBase to /drupal in .htaccess and document in drupal-README.fedora how to enable clean URLS for a name-based virtual host. Make a choice between these solutions based on the expected usage. In either case it would be nice to mark .htaccess as noreplace. Does this also mean it will have to move to /etc/drupal and symlinked since essentially it becomes a configuration file then? How about I upgrade to 5.7? http://drupal.org/node/215269 Looks like this, plus marking .htaccess as noreplace, would do it. Agreed? Sorry for not responding earlier but I lost this bug on my 'radar'. Your proposal looks OK to me (better to include 6.x in Fedora 9 ;-)). drupal-5.7-1.fc8 has been submitted as an update for Fedora 8 Build, bodhi requests for F-8 and F-7. Starting work on drupal 6.0 for F-9. Thanks! drupal-5.7-1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report. |