Addresses, profile2, fieldAPI and so on
I've been working on the FieldAPI version of Drupal core's Profile module.
One of the potentially very cool applications of this would be a module to handle addresses in such a way that:
- the user can edit their addresses within their profile
- they can appear on profiles, member directories, etc
- modules like Ubercart can suggest them to users as billing and shipping addresses
The other big benefit would be that all the horrendous country-specific stuff like postcodes and the like could nailed once and once only :D
I'd be very interested to work with Ubercart developers to make sure profile2's API provides what is needed.
Comments
Awesome news, joachim. It
Awesome news, joachim. It might be worth contacting DamZ (Damien Tournoud) if possible, as I know he's also done some work in the address space for a recent project we worked on. I would love to kill the country system as it currently exists in Ubercart. : D
+1 for working with profile 2
+1 for working with profile 2 api.
I quickly followed the big topic about fielf api applied to profile and it was cancelled for D7 to be planned for D8. The profile 2 api is to make field API applicable on profile for D7 (correct me if I'm wrong).
So, this extend the possibility of profile, and it will be in core for D8, so I think wa can abandon the classical profile module today and work with tomorrow's tools.
The plan is for profile2 to
The plan is for profile2 to be a contrib module for D7.
Its basic aim is to be a replacement for the old profile module, based on FieldAPI.
But I very much want it to be the base system for collecting and storing data about users (or indeed, non-users).
There's an issue open to discuss the module's architecture here: http://drupal.org/node/623210
I'm starting to wonder
I'm starting to wonder whether addresses should be entities in their own rights, and therefore whether there should be a standalone address module that provides these, along with an address_reference field and some nice UI so users can enter new addresses on the fly.
In other words, something that is partly a FieldAPI conversion of the uc_addresses module.
This would then be a building block for both Drupal Commerce and a Drupal CRM.
What requirements does Drupal Commerce have for addresses?
BTW, the Drupal CRM project -- now DropCRM -- has got itself a domain and a site (whose theme looks strangely familiar for now... ;).
postaladdress module
AFAIK, Drupal Commerce plans to use the postal address module. I haven't studied it yet to see if it's just a Field type, or providing full blown entities. I'm concerned about having too many entities, but understand why it might be a good idea for addresses.
I don't believe it's an upgrade of uc_address. It's a fresh start, which is fine by me.
Postal address is on damz's account on github. I can't post the URL, or the spam filter will block my submission, apparently.
github . com / damz / postaladdress