TIP: Use Markdown or, <pre> for multi line code blocks / <code> for inline code.
KO3 Auth for non-logged in users
  • SurferSurfer
    Hi,

    I have a question. I am using the auth module and have the login and admin role. I also want the ability to add a deleted/banned/suspended status. At first I thought of just adding these additional roles to the user and at the same time remove the login role. Now I am thinking this will use an unnecessary amount of queries as every time a user object is returned I will need to check which role the user has and then decide what to display. Should non logged in roles be stored directly in the user object? Maybe it is more suited to add roles to users that are logged in?

    Any advice is appreciated!

    Thanks!
  • SurferSurfer
    On another auth topic. When I have the profiler activated I can see the queries done for each page. It is my understanding that after a login the auth module fetches the user object from the session and not from the DB. Yet on every page there is a "SELECT `users`.* FROM `users` WHERE `users`.`id` = 1 ORDER BY `users`.`id` ASC LIMIT 1" query. After this query the roles queries come. Is the user object really loaded from the session?
    Also, why can't also the roles be saved in the session to save additional queries?

    Thanks!
  • WebthinkWebthink
    I think the problem you'll come up against if you look into this is that ORM objects aren't cacheable (or serializable) because they point to a mysql resource identifier.
  • SurferSurfer
    Thanks for your reply! So what is the benefit by storing the user object in the session? Makes more sense to just store the user id then?
  • biakaveronbiakaveron
    Check $_reload_on_wakeup ORM property (if TRUE, model doesnt execute DB query when loading from session)
  • SurferSurfer
    Thanks I will check that out! Will the user object still have data if it doesn't execute?
Add a Comment