I use the sessions only as a way to authenticate users, and don't associate data with the sessions. So I have no use in the second cookie that gets created.
Additionally, "data" cookies are created for each "directory level". For example, if I have a page located at /add/issue, I will get a "data" cookie for root "/" and "/add/issue". This is because, unlike the session cookie, the data cookie is not set to respect the "cookie_path".
I've pushed a first commit on my fork to address those 2 issues (I already use that live on my production instance), sending a pull request for you to examine it.
I use the sessions only as a way to authenticate users, and don't associate data with the sessions. So I have no use in the second cookie that gets created.
Additionally, "data" cookies are created for each "directory level". For example, if I have a page located at /add/issue, I will get a "data" cookie for root "/" and "/add/issue". This is because, unlike the session cookie, the data cookie is not set to respect the "cookie_path".
I've pushed a first commit on my fork to address those 2 issues (I already use that live on my production instance), sending a pull request for you to examine it.