Opened 15 years ago
Closed 9 years ago
#13504 closed enhancement (wontfix)
Create cookie name hash option
Reported by: | wpmuguru | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Networks and Sites | Keywords: | |
Focuses: | Cc: |
Description (last modified by )
I put this on future release but we should do it early in 3.1. Currently, by default,
an upgraded MU install has an empty string as a cookie name hash
a single WP site uses the siteurl option as the seed for a MD5 hash
a WP -> WP 3.0 network uses the main site's siteurl option + '/' as the seed for a MD5 hash
We should move these to a common more appropriately name option/site option and give the super admin(s) the ability to change it and/or generate a new one.
Change History (5)
#4
@
11 years ago
If anybody has familiarity with how (if) this has changed, please chime in. :)
Nothing has changed since that code was added (3.0),
#5
@
9 years ago
- Focuses multisite removed
- Keywords dev-feedback removed
- Milestone Future Release deleted
- Resolution set to wontfix
- Status changed from new to closed
No other requests than the OP's in 5 years, and no activity in last 2 years. Closing for inactivity as wontfix. If interest re-emerges, feel free to reopen
I'm going to dig into our cookie hashing for multisite a bit and see what changes the last few years have brought us. It's possible that this has been addressed.
If anybody has familiarity with how (if) this has changed, please chime in. :)