Customizing SMF > SMF Coding Discussion

[WIP/BETA] EU cookie law

<< < (17/48) > >>

emanuele:

--- Quote from: nend on May 22, 2012, 10:19:00 AM ---For the rest though why not set up a custom function for SMF that handles all cookies and sessions then start rewriting SMF to use that function throughout the entire source. This will be the first step and maybe you can encourage mod authors to use this function to set the cookie instead of PHP's function.

--- End quote ---
In 2.1 is there...it was born for another purpose, but it's there and is used, in the future it will be up to modders to use it. ;)

bonzo:
A lot of post on the subject all of a sudden!

I also think that the SMF developers should help out here and if it was easy to change forums I would as their seemingly head in the sand attitude is anoying me. Although I have had a quick look around and can not see any posts about other forums doing anything either.

I run a basic form with no mods and do not care about guests - why track guests they do not mean anything until they have regestered?
I can not see the point in most mods as the forum is to discuss the subject and I think a lot of forums are having a load of surpless content. Who wants or pays attention to "The quote of the day" add  Twitter and Facebook links !!!
A lot of users on my forum have trouble even posting!

Anyway back to the problem I have the one PHPSESSID cookie when people first visit the site which is a problem and the SMF cookie when they have logged in which is not a problem if they want to be a member of the forum.
Will emanuele's code take care of the PHPSESSID cookie?

I would think there are quite a few installations of the forum around that are not overloaded with extra packages as people just want a basic easy to maintain forum. I had a couple of plugins when I was on verson 1. to try and stop spammers but they always turned out to be a problem when upgrading which I think is another reason to stay clear of them.

Bloc:
I think Arantor is spot on here - the only good solution IMO is to not track guests at all. Its only then you really abide the cookie law, and you also focus the software towards USERS instead of guests, which can be *anything* that request the page, human or not. AWstats or other server logging software will give you this traffic anyway. IMO, if you are on a shared host and isn't able to check server logs because of that, well, then its one of the things you just cannot access by being on that setup.


As for the "upshrink" cookie, why set it at all? IMHO upshrinks that remember state should be reserved to members only. It can still work, just not remember over the next page.

bonzo:
If you are on a shared hosting and can not access the stats you could always install bbclone - although every shared hosting I have been on has had cpanel.

I think you get a lot more as standard these days even on a shared hosting. I have set somebody up with a hosting package for about £20/year that has everything and is UK based. If you want something and its not on your hosting package you do not have any excuse not to move.

Off-topic
Is it just me or does everybody get redirected back to the section index when you have posted?

feline:
You forgot a lot of cookies they set by javascript .. all the collapse functions (smf_toggle) ...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version