View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004336 | mantisbt | reports | public | 2004-08-17 00:41 | 2004-11-06 06:55 |
Reporter | djockheck | Assigned To | thraxisp | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Product Version | 0.19.0a2 | ||||
Summary | 0004336: in one of my two installations the graphs (jpgraph) are empty | ||||
Description | in one of my two installations the graphs (jpgraph) are empty after the update from 18.3 to 19.0a2. | ||||
Additional Information | How can I trace the problem? Both Versions are installed on Suse 9.0 Systems. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Did you check the notes on the JpGraph page in Mantis manual? |
|
Yes I've done so: <cut> Where does jpgraph (temporary) store it's images? Maybe it's a problem of permissions? Are there any logfiles that migth be userfull? |
|
hi, this helped for me: get the url of a image and open this url directly in your browser. Doing so, I got some error messages which helped me to solved the problem. |
|
I tried opening the ulr ( http://aslixp02.cad/mantis/summary_graph_bystatus.php ) directly but there's always the empty pictureframe with the red cross in the upper left :-? edited on: 08-18-04 00:27 |
|
Hi, no, this is the url of the complete summary page. But each picture has it´s own URL, take a look into the html source code in your browser. In my firefox browser, I can right click a picture and find the menu entry "Copy Image Location". If you open this location/URL directly in your browser, I got some helpfull error messages. |
|
I've updated Suse 9.0 via yast online update. Now I opened the picture-URL: The messages I reveive there is: |
|
I've changed Memory Limit from 8M to 16M in /etc/php.ini memory_limit = 16M ; Maximum amount of memory a script may consume (8MB) now it works fine :-) This bug can be closed :-))) |
|
I will leave this issue open till we add information about debugging such problems in the FAQ. This has been raised several times before with the same debugging steps. This issue is now marked as a child of a documentation issue. |
|
See also 0004411 |
|
TomR, Have you tried to open the URL http://proguide.speed.planet.nl/cts/summery_graph_bystatus.php directly? ciao |
|
I have added a new Troubleshooting section to the manual source to include these tips. |
|