changing from 5.x-1.x-dev (2007-Oct-31) to 5.x.3.x-dev:
- no countries select list at /admin/settings/location, only empty fieldset
- no "Add another location" fieldset at the node (it was enabled in 5.x-1.x-dev, setting invisible in 5.x-3.x-dev)
- when editing a node:
- only first location has city/country fields, other locations have only latitude,longitude fields
- entering city/country information is not saved
Comments
Comment #1
alexis commentedI'm using location 5.x-3.0-rc2 and also tried with location 5.x-3.x-dev in in a Drupal 5.10 installation and when I go to the 'countries' fieldse in /admin/settings/location I get this message:
Currently, your Drupal site is capable of supporting extra features (e.g., postal code proximity searches) for locations from this list of countries. You can narrow the list down to countries for which you want to support these extra features. It may be useful for performance to narrow down this list if most the locations in your system are from only a handful of the listed countries.
I was expecting to see checkboxes to tell Drupal which countries the site will support, if I remember correctly this is how older versions of location module worked. Do you plan on adding this?
Is they any other 'good way' of limiting the countries that my site will have available?
Comment #2
gnat commentedTo add more information to this bug. I have followed the same process (upgraded my 5.x-1.x version to 5.x-3.x-dev), and have found the same issue.
I looked inside the the file location.admin.inc, at the section of the administrative page form, and found that there's no options in that section of the form. Looking at the commit log for this file in CVS I found this message:
So this seems like the cruft leftovers as part of a transition away from selecting configured countries, to automating that process, and more likely that section of the administration form will end up being removed or reworded.
Comment #3
yesct commentedtagging.
Comment #4
yesct commentedPlease try the newest official release or dev release as there have been many changes made. If there is still a problem, please post an updated detailed summary and be sure to set the status back to active. Thanks.
Comment #5
ankur commentedThis might've been fixed in another ticket since D5. If not, please re-open and update the version.