Outstanding issues with .htaccess, settings.php or robots.txt on Drupal 6?
Hi, With each Drupal 6 release, we made it a best practice to include a note in the related SA that "the settings.php, robots.txt and .htaccess files have not changed and can be left as they are if upgrading from the current version of Drupal". As part of my usual Drupal 6 branch maintenance, I've worked down the RTBC queue for Drupal 6 to two issues: - http://drupal.org/node/28776 - Protect svn files in .htaccess (which also protects .test files on the Drupal 6 patch) - http://drupal.org/node/299582 - Update robots.txt to remove obsolete items and order existing ones in alphabetical order If we do change any of the three files, I think it is better to do them all at once and then try to stay away from touching them for another lengthy period to help people apply changes to these three files which are most likely patched on a considerable number of Drupal installs. Therefore I am asking if you have any issues with these existing two patches to sound your concerns before they are committed (avoid the next Drupal version to come with changes to these files). Also, if you have other issues against these files, which you think should be resolved sooner then later, it is the time to put them into the spotlight. Gábor
Gábor Hojtsy wrote:
Therefore I am asking if you have any issues with these existing two patches to sound your concerns before they are committed (avoid the next Drupal version to come with changes to these files). Also, if you have other issues against these files, which you think should be resolved sooner then later, it is the time to put them into the spotlight.
If user-friendliness is a desired goal, then maybe it's the opportunity to uncomment one of the suggestions in .htaccess, regarding the access to the site with/without the www prefix (preferably keeping the one WITH www). Having them both creates duplicates (any seo expert around here to explain the effect of that?), and by default it is not sharing session cookies (last time I checked at least), which leads to confusions ("hey! why am I thrown out of that site?!"). Probably many of the mentioned patches to this file, are in these lines. Savvy users will probably know how to change the values, if they really need to.
On what Drupal project issue URL is this suggestion tracked? Gábor On Mon, Nov 10, 2008 at 1:51 PM, זהר סטולר - לינווייט <z.stolar@gmail.com> wrote:
Gábor Hojtsy wrote:
Therefore I am asking if you have any issues with these existing two patches to sound your concerns before they are committed (avoid the next Drupal version to come with changes to these files). Also, if you have other issues against these files, which you think should be resolved sooner then later, it is the time to put them into the spotlight.
If user-friendliness is a desired goal, then maybe it's the opportunity to uncomment one of the suggestions in .htaccess, regarding the access to the site with/without the www prefix (preferably keeping the one WITH www). Having them both creates duplicates (any seo expert around here to explain the effect of that?), and by default it is not sharing session cookies (last time I checked at least), which leads to confusions ("hey! why am I thrown out of that site?!"). Probably many of the mentioned patches to this file, are in these lines. Savvy users will probably know how to change the values, if they really need to.
I was uncertain (still am) about the necessity of this modification, so I didn't create an issue yet. Here's where it is now: http://drupal.org/node/332439 I also came across this one: http://drupal.org/node/69262 Gábor Hojtsy wrote:
On what Drupal project issue URL is this suggestion tracked?
Gábor
On Mon, Nov 10, 2008 at 1:51 PM, זהר סטולר - לינווייט <z.stolar@gmail.com> wrote:
Gábor Hojtsy wrote:
Therefore I am asking if you have any issues with these existing two patches to sound your concerns before they are committed (avoid the next Drupal version to come with changes to these files). Also, if you have other issues against these files, which you think should be resolved sooner then later, it is the time to put them into the spotlight.
If user-friendliness is a desired goal, then maybe it's the opportunity to uncomment one of the suggestions in .htaccess, regarding the access to the site with/without the www prefix (preferably keeping the one WITH www). Having them both creates duplicates (any seo expert around here to explain the effect of that?), and by default it is not sharing session cookies (last time I checked at least), which leads to confusions ("hey! why am I thrown out of that site?!"). Probably many of the mentioned patches to this file, are in these lines. Savvy users will probably know how to change the values, if they really need to.
I've had an issue open for a long while now that I hoped would help people with multisite and www/non-www domains. http://drupal.org/node/158445 It's been open since pre Drupal 6 and has had a few re-rolls. I've not done promotion of it because I'm the type of person to let sleeping dogs lie but I think that it should probably be considered with these other issues. Hopefully this can be moved forward. Thanks Adam This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.
participants (4)
-
Adam Cooper -
Gábor Hojtsy -
Zohar Stolar - Linnovate -
זהר סטולר - לינווייט