Ah, now that is interesting. If the cookies have different paths, then
that would indeed explain the problem. In the browser, a cookie is
uniquely identified by its name, domain, and path.
Mahara is *supposed* to set the session cookie's path to be only the
path portion of $CFG->wwwroot, so that a
Thanks Aaron.
I've just had it happen again. I checked my cookies and I end up with
two 'mahara' cookies.
1. path: /admin/site
Expires: at end of session
2. path: /
Expires: at end of session
I think it's not clearing the cookies correctly.
So, if I log in from the main page, then the ses
** No longer affects: mahara/16.04
** No longer affects: mahara/15.10
** No longer affects: mahara/15.04
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- plea
** Also affects: mahara/15.10
Importance: Undecided
Status: New
** Also affects: mahara/16.10
Importance: Undecided
Status: New
** Also affects: mahara/16.04
Importance: Undecided
Status: New
** Changed in: mahara/16.10
Milestone: None => 16.10.0
** Changed in:
4 matches
Mail list logo