|
| Summary: | [Chameleon-Documentation]Keymap path issue | ||
|---|---|---|---|
| Product: | Chameleon | Reporter: | Normand Savard <nsavard@mapgears.com> |
| Component: | Documentation | Assignee: | chameleon-dev <chameleon-dev@lists.maptools.org> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 1.99 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
an update on this. The KeyMap widget will now work with remote files, it downloads a copy first. So it should work exactly as every other widget does. I think that makes this bug invalid, although I guess you could test it first to ensure that it does work as expected. That would be a different bug, though, I think.
Thanks. I'll check that.
I added this note to the documentation. closing bug.
Bug 52 described a problem related to path to keymap image. It should be documented. --------------------------- Here is a snippet of the documentation to add: "I don't think that the keymap image can be treated in exactly the same way because mapserver doesn't allow for a remote image to be used for this so the actual order will be: * absolute, leave as is * relative, check file system relative to application htdocs directory (subtle difference here .... not necessarily relative to template because the template could be in a different location from the 'index.phtml' file). * relative, check file system relative to chameleon htdocs directory"