From #107824: Convert {watchdog}.referer and {accesslog}.url from VARCHAR to TEXT, I didn't get the patch that I wanted committed, so now I need to file a separate issue. We're currently using the incorrect spelling of "referrer" through our database columns and core code. I think we should be should fix the spelling error in Drupal since it is easy and will not continue to propogate a sad, mis-spelled word.

From the Wikipedia article on "referrer":

Referer is a common misspelling of the word referrer. It is so common, in fact, that it made it into the official specification of HTTP – the communication protocol of the World Wide Web – and has therefore become a widely used industry spelling when discussing HTTP referrers[citation needed]. The misspelling usage is not universal, the correct spelling of "referrer" is used in some web specifications such as the Document Object Model.

This issue will also rename the {accesslog}.url column to {accesslog}.referrer to match consistancy and description. "url" to me implies the current url, when in fact, that column's description from the schema says, 'Referrer URI.'

Comments

dave reid’s picture

Status: Active » Needs review
StatusFileSize
new13.39 KB

Patch ready for review.

pancho’s picture

StatusFileSize
new12.53 KB

I was just creating an issue to rename {statistics}.url' to 'referrer', but this should be handled consistently.
So a +1 from me.
However, we never ever change existing update functions, but create additional ones to ensure the upgrade path! Fixed this in the enclosed patch.

dave reid’s picture

Thanks Pancho! Yeah, I should have backtracked on changing an update function. I wasn't too worried about it since it's a 7.x upgrade, which is not finalized yet. Revised from #3 that adds the php-doc grouping around the update functions. Plus, no offense, I like my patch name better. :)

pancho’s picture

It doesn't matter whether 7.x is finalized or not - we want to make sure people who use 7.x-dev are not left with broken tables. #3 is good.

Status: Needs review » Needs work

The last submitted patch failed testing.

dave reid’s picture

dave reid’s picture

Status: Needs work » Needs review

As I have learned recently, a 7.x -> 7.x update path are not supported since 7.x is always changing.

Status: Needs review » Needs work

The last submitted patch failed testing.

dave reid’s picture

Status: Needs work » Needs review
StatusFileSize
new14.83 KB

Re-rolled and merged the updates into current 7.x update functions.

Status: Needs review » Needs work

The last submitted patch failed testing.

dave reid’s picture

So I've tested #9 on a clean MySQL and PostgreSQL HEAD install and I cannot duplicate the 1 exception from the testing bot...

dave reid’s picture

Issue tags: +Quick fix
dave reid’s picture

Status: Needs work » Needs review
StatusFileSize
new15.25 KB

Re-rolled and ready for review!

Status: Needs review » Needs work

The last submitted patch failed testing.

dave reid’s picture

Status: Needs work » Needs review
StatusFileSize
new15.25 KB

Re-rolled because user table name was rolled back to users.

Status: Needs review » Needs work

The last submitted patch failed testing.

Tor Arne Thune’s picture

Version: 7.x-dev » 8.x-dev

Still a valid issue after the release of 7.0. Moving to 8.x.

valthebald’s picture

Status: Needs work » Needs review
StatusFileSize
new15.24 KB

Reroll for 8.x

Status: Needs review » Needs work

The last submitted patch, make-it-referrer-343626-18.patch, failed testing.

valthebald’s picture

Status: Needs work » Needs review
StatusFileSize
new15.24 KB

Wrong copy-paste, sorry

Status: Needs review » Needs work

The last submitted patch, make-it-referrer-343626-20.patch, failed testing.

valthebald’s picture

Status: Needs work » Needs review
StatusFileSize
new15.24 KB

What's wrong with me? :(

Status: Needs review » Needs work

The last submitted patch, make-it-referrer-343626-22.patch, failed testing.

valthebald’s picture

Status: Needs work » Active

Interesting. Upgrade path produces messages => watchdog schema changed => watchdog() throws exceptions. I wonder how to fix this in a sane way?

valthebald’s picture

Is it at all possible to introduce {watchdog} schema change without breaking upgrade tests?

valthebald’s picture

Status: Active » Needs review
Issue tags: -Quick fix +Grammar Nazi
StatusFileSize
new15.91 KB

I suggest using hook_requirements to rename referer field to referrer in dblog schema.
Actually, it goes in 2 steps:
1) hook_requirements adds new field referrer, to allow modules use watchdog() during installation, and not to break upgrade path
2) hook_update_N removes referer field, which becomes obsolete

valthebald’s picture

StatusFileSize
new15.91 KB

Fixed small typo in dblog_update_8002() comment

Status: Needs review » Needs work

The last submitted patch, make-it-referrer-343626-27.patch, failed testing.

valthebald’s picture

Status: Needs work » Needs review
StatusFileSize
new16.24 KB

hook_requirements() *MUST* return value, retrying...

Status: Needs review » Needs work

The last submitted patch, make-it-referrer-343626-29.patch, failed testing.

valthebald’s picture

Assigned: dave reid » valthebald
Status: Needs work » Needs review
StatusFileSize
new16.24 KB

Check dblog schema, not system.

Status: Needs review » Needs work

The last submitted patch, 31: make-it-referrer-343626-31.patch, failed testing.

valthebald’s picture

Assigned: valthebald » Unassigned
Issue summary: View changes

with 3d-party libraries using the same "erroneous" spelling (both guzzle and symfony use `referer`), does it at all make sense to fix field naming in Drupal?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

kaynen’s picture

I noticed this when doing some troubleshooting, but it appears that 'referer' and 'referrer' have almost become interchangeable. Should this issue be closed?

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.