FW: [Chameleon] CwcImage_0 when upgrading to Chameleon 2.6
johnlace65 at hotmail.com
Mon Sep 1 22:15:02 EDT 2008
Thanks again for your reply, Justin. But it hasn't solved my problem.hovering or right clicking on the "cwcimage_0" text will only point to the sample_basic.phtml# file, and not to the expected button image, as it does for the scale bar and other images. Maybe the explanation (and solution) comes from the fact that in my actual configuration I have never seen buttons created to the /ms_tmp/buttons/ folder, and that was unimportant for ver 2.4 but now it's crucial for 2.6. Something related to the skins/ file config? The sample files are identical for 2.4/2.6, and the directories below chameleon are also just the same. What else could I check? writing rights, paths and main.phtml I have checked several times. Thanks for your replyJohn Lace
From: justin.ngan at utoronto.caTo: johnlace65 at hotmail.comSubject: RE: [Chameleon] CwcImage_0 when upgrading to Chameleon 2.6Date: Mon, 1 Sep 2008 15:00:21 -0400
Out of curiosity, if you right click on where the icon is expected, and click on properties (sometimes a hover is enough), does it show you where it is looking for the image? This has been a very useful way for us to trouble porting and setup problems!
After that, I would look in that location, after the map is loaded (don’t close the session of course) and see if the image is there.
If it is: then there is a rights issue between chameleon/mapserver/apache.
If it is not: are you developing in an environment that offers a ‘file search’ tool and see if you can locate where the ‘expected file’ is being placed?
Finally, if the search does not return any file of the name expected, then almost for sure, you know that you have a rights problem for ‘writing’.
Incidentally, after looking at your config file, I know that it looks just the way it SHOULD according to chameleon docs. HOWEVER, I think that in the more recent versions, the *_tmp locations are definitely an issue. I bet, your problem can be fixed by following the above suggestions and finding which temp directory Chameleon is dropping your images. GOOD LUCK!
I hope this helps a little.
From: john lace [mailto:johnlace65 at hotmail.com] Sent: Monday, September 01, 2008 10:45 AMTo: Justin NganSubject: RE: [Chameleon] CwcImage_0 when upgrading to Chameleon 2.6
Dear Justin:Thanks for your reply. But all 4 checkpoint you mention seem to be ok.1.- The chameleon dir is exactly 'chameleon', no capital letters.2.- There seems to be no directory or files names changed.3.- I've double checked the temp folder paths. No typos.4.- All temp folders are rights 777. By the way, php error log is clean.I'm attaching the Chameleon config, using the Admin. Please take a look at it. Thanks in advance. John Lace ----------------web_server_path /chameleon/htdocs/ows_schemas_location http://ogc.dmsolutions.cawms_parse_file wms_connectiontimeout 30validate_template truedefault_language en-CAinvalid_session_template /usr/local/apache2/htdocs/error.htmlmapscript_module php_mapscript.so image_type AUTObutton_cache_path /usr/local/apache2/htdocs/ms_tmp/buttons/button_cache_web_path /ms_tmp/buttons/tmp_web_path /ms_tmp/tmp_img_path /usr/local/apache2/htdocs/ms_tmp/execution_timeout 120maturity_level ALPHAcount_hits falsecache_mlt true
From: justin.ngan at utoronto.caTo: johnlace65 at hotmail.comSubject: RE: [Chameleon] CwcImage_0 when upgrading to Chameleon 2.6Date: Mon, 1 Sep 2008 07:56:21 -0400
I think you are right that it is 1 of 4 possible problems.
The first you have already guessed. Pretty well all Apache (I’m assuming) and Unix setups are case sensitive. So if you did not rename your new environment the same way, you will have this EXACT problem.
Second, I have not made the switch to 2.6 but there could be a directory structure change. So, you might want to confirm that is not the case.
Third, is there any chance that any part of the path to the images folder has been named incorrectly?
Fourth, are there sufficient rights for READ and WRITE to the images directory?
I think that’s it but I’m pretty sure that one will address your problem. It looks very much like a problem encountered during setup. Oh, and if you’ve not used it, the ADMIN (HTML) page for Chameleon to check all the ‘expected’ ‘environment’ paths will be very helpful. You can confirm what your paths are and then check where the HTML page is expecting to find the images in the same place!
I hope this helps
Get more from your digital life. Find out how.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Chameleon