CI Lee - 06 October 2008 07:03 PM
I had figured that out and updated that.
It works now, however I wonder why sessions does not work on the server.
-Lee
Sessions would not be an issue server side as they are fully handled by EE, EE generates and stores its own session IDs in the database, so if you could login to the cp, and were staying logged in to the CP, then sessions were working.
It still seems that, like Derek said, if you had sessions only set, your accesses to the front-end would also have to have the session ID in the URL, same as the back-end to function. If you did not see the session ID in the front-end URL, like you would in the CP, then it would not know what session to tie your access to, and you would not be seen as a Superadmin on the front-end.