#217: <label> tags refer to names, not IDs
------------------------+---------------------------------------------------
Reporter: ilmari | Owner: ilmari
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords: hackfestsummer2007-reviewed
------------------------+---------------------------------------------------
<label for="..."> refers to IDs, but (at least) the edit page form uses
the name of the form element.
--
Ticket URL: <http://dev.openguides.org/ticket/217>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#123: Bogus warnings about duplicate IDs in HTML templates
-----------------------------------------+----------------------------------
Reporter: dom | Owner: ilmari
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Resolution:
Keywords: hackfestsummer2007-reviewed |
-----------------------------------------+----------------------------------
Changes (by ilmari):
* summary: Duplicate IDs in HTML templates => Bogus warnings about
duplicate IDs in HTML templates
Comment:
This is [http://bugzilla.gnome.org/show_bug.cgi?id=305885 libxml2 bug
305885].
--
Ticket URL: <http://dev.openguides.org/ticket/123#comment:5>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#176: OSGB x/y coords should be converted to WGS84 lat/long at page save time.
------------------------+---------------------------------------------------
Reporter: Kake | Owner: kake
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
------------------------+---------------------------------------------------
Suppose a guide accepts geodata as OSGB x/y. When the page is saved, we
use Geography::NationalGrid::GB to convert these to lat/long, and store
those in the database as well. Unfortunately these are actually OSGB
lat/long, whereas most people/applications will expect WGS84 lat/long. We
hacked around this for Google Maps display by using Geo::!HelmertTransform
to transform into WGS84 before talking to the Google API, but it would be
better to do the transformation at page save time, so the lat/long is
correct in the database, on the page, and in the RDF output.
This is likely an issue for OSIE guides as well.
--
Ticket URL: <http://dev.openguides.org/ticket/176>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project