Django

Code

Ticket #11401 (closed: fixed)

Opened 9 months ago

Last modified 9 months ago

OSM Admin broken after OpenLayers updated to version 2.8

Reported by: yourcelf Assigned to: nobody
Milestone: 1.1 Component: GIS
Version: 1.0 Keywords:
Cc: Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

OpenLayers? updated their stable version from version 2.7 to version 2.8. I don't know why, but this seems to have broken the Admin OSM implementation, even though the admin implementation still uses version 2.7. See this thread:

http://groups.google.com/group/geodjango/browse_thread/thread/139f0e7013a87c78

The attached patch seems to resolve the issue by using OpenLayers? version 2.8 in the admin implementation instead.

Attachments

update_osmadmin_to_OL2.8.diff (0.6 kB) - added by yourcelf on 06/29/09 10:55:58.

Change History

06/29/09 10:55:58 changed by yourcelf

  • attachment update_osmadmin_to_OL2.8.diff added.

06/29/09 12:57:23 changed by jbronn

  • status changed from new to closed.
  • needs_better_patch changed.
  • needs_tests changed.
  • milestone set to 1.1.
  • needs_docs changed.
  • resolution set to fixed.

(In r11125) Fixed #11401 -- Update geographic admin to use OpenLayers? 2.8 as OpenStreetMap? does not support previous versions. Thanks, yourcelf for ticket and patch.

06/29/09 12:58:07 changed by jbronn

(In [11126]) [1.0.X] Fixed #11401 -- Update geographic admin to use OpenLayers? 2.8 as OpenStreetMap? does not support previous versions. Thanks, yourcelf for ticket and patch.

Backport of 11125 from trunk.

06/29/09 13:31:53 changed by jbronn

In #geodjango, springmeyer identified the root cause: http://trac.openstreetmap.org/changeset/16131.

The OSM JavaScript file that is linked to in the geographic admin was changed to only support OpenLayers 2.8. Glad this was caught before the release.

Add/Change #11401 (OSM Admin broken after OpenLayers updated to version 2.8)




Change Properties
Action