Canon attend certain raids in the next year

[GoogleCodeExporter]

Hello

A bug has been detected on the version 1.0.2 from the month of January on the 
first 15 days of the month, when you create a raid, we cannot register it, but 
from 16 this working properly.

I test on the months of February and March even problem

The problem is reproduced on 2 different installations on 2 different servers.

Original issue reported on code.google.com by dizier.d...@gmail.com on 16 Dec 2013 at 12:47

[GoogleCodeExporter]

Probably related to Issue #95.

(Almost) same questions here:
- On what date did your try this? As this bug appeared on Dec 16 I assume this 
date.
- In which timezone are you living / does your server run?
- What is your *exact* PHP version?

Original comment by arne.cl...@gmail.com on 16 Dec 2013 at 12:55

[GoogleCodeExporter]

Original comment by arne.cl...@gmail.com on 16 Dec 2013 at 12:55

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

[GoogleCodeExporter]

Another question: Does the raid show up correctly in the database?
Go to the raids table (e.g. "raids_Raid"), order by Id (descending) and check 
the date of the first raid (which should be the one you created last).

Original comment by arne.cl...@gmail.com on 16 Dec 2013 at 1:39

[GoogleCodeExporter]

same here, I can't attend for a raid on the 15th but I can on the 16th and both 
are correct in the database:

Original comment by athenebl...@gmail.com on 16 Dec 2013 at 4:22

Attachments:

• bug.PNG

[GoogleCodeExporter]

This problem for months is not the month of December, but only from the month 
of January is the other next month.

I'm on the GMT + 1 time zone

On one of my servers, I'm in PHP Version 5.3.2 on the second server, I'm in PHP 
version 5.3.25

Yes the dates are correct

Original comment by dizier.d...@gmail.com on 16 Dec 2013 at 6:05

[GoogleCodeExporter]

As the database values are correct it breaks down to being a script issue with 
the calendar display.
I'll have a look at it asap.

Original comment by arne.cl...@gmail.com on 16 Dec 2013 at 6:31

• Changed state: Accepted
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

The bug will affect days in the next year that are <= current day.
The attached file contains a fix for that.

Original comment by arne.cl...@gmail.com on 16 Dec 2013 at 8:40

• Changed state: Done

Attachments:

• fix96.zip

[GoogleCodeExporter]

And of course - as this is a script bugfix - SCRIPT_DEBUG has to be set to true 
for this fix to work.

Original comment by arne.cl...@gmail.com on 16 Dec 2013 at 8:51

[GoogleCodeExporter]

This is good :)

Original comment by dizier.d...@gmail.com on 16 Dec 2013 at 9:17

[GoogleCodeExporter]

This fix introduces a new bug on my calendar, I can't attend on the raids that 
are on the current day, I can only do it through the Raid Tab.

Original comment by athenebl...@gmail.com on 29 Dec 2013 at 3:58

[GoogleCodeExporter]

In which time zone are you living?
Does this affect all raids or just raids that are due to start in the next x 
hours (with x equal to your time zone offset to utc)?

Original comment by arne.cl...@gmail.com on 29 Dec 2013 at 4:21

• Changed title: Canon attend certain raids in the next year
• Changed state: Accepted

[GoogleCodeExporter]

I'm living in time zone UTC+01, it only affect raids in the next hours I'll try 
tomorow if I can found how many hours before the problem starts to occur

Original comment by athenebl...@gmail.com on 29 Dec 2013 at 8:08

[GoogleCodeExporter]

I have replaced the two files with those in Fix96 and changed 
define("SCRIPT_DEBUG", true);  in index.php.

Still unable to sign up for the dates in question.

Original comment by try...@gmail.com on 29 Dec 2013 at 9:30

[GoogleCodeExporter]

The attached file fixes the problem where you cannot attend raids on the 
current day.
As this is a script change don't forget to set SCRIPT_DEBUG to true - if you 
did not already do this.

At least on my system (with all 1.0.3 fixes applied) I have no problems 
attending raids in January, so the problem is either system specific or a 
missing hotfix. Have you applied the script fix (not the database fix) from 
Issue #95, too?

Original comment by arne.cl...@gmail.com on 30 Dec 2013 at 9:07

Attachments:

• fix96_2.zip

[GoogleCodeExporter]

This fix works for me, thanks^^

Original comment by athenebl...@gmail.com on 30 Dec 2013 at 12:35

[GoogleCodeExporter]

If any problems persist after upgrading to version 1.0.3, please create a new 
bug.
This way we're all starting off the same base again.

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

• Changed state: Fixed