Well it isn't working 100% for me, let me put it that way. The PHPSESSID cookie is being set regardless. But I will agree that Emanuele has done a splendid job in addressing the issue and has made some changes to subs-eclwarning.php since releasing it yesterday to take account of SEF considerations.
Hey, that was me who tried Emanuele mod.Unfortunately neither of the solutions work. That by the-person-whose-name-I-can't-read-let-alone-pronounce didn't work at all. The second one, by Emanuele, isn't preventing the PHPSESSID (ie visitors) cookie from being set.
It did work, I set it up and it disabled cookies for guests until they agreed to use them, using the notice that is placed at the top.
So SMF didn't issue no cookies at all lol.
It says, either agree, login or register to accept the cookie.
Then it places an ecl_ cookie on your computer to verify that you have accepted lol.
I checked and there was no cookie issued to the guest only analytic's and shoutbox, not SMF.
I have un installed it now, as it looks a mess right now lol.
But I believe it does the job, with an extra page that you can click in the notice where all the information will be about the cookies.
Nothing on it as of yet lol.
Rather than disable features completely - such as your shoutbox - all you need do is add a call to ecl_authorized_cookies() - and if that returns TRUE, cookies have been accepted ;) I've had to do that in subs.php for the Google Analytics mod.
But as you can see on on this site, no main menu is shown until after the visitor accepts the cookies so, as best I can tell, that site is now almost in full compliance with UK law, the PSPSESSID cookie issue notwithstanding.