Open GoogleCodeExporter opened 8 years ago
Thank you for the bug report. I have just tested with MAMP on my computer and I
am not able to reproduce the
problem. So I think I am going to need more information to be able to help you.
It would be great if you could firebug or something similar to view the body of
the ajax response received when
clicking the "update" button. If that response contains PHP errors it would be
a great help if you could post the
error messages here.
Original comment by oett...@gmail.com
on 10 May 2009 at 3:09
I ran into this issue, as well. It turns out that php didn't have write
permissions on the output directory, so
webgrind would show the load message and then immediately fail. Giving everyone
r/w access to the output
directory fixed the problem.
Original comment by bob.crys...@gmail.com
on 1 Oct 2009 at 11:53
Thank you for the comment Bob.
We should add better error handling to the system. It is on our todo list.
Original comment by oett...@gmail.com
on 2 Oct 2009 at 7:12
don't forget to activate json.so module in PHP...
Original comment by das...@free.fr
on 6 Dec 2009 at 11:22
Have installed json.so
Cache files are present and .webgrind file is created in output directory
(Indicating that write perms are OK)
However I still get the blank screen when trying to load a logfile in both IE
and
FF3.5
Original comment by denye...@gmail.com
on 18 Dec 2009 at 5:44
@denyerec
As mentioned above webgrind needs better error handling. If nothing happens
when you click "update" this will
almost certainly be the result of a misconfiguration error. You should be able
to see the PHP error in either the
XMLHttpRequest response using firebug, or directly in the apache error log.
Could you please try to locate the error and post it here, then we will try to
help you.
Original comment by info%sim...@gtempaccount.com
on 21 Dec 2009 at 2:22
Original issue reported on code.google.com by
tanc.whi...@gmail.com
on 22 Apr 2009 at 12:26