Clear your cookies - sound familar? Clear your cookies - sound familar?
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

Clear your cookies - sound familar?

Started by electrode, November 17, 2006, 09:06:20 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

electrode

How many times has advice been offered to "clear your cookies" in order to solve problems?
What other system has these problems?

How about solving the cookie problems once and for all in the next major release?

Personally I think cookies should only be used during the current session and not for storing context between sessions.

Please add an option to set the cookies to expire, or reinitialize the cookies at every logon or session start.

If permanent context (ie., between sessions) is absolutely required, then store it in the database.  What really needs to be kept besides current theme setting and language?

Thanks for considering ... :)



Abbas Ali

Cookie is the problem only because of improper browser settings. We cannot eliminate cookies and use database for trivial information storage. Storing information in database and retrieving them means making additional database queries on each page which slows down cpg.
Chief Geek at Ranium Systems

Joachim Müller

Using PHP-sessions instead has severe drawbacks as well. The board would be cluttered with people complaining about session issues instead of cookie issues. Review the threads where supporters recommended to clear the cookies: in all those threads, users have done something they shouldn't have done in the first place (like using invalid cookie names or similar) - those are PEBKAC issues imo.
You're welcome to post actual code that fixes any issues related to cookies. Just proposing to get rid of cookies is similar to asking to release bug-free software.

electrode

#3
Hi Stramm. Not suggesting to get rid of cookies. Absolutely necesary to efficiently carry context between pages within a session.

For many situations, the same PC is used by different users accessing the same or different cpg sites, often with the same default cookie prefix, perhaps even at the same time. And the same user can use different PCs, perhaps even at the same time.

Once the user logs off, then the cookie context should be redundant, and at next log on cookies reinitialized.

For non-members no context should held between sessions.
Am I right that this suggestion only presents small complications because of non-members?
Even so, if a new browser session is started, then cookies could be reinstated. 

I might look at trying this once I know my way around the code a bit better.

For members, what other context would need to be stored between sessions besides current theme and language?