1. There is a new configuration requirement for some users. I've found that SOME ISPs run site configurations that don't play nice with e-Privacy. I found this by buying a hosting account with one of these ISPs so I could experience it first-hand. The particular host I knew would replicate this issue only sells hosting accounts on an annual basis - so it was an expensive bug to find.
The configuration to resolve that issue is to set the cookie domain in Joomla global configuration. Simply, make it the same as your canonical domain name. By default, Joomla precedes this with a "." (dot/period), so if you want it to behave like vanilla joomla, you can do that too. If you're running your site on
www.example.com
- your cookie domain can be any of: .
www.example.com
(the joomla default),
www.example.com
(restrictive), or .example.com (super non-restrictive) - If you don't have a particular reason to pick 2 or 3, go with 1.
2. Good call, I'll make that adjustment - but I'll go with a varchar length of 45 which accommodates ipv4, ipv6 and ipv6mapped addresses. It's for logging purposes only, so it should be fine, and backwards compatible.
3. I'll address that with the SQL changes
4. I wrote it in 2012, and IPv6 wasn't such a big deal then. I've written much better IPv6 tools, and I'll apply them.
Thanks for the constructive criticism and praise, I appreciate it! I'll start working on the 3.8.0 version soon, which will incorporate at least one new feature, similar (opposite) to the accepted cookies access level, users who have not accepted cookies will be part of a different access level - allowing you to display alternate modules for users who have not accepted cookies (taunting them to accept)
