simultaneously use two calendar

[GoogleCodeExporter]

Be able to use 2 different calendars with 2 Gameconfig at the same time.

Currently there is a problem with cookies (they share the same cookie).

Original issue reported on code.google.com by athenebl...@gmail.com on 2 Dec 2013 at 11:09

[GoogleCodeExporter]

The attached files should fix the problem.
The cookie now is now postfixed by a crc32 of the raidplaners working directory.
This should be sufficient in most cases.
Furthermore you can add a column to the settings table (e.g. "raids_setting") 
with "Name" set to "CookieId" and "TextValue" set to the value that you want to 
add to the end of the cookie name.
So e.g. adding "FooBar" here will lead to the cookie name 
"ppx_raidplaner_FooBar".

Original comment by arne.cl...@gmail.com on 2 Dec 2013 at 2:44

• Changed state: Done
• Added labels: FixScheduledFor-1.0.3

Attachments:

• fix93.zip

[GoogleCodeExporter]

i'm trying it with the raid_settings table, i'll tell you if there is any bug 
this week.
thanks for the fix^^

Original comment by athenebl...@gmail.com on 2 Dec 2013 at 3:43

[GoogleCodeExporter]

Please tell me if the defaults were sufficient for you as I'm not sure if I'll 
keep the database fallback (as it causes an extra query on each request).

Original comment by arne.cl...@gmail.com on 2 Dec 2013 at 4:17

[GoogleCodeExporter]

Yes defaults are sufficient both calendars works now

simple question: how long the little padlock keeps the session active ? every 
4-5 hours I see the login screen again and if I refresh the page directly I 
arrive on the month calendar without typing my login/password.

Original comment by athenebl...@gmail.com on 5 Dec 2013 at 6:53

[GoogleCodeExporter]

Great, I removed the database fallback for the next patch.
As for the padlock - this should keep the login for 1 week but I guess it's 
broken ... again. *sigh*
I'll check on it.

Original comment by arne.cl...@gmail.com on 5 Dec 2013 at 8:08

[GoogleCodeExporter]

The cookie used for the sticky login (the padlock) did not have the "SiteId" 
used for the session.
Maybe this broke it in your case.
I tried it here locally by removing the session and it worked. Cookie 
expiration seems to be ok, too, so the attached fix v.2 should do the trick 
(hopefully)

Original comment by arne.cl...@gmail.com on 5 Dec 2013 at 8:23

Attachments:

• fix93-2.zip

[GoogleCodeExporter]

seems to work, no login screen today, thanks :)

Original comment by athenebl...@gmail.com on 6 Dec 2013 at 3:42

[GoogleCodeExporter]

One login screen this morning, maybe it's because I didn't clean my 
cache/cookies before applying fix93-2
But this fix kept the login for 1 day, always better than the 3-4 hours I had 
previously

Original comment by athenebl...@gmail.com on 7 Dec 2013 at 1:34

[GoogleCodeExporter]

Original comment by arne.cl...@gmail.com on 30 Dec 2013 at 6:35

• Changed state: Fixed

[GoogleCodeExporter]

I don't know where to put this but since I set debug script to true my cookie 
expiration seems to be fixed

Original comment by athenebl...@gmail.com on 1 Jan 2014 at 6:23

[GoogleCodeExporter]

After the update to 1.0.3?

Original comment by arne.cl...@gmail.com on 1 Jan 2014 at 8:43

[GoogleCodeExporter]

After the fix96_2.zip and having set debug script to true for the first time. I 
haven't updated to 1.2.3 yet.

Maybe it's something with the loading of all single script instead of one big 
script that make it work now

Original comment by athenebl...@gmail.com on 2 Jan 2014 at 8:16

[GoogleCodeExporter]

Every fix that contains Script changes requires this.
And yes, it disables loading the compiled script and loads single files again.

Version 1.0.3 contains the compiled form of this fix (and others) so it should 
not be required to enable script debugging anymore.

Original comment by arne.cl...@gmail.com on 2 Jan 2014 at 10:17