You need to log in before you can comment on or make changes to this bug.
Unable to open a context file from the interface I click on "Open context" button. I typed in a local context file or a remote (URL) context file. Then the text is erased when I click the "Ok" button JavaScript console: Error: uncaught exception: Permission denied to get property Window.OpenContextCB Apache: [Wed Feb 25 12:06:25 2004] [error] [client 127.0.0.1] gd-png error: setjmp returns error condition, referer: http://192.168.4.13/testsuite/studio/ Php: No error. Redhat 9.0 chameleon and studio updated from cvs 2004-02-25:08:57 mapserv and php_mapscript fresh compiled
Problem similar on xcalibur but a few more messages: JavaScript console: Error: syntax error Source File: http://www2.dmsolutions.ca/msapps/chameleon_cvs//widgets/UploadContext.phtml?sid=403cdccb7e683 Line: 31 Source Code: <br /> Error: OpenFile is not defined Source File: http://www2.dmsolutions.ca/msapps/chameleon_cvs//widgets/UploadContext.phtml?sid=403cdccb7e683 Line: 99 Error: CloseWindow is not defined Source File: http://www2.dmsolutions.ca/msapps/chameleon_cvs//widgets/UploadContext.phtml?sid=403cdccb7e683 Line: 104 Error: OpenWindow is not defined Php:Warning: php_hostconnect: connect failed in /home/msapps/chameleon_cvs/htdocs/widgets/Popup.php on line 207 Warning: fopen("http://www.lan.dmsolutions.ca/msapps/studio/skins/flat_grey/popup.css", "r") - Bad file descriptor in /home/msapps/chameleon_cvs/htdocs/widgets/Popup.php on line 207
The problem is clarified. I set up the Web server path to "localhost" instead of "192.168.4.13" ip address. Now the context is loaded. "cwc2.xml" snippet: <context-param> <param-name>web_server_path</param-name> <param-value>http://localhost/testsuite/chameleon_cvs/</param-value> <description>This is where chameleon.php script is located.</description> </context-param>
Comment number two is not clear. I meant that I initially set the Web server path to "localhost" instead of a static IP address. This is generating the error described in the bug. When I set a static IP address the problem disappear. Maybe we should add a not in the documentation about this.
