Ciao Luca,
I attached a function that should go eg. into common.php. Use then instead of
$this->mapURL = $mapImg->saveWebImage();
$this->scalebarURL = $scalebarImg->saveWebImage();
this
$this->mapURL = mapSaveWebImage($this->map, $mapImg);
$this->scalebarURL = mapSaveWebImage($this->ma
no, it's not a disadvantage. It's more that there's exactly a function that
does it completely, it just got a bug. I'm wondering that this problem is not
more often discussed on the Mapserver list, since saveWebImage() is for sure
one of the core functions of a Mapscript application.
I will put
Hi Armin, Thanks for the code it fixes all. That's great!!
At last I can use the ver 2 for production.
I did few test but as soon I applied this patch the problem
disappeared so why don't keep it in the pmapper code as default? there
is some disadvantage on this approach for image name?
Thanks for
Hi Luca,
here is a sample code as workaround for the strange Mapscript bug and
the tmp file names:
in map.php for function 'pmap_createMapImage()' replace
$this->mapURL = $mapImg->saveWebImage();
with
$tmpImgBaseName = session_id() . "_map_" . time() . "." .
$_SESSION["imgFormat"];
$tm
