[eluser]a.somervell[/eluser]
We're porting a massive site to CI, it has to be done bit by bit... section by section.
We've rebuilt the forum (getting rid of PHPBB YAY!), login, user management, preferences etc. in CI. Y'know, all the important bits...
For MOST of the rest of the site they dont need to be authenticated, but if they do (like our photo section) I want to see if they're logged in already, kick them to the CI based login part.
So. We really need to be able to include, or check for sessions AND/OR start them if they come to another non CI part of the site...
Do you think its better to:
- Include a CI controller in some way?
- Build a custom class in our existing site to check the CI sessions table?
I assume the cookie they'll get will have their SessionID in it which we can use to check against the table, but if there isnt one already we'll ahve to create one such that CI recognises it?...
To just include the whole CI framework in every non CI page somehow seems the best solution? Wasnt there a way you could set variables then include a page to load a controller?
