Comments on: Working Around CodeIgniters Default Session Library

By: chris

chris — Tue, 15 Nov 2011 03:14:05 +0000

Robert – thanks I may end up using your code instead.

Erik – Yes I may have some refactoring to do. I don’t like storing session data in the database unless I need to. I like PHPs file-based sessions just fine.

By: Erik

Erik — Tue, 15 Nov 2011 02:12:40 +0000

sorry to have to make another comment but can’t edit

1) Your session is always started in your constructor. Why are you starting it (with error supression) in all your methods?
2) If you use CI’s ability to store session data in the database you no longer have the limitation of how much data a cookie can store.

By: Erik

Erik — Tue, 15 Nov 2011 02:09:15 +0000

The find and replace is a bit overkill — you can simply drop a file in your libraries folder and name it MY_Session.php. Now override whatever methods you want to (or all of the methods) and now you can use your new session library without changing a line of code in the rest of your applications (assuming you implement the same methods with the same parameters)

By: Robert

Robert — Sat, 12 Nov 2011 09:38:43 +0000

Here, try this instead, this is a drop-in replacement for CI 2.0

https://gist.github.com/1360305

I borrowed it from somewhere, but now i forget where. Anyways, this tosses out the whole cookie approach and sticks to the tried & true session handler in php.