Opened 15 years ago
Closed 9 years ago
#9873 closed defect (bug) (wontfix)
enforce a consistent home and siteurl www. pref
Reported by: | Denis-de-Bernardy | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.8 |
Component: | Users | Keywords: | has-patch |
Focuses: | Cc: |
Description
Seen on a few sites. home and siteurl with inconsistent www prefs prevents the admin user's cookie from getting picked up properly, upon logging in.
code I currently use to prevent the issue is this:
add_action('login_head', 'fix_www_pref'); function fix_www_pref() { $home_url = get_option('home'); $site_url = get_option('siteurl'); $home_www = strpos($home_url, '://www.') !== false; $site_www = strpos($site_url, '://www.') !== false; if ( $home_www != $site_www ) { if ( $home_www ) $site_url = str_replace('://', '://www.', $site_url); else $site_url = str_replace('://www.', '://', $site_url); update_option('site_url', $site_url); } } # fix_www_pref()
there's probably a better way and a better location for this.
Attachments (2)
Change History (17)
#9
@
12 years ago
- Cc andrew@… added
- Keywords has-patch added
- Type changed from enhancement to defect (bug)
- Version changed from 2.8 to 3.4
#10
@
12 years ago
- Version changed from 3.4 to 2.8
Version number indicates when the bug was initially introduced/reported.
#12
@
11 years ago
- Cc johnpbloch@… added
It seems to me that overriding a user's chosen preference in the options table is the wrong way to fix this bug. Since the problem is that it causes inconsistencies in cookie behavior, it makes more sense to me to fix this issue by forcing a value for COOKIE_DOMAIN
if a www.
inconsistency is detected.
This ticket was mentioned in IRC in #wordpress-dev by ipstenu. View the logs.
11 years ago
#15
@
9 years ago
- Keywords dev-feedback removed
- Milestone Future Release deleted
- Resolution set to wontfix
- Status changed from new to closed
I struggle to believe that this is such a common occurrence that core needs to handle this.
In addition, both of the proposed solutions will break sites which use a different domain name for home
and siteurl
(eg. www.example.com
and admin.example.com
).
Feel free to re-open if there's a common situation which leads to this that I'm not accounting for, and/or if someone wants to write a comprehensive patch with unit tests.
punting pending patch