View Issue Details

IDProjectCategoryView StatusLast Update
0004411mantisbtbugtrackerpublic2004-11-06 06:02
ReporterTomR Assigned Tothraxisp  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Versiongit trunk 
Summary0004411: Graphics not viewable anymore
Description

After installing 0.19.-CVS the graphics are shoewn as a red cross. Everithing works okay in 0.19.0a2.

Additional Information

This bug looks related to 0004410

Tested with jpgraph 1.14 and 1.16.

TagsNo tags attached.
Attached Files
error.JPG (27,946 bytes)   
error.JPG (27,946 bytes)   

Relationships

Activities

TomR

TomR

2004-08-27 04:26

reporter   ~0007219

Tested with core/file_api.php version 1.52 and 1.53.

TomR

TomR

2004-08-27 05:04

reporter   ~0007222

Last edited: 2004-08-27 05:05

Problem still exists, however it should be a problem not related to 0.19.0-CVS.

However the jpgraph/src/Examples/testsuit.php is displaying all of the graphics fine.

edited on: 08-27-04 05:05

djockheck

djockheck

2004-08-27 07:44

reporter   ~0007228

Have you tried the solution of 0004410?

thraxisp

thraxisp

2004-08-27 11:19

reporter   ~0007231

Last edited: 2004-08-27 11:20

Are you referring to embedded graphics (e.g., pencil graphic for update), the uploaded images, or to the summary graphs?

If the latter, you can try to debug them by looking at the source for the summary page and executing the image php functions directly. It usually turns out that there is something missing in jpgraph.

edited on: 08-27-04 11:20

TomR

TomR

2004-08-28 05:44

reporter   ~0007268

I am refferring to the summary grpahs. Both embedded and uploaded images looks fine.

When I executed the url for teh image http://proguide.speed.planet.nl/cts/summary_graph_bystatus.php directly I get an error.

However all of the exeample functions op jpgraph works fine, so I guess jpgraph has been setup correctly. Also when I go back to an earlier version of Mantis ( with the same database as used in 0.19.0-CVS ) it works correct.

thraxisp

thraxisp

2004-08-28 16:40

reporter   ~0007281

What error do you get?

I have noticed a problem with the cumulative_by_date graph if you have a lot of bugs. It exceeds the runtime allowed by php.

TomR

TomR

2004-08-29 08:28

reporter   ~0007282

I get the error as in the uploaded picture. And system does not have a lot of bugs ( < 100 ). It is with every graph from Mantis.

thraxisp

thraxisp

2004-08-30 23:12

reporter   ~0007322

Is the error you are referring to the "cannot download summary_graph_bystatus.php..."? This could be a web server misconfiguration.

Is the URL you listed accessible from the internet?

TomR

TomR

2004-09-02 04:02

reporter   ~0007395

Yesy it is. The page is accessible from the internet, it is a standard MAntis program, however, there is some 'activity' in the program ( creating and storing image in the cache directory? ) resulting in the error.

It is a strange problem, however I find that a lot of people having problems with Mantis <--> jpgraph.

How do you explain that the standard Examples are al working fine?

hugopedersen

hugopedersen

2004-09-02 14:01

reporter   ~0007404

Just a comment:
Since I upgraded to version 0.19.x I haven't been able to get any graphs either. My 'old' 0.18.3 setup shows the graphs very fine.

thraxisp

thraxisp

2004-09-02 15:35

reporter   ~0007410

Would it be possible to get access to the site to see the problem first hand? You can email me the uid and password privately.

The problems with jpgraph usually result from problems with the path settings or php setup problems. Accessing the graphic building php routine (e.g., summary_graph_bystatus.php) directly should display these error messages.

hugopedersen

hugopedersen

2004-09-02 23:54

reporter   ~0007416

My site is located on mantis.hp-data.net
You can sign up for at test account.

hugopedersen

hugopedersen

2004-09-03 00:34

reporter   ~0007418

Things are getting a bit strange now - I have an internal testsite with 0.19.0rc1 installed on a Windows 2000 box and that has no problems with displaying the graphs.
The other site is located on a linux box at my ISP

The only thing changed in config is the database connection.

TomR

TomR

2004-10-04 07:20

reporter   ~0007886

Is this problem still unsolved by others, it is with me. I have checked everthing ( also the manual ) and everything is set fine.

However I am not be able to see graphics, same problem exits with relationship graphics.

Can anyone please explain to me why then supplied examples from jpgraph are working fine while the graphs from Mantis does not show!

thraxisp

thraxisp

2004-10-04 09:39

reporter   ~0007889

The relationship graphics are quite independent of the graphs. For the relationships, you need to install GraphViz as well.

I may be able to help if I can get access to your site. Please contact me privately.

TomR

TomR

2004-10-04 10:18

reporter   ~0007893

thraxisp, how can I contact you privatly?

You can access my site ( development 0.19.1-CVS ) at

http://proguide.speed.planet.nl/ctscvs

Platform WindowsXP
Apache 2.0.50
PHP 4.3.7
jpgraph 1.15

TomR

TomR

2004-10-05 00:54

reporter   ~0007901

Last edited: 2004-10-05 08:35

Thanks to Glenn Henshaw my problem is solved. He took a look at my site and came to the following suggestion:


The graphics seem to being corrupted by some blank lines being added
to the beginning of the file. These typically originate in the config
files (config_inc.php, custom_strings_inc.php,
custom_constants_inc.php). Could you check to see that you don't have
any brank lines after the ?> (end of php marker) in those files.

The same lines show up in the regular pages as well, but the HTML
renderer ignores them.

In my case the problem was not in blank lines, but only in a few spaces behind the ?> ( end of php marker ) in a custom* file.

Everything is working as expected now, also the relationship graphs.

It seems usefull to add this suggestion to the FAQ on jpgraph.

Thanks again Glenn...

edited on: 10-05-04 08:35

thraxisp

thraxisp

2004-10-15 13:29

reporter   ~0008065

We eventually need a check for the custom* files in admin setup.