Closed (fixed)
Project:
Address Field
Version:
7.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
3 Nov 2010 at 04:13 UTC
Updated:
16 Sep 2011 at 08:21 UTC
It seems that some of the "What this module isn't" is alluding to the other modules, but it would be really nice to know the pros and cons as you see them. I'm with you that the Location module is bloated, but the Addresses modules doesn't seem that bad.
http://drupal.org/project/location
http://drupal.org/project/addresses
Just wondering if you could offer an help in making the choice. You modules isn't very well adopted yet, but it seems like you've got a good roadmap, and the support of drupal commerce. Speaking of which, is that support solid, or tentative?
Thanks very much for any help you can offer!
Comments
Comment #1
rszrama commentedI'll have to let Damien chime in with more info, but the basic differences w/ Addresses are a dependence on a different underlying standard (xNAL vs. hCard), a template approach to address formats, country-specific address entry forms via includes, and a Drupal 7 release target (important for our integration w/ Drupal Commerce). This module was started specifically to support the initial address needs of Drupal Commerce, so that relationship is solid.
That's not to say Drupal Commerce won't be better served by another module in the future... we'll have to do a more in-depth examination once everyone's up on Drupal 7.
Comment #2
patcon commentedOh hey, thanks so much for the clarification. Didn't realize it hinged so much on the standard, so I just looked into them more and it makes sense.
Comment #3
patcon commentedComment #4
Jerome F commentedSubscribing
I hope address field, location and adresses will merge in the future in a good address field with full views integration.
Comment #5
Jerome F commentedI think we could also imagine merging address field + phone + Gmap (or an other map module like geofield, geolocation, etc.) + countries + etc.
in a field collection to take advantage of D7 entities and the best specialised fields available
This way you make the modular address field you need for each website.
http://drupal.org/project/addressfield
http://drupal.org/project/phone
http://drupal.org/project/email
http://drupal.org/project/countries
http://drupal.org/project/gmap
http://drupal.org/project/field_collection
Comment #6
patcon commentedSounds like something that might be packageable as a feature. Sometimes I wonder whether a feild collection-type solution might be best for all of address field in general...
But yeah, I'm thinking that I'm with you in your thinking
Comment #7
Jerome F commentedYes a feature package would serve this purpose very well.
Comment #8
Jerome F commentedThis issue is interesting considering the roadmap of location's future development and integration with addressfield: http://drupal.org/node/1063920
Comment #9
damien tournoud commentedI think the information has been given here.