#248 closed defect (fixed)
AddWMSfromList + AddWMSfromFilteredList don't use OWSPROXY when loading WMS
| Reported by: | verenadiewald | Owned by: | verenadiewald |
|---|---|---|---|
| Priority: | major | Milestone: | 2.5 release |
| Component: | administration | Version: | 2.5 rc3 |
| Keywords: | owsproxy | Cc: |
Description
Using modules AddWMSfromList or AddWMSfromFilteredList do not use the owsproxy url when loading the wms into the gui
Change History (3)
comment:1 by , 17 years ago
| Status: | new → assigned |
|---|
comment:2 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:3 by , 17 years ago
try to use module AddWMSfromFilteredList instead of (AddWMSfromList because it is the newer one and contains all functionality of you want to use from AddWMSfromList
Note:
See TracTickets
for help on using tickets.
changed files are: http://trac.osgeo.org/mapbender/browser/branches/2.5/http/classes/class_wms.php?format=raw&revision=2563 http://trac.osgeo.org/mapbender/browser/branches/2.5/http/javascripts/mod_addWMSfromfilteredList_ajax.php?format=raw&revision=2564 http://trac.osgeo.org/mapbender/browser/branches/2.5/http/javascripts/mod_addWMSfromList.php?format=raw&revision=2564 http://trac.osgeo.org/mapbender/browser/branches/2.5/http/php/mod_createJSObjFromDBByWMS.php?format=raw&revision=2565