You need to log in before you can comment on or make changes to this bug.
Darren's comment:(Issue found during cwc2 course) > 1. If the location provided in the URL for your context is invalid, you > get PHP errors displayed on the resulting page. This shouldn't happen - > some higher-level error should be given. > Chris's comment: I have been unable to reproduce this using the sample template in cwc2/htdocs/test.html with Chameleon 1.0.3. But I was able to produce an error using the course templates. Service Instance used (where the context path is wrong): http://localhost/cwc2/cwc2.php? template=http://localhost/msapps/cwc2_coarse/cwc2_cmaterial2/ tutorial_template_5_1.html &context=http://localhost/msapps/cwc2ogc_demo/ogc_context.xml The error received on the template: Warning: file(http://localhost/msapps/cwc2ogc_demo/ogc_context.xml): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in C:\ms4w\apps\cwc2\htdocs\cwc2.php on line 498 The error received in the ErrorReport: * (c:/ms4w/tmp/sess_3fc384f15dea5\con56.tmp.xml) * Unable to read c:/ms4w/tmp/sess_3fc384f15dea5\con56.tmp.xml * ERROR: Invalid context file. If the context file is invalid, is this the appropriate response by chameleon? This I find strange since the course template contains the following ErrorReport Widget. Should the above error be placed in the Error Popup? <CWC2 TYPE="ErrorReport" Visible="true" PopupWidth="500" PopupHeight="400" Toolbar="false" Status="false" Menubar="false" Image="images/icon_error.png" ImageWidth="18" ImageHeight="18" ImageTip="Display Error Report" Label="Error Report"/> However, if the user has added the error reporter widget than the errors will be displayed there. Is it possible to suppress the php error when it is clearly displayed using the ErrorReport widget? So, if the ErrorReport widget is NOT present the php errors will have to be displayed.... Any thoughts? I also realize from a previous bug that the ErrorReporter has a delayed reaction and often the error does not show up until the user interacts with the app. This will cause confusion, and is probably why the php error are helpful to have anyways. Either way the php error display may not be worded correctly for the simple user of chameleon. The display of php error is directly related to their php.ini error loging setings. This would be either controlled by administrator of the web server.
reassigning to Zak since he is working on some other issues related to Upload widgets ... to be done for 1.99
Changed Target Milestone to 1.99 RC
this is completely resolved with the new service instance and a wontfix for version 1.0.x