Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the OpenGuides CPAN distribution.

Report information
The Basics
Id: 15051
Status: resolved
Priority: 0/
Queue: OpenGuides

People
Owner: Nobody in particular
Requestors: ivorw-cpan [...] xemaps.com
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Break down address into separate fields
Currently, OG has two fields which are configured at guide level: country and city. This is not flexible enough, and can't cope with circumstances like "The Tourist Engineer". While still retaining a metadata field called "address" containing "Foobar House, 2 Foobar Crescent" and suchlike, I propose the following configurable metadata fields: town city county state country Each of these is configured at the guide level to be one of the following: * A metadata field * Turned off * Forced to be a particular value e.g. London In the latter case, the edit page presents a checkbox against the forced value. This will enable us to have addresses in "Richmond, Surrey" in the London guide for example.
Starting to work on this one. Please let me know of any relevant points.
A patch is ready (attached)

Message body is not shown because it is too large.