Closed GoogleCodeExporter closed 9 years ago
I need some more information about this
- On what date did your try this? As this bug appeared on Dec 16 I assume this
date.
- Does this happen for raids on every day in December or just certain dates?
- 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 11:36
Original comment by arne.cl...@gmail.com
on 16 Dec 2013 at 12:55
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:40
Thanks for the reply, to answer your questions:
Raids created on any day within december cause this to happen. If you view the
month of November you can see the first couple raids displayed for December,
but they don't show up while viewing december.
I'm in the PST timezone as is my server.
Exact PHP version is: PHP Version 5.3.13.
The raids are indeed created and showing up in the raids_Raid table, and the
raid for tomorrow (Dec 17th) is listed there and as open, it will just not
display the raids in the month of december.
If it helps, when you click on Raid instead of trying to view it under calendar
view, the raid appears there.
Original comment by pbrig...@gmail.com
on 16 Dec 2013 at 8:25
I cannot reproduce this on my systems here. Could you provide a link+login so I
can debug the script on your server? You can send the login/password to
arne.claus@gmail.com if you do not want to post it here.
Please don't forget to set SCRIPT_DEBUG to true in the index.php so I have a
chance to actually see something ;)
In addition to that:
This sounds a bit like Issue #84 or Issue #96. Could you please download the
file attached to Issue #96 and see if that fixes your problem? It addresses
Issue #84 in a more robust way.
Original comment by arne.cl...@gmail.com
on 16 Dec 2013 at 8:51
I emailed you the info, I wrongly stated that it was issue #96 in the topic I
believe when I meant to say it was Issue #95.
The Issue #96 fix unfortunately did not work for me.
Original comment by pbrig...@gmail.com
on 17 Dec 2013 at 9:40
I tried to reproduce it on your server, but raids are showing in december and
creating a raid did work, too...?
What browser were you using?
Original comment by arne.cl...@gmail.com
on 17 Dec 2013 at 11:39
I just tested again and neither of these worked.
I'm using Chrome Version 31.0.1650.63 on two machines, one windows one linux
and it will not display raids in calendar view.
It also behaves the same way in IE 10.
Original comment by pbrig...@gmail.com
on 17 Dec 2013 at 11:49
Oh, all other raiders and users report them not showing up as well, under a
number of different browsers.
Just confirming that you're at the right place: http://www.luxiv.net/raid/
Original comment by pbrig...@gmail.com
on 17 Dec 2013 at 11:50
Hmm. Strange.
Looks like this on my system:
http://www.packedpixel.de/raidplaner/debug/raids.png
Another thing I noticed is that not all locations show up on the locations
chooser, which is weird, too, but might be unrelated.
Original comment by arne.cl...@gmail.com
on 17 Dec 2013 at 12:20
Got it. It's a timezone related problem.
The first raid returned from the database is Nov.24, which is never displayed
and thus breaking the current "raids on this day" lookup for all following days.
Shouldn't take too long to fix, but I won't be able to get to it until this
evening.
Original comment by arne.cl...@gmail.com
on 17 Dec 2013 at 12:28
Well that's extremely weird. All any of us see is:
http://www.luxiv.net/planner.png
I notice your screenshot has you clicked on "Raid" and not "Calendar"? Could
this make a difference?
If I go backwards one month to November this is what we see:
http://www.luxiv.net/planner.png
Which shows some of the raids in early December.
Creating a raid in January displays fine, so it is ONLY December that is having
the issue.
Original comment by pbrig...@gmail.com
on 17 Dec 2013 at 12:32
Okay awesome, is there a temporary stopgap I can use in the mean time? If I
were to manually delete a raid in the database would it fix it for now?
Original comment by pbrig...@gmail.com
on 17 Dec 2013 at 12:33
Okay, I deleted the Nov 24th raid so that we can still use the planner in the
mean time. Let me know if you need anything or me to re-add it in case it's a
real script issue somewhere that'd need fixing.
Original comment by pbrig...@gmail.com
on 17 Dec 2013 at 12:59
Ok - we've got a bit of a problem here.
The fix for this is already present in 1.0.2 but it's been deactivated.
Activating it will change all raid times by a certain offset and I have not
written a script to automatically fix it, yet.
It WILL be part of version 1.1.0 though.
So - if you want to fix it. Go to "lib/private/connector.class.php" line 23 and
24. Put line 23 in comments and remove the comments from line 24. It will look
like this:
parent::__construct("mysql:dbname=".$aDatabase.";host=".$aHost, $aUser, $aPass,
//array(PDO::MYSQL_ATTR_INIT_COMMAND => "SET NAMES 'utf8'"));
array(PDO::MYSQL_ATTR_INIT_COMMAND => "SET NAMES 'utf8', time_zone = '+00:00'"));
As I said - this will change the times of all raids that are existing at the
moment.
To fix those, try the following query in phpMyAdmin (assuming your raids are
stored in "raids_Raid"
UPDATE raids_Raid SET Start=FROM_UNIXTIME(UNIX_TIMESTAMP(Start)+14400),
End=FROM_UNIXTIME(UNIX_TIMESTAMP(End)+14400)
The "+14400" is the time offset to add to each raid. In this case you will add
4 hours to each raid (60*60*4).
Original comment by arne.cl...@gmail.com
on 17 Dec 2013 at 5:48
The attached file contains a symptomatic fix. This means the bug will disappear
but the reason for it will not be fixed (see my previous posting).
It is meant for those who don't want to tinker around with the database.
You will need to set SCRIPT_DEBUG to true in the index.php for this fix to work.
Original comment by arne.cl...@gmail.com
on 17 Dec 2013 at 6:07
Attachments:
Original comment by arne.cl...@gmail.com
on 30 Dec 2013 at 6:35
Original issue reported on code.google.com by
pbrig...@gmail.com
on 16 Dec 2013 at 1:19