I must apologize for basically falling off the grid for so long. I know many folks are annoyed that this module has just sat here for like a year. I've been working two jobs that whole time. Fortunately, my day job has allowed me to start using Drupal and I need to update most of my old modules. This is one of them.
Why not use the addresses module? Frankly, I don't like it. I don't like how it works, I don't like the admin options (or lack thereof), I don't like its display and several other things. That said, there are a couple of things it has that I like.
What will this new D6 version have?
- I already stole the country and state lists from the addresses module. Database-stored, not Drupal variables.
- Full AHAH support for country/state
- Full Views 2 support
- Full Token support
- Full Diff support
- Full Location support
- Maybe the microformat stuff from addresses
- Ability to validate against a known list of addresses (as before, this is set up for my needs but could be expanded to a more general case if there's a demand)
- A validation API (a rework of the existing one from cck_address - no longer need separate modules for each country)
- Both global and per instance settings
- The same customization settings as before
- Better theming support
- Separation of functions into many files to minimize memory usage
I'll also go through the issue queue and make sure I don't carry forward any nasty bits you've all found lacking.
Questions?
Comments
Comment #1
rconstantine commentedI forgot, I will also support multiples and I'll look at the idea of address books for users. I won't have phone and fax included in this. There's already a dedicated module for that http://drupal.org/project/phone.
Comment #2
aren cambre commentedExcellent! (subscribing)
Comment #3
Jagg3d commentedNice!
Comment #4
michelle"Full Location support"
Does that mean this could be used instead of the location form and still have all the other functionality?
Michelle
Comment #5
quinn-2 commentedcan you upload a patch file? i'd love to try it out right now
Comment #6
rconstantine commentedNo patch is ready yet. Got side-tracked with other work (thank my boss!) but am back on this tomorrow (tonight actually). I need this for both my day job and my side work, so this is a priority for me.
@Michelle, by "Full location support", what I mean is some kind of Geocoding. Originally, I thought I'd make this compatible with the Location module, but now I'm leaning toward Geo and Geocoding modules instead. But in any case, that will be the last thing implemented most likely and I'll have a release which includes support for diff, views, token, etc. before that. Those are all much smaller and easier to crank out.
Comment #7
michelle@rconstantine: Ah, too bad. I use location/gmap but don't care for the form that comes with location. I'd prefer a CCK based one and was hoping this would do it. Thanks anyway. :)
Michelle
Comment #8
quinn-2 commenteddoes this module store the address's lat and long?
Comment #9
rconstantine commentedA few days has turned in to many, but progress is being made.
Comment #10
deviantintegral commented+1 for a patch for testing, or a CVS branch for Drupal 6. I'm working on a D6 site and I think this will be more appropriate than Addresses.
As for Location integration, my patch against D5 may be useful if you haven't seen it: #424698: Location Integration
Comment #11
neilnz commentedI can't wait - building a site now that could use this. Subscribing.
Comment #12
quinn-2 commented@deviantintegral yeah, a super buggy patch is better than no patch at all.
Comment #13
rconstantine commentedFolks,
I wanted to take a moment to explain why this is taking so long. It comes down to two things. First, I'm working on this at work, for work, but it is not yet critical, so other things are fighting for my attention at the moment. Second (and this is the big one) there is a major hurdle to overcome which nobody has been able to figure out in any CCK module for D6. That hurdle is the 'simple' function of updating one select field based on the selection from another one. For regular modules, this is really easy. For CCK, not so. However, based on my work on the 'nested fieldgroups' patch which will make its way into core CCK (after the row delete and multigroups patches), I may have a solution. I'm working on it, but it's going slower than I want it to. The module is unusable at this point due to this, but once this part is accomplished, the rest is pretty easy, including Views 2 integration, token, diff, etc. Even the geocoding (or whatever I choose in that regards) is easier than what I'm trying to get over now. If my current path doesn't work, I may need to patch CCK itself.
One funny thing about this is that supposedly when D7 comes out and fields are part of core, there will exist a function that would solve this issue. Unfortunately, a back-port of that is not possible due to other constraints.
So be patient, cross your fingers, wish me luck. If I do succeed at this, then that will also mean that modules such as 'hierarchical select' should also be able to use my methods to update their CCK portions as well.
Comment #14
AmitV-2 commentedsubscribing, excellent been waiting for this, good luck
Comment #15
AmitV-2 commented"Ability to validate against a known list of addresses (as before, this is set up for my needs but could be expanded to a more general case if there's a demand)"
Please convert this into dependant select lists, i.e. Country->State. Rather than use what the addresses modules uses, where we need to type out the State/Province and wait/check for validation.....
Comment #16
rconstantine commented@AmitV's #15... that's the hard part and why nobody else has done it before. I have literally been down a dozen or more dead ends trying to get this to work. I have about 4 or 5 more things to try, but each one takes a lot of effort and so that is what is taking so long. I'm about to scrap the current method and try the next one. This may be impossible, but I'm going to keep at it because not only would it be worth the effort, but it would be cool! ...and useful to know the method that works in order to use it on other CCK projects.
Comment #17
3cwebdev commentedSub
Comment #18
goodeit commentedsubscribing
Comment #19
monotaga commentedSubscribing
Comment #20
Craig Gardner commentedsubscribing.
Also +1 for a D6 branch for testing.
Comment #21
rconstantine commentedLooks like this is going to require a patch to CCK. Once done, I'll see about CCK taking the patch so you all don't have to hack CCK.
Comment #22
csc4 commentedSubscribing
Comment #23
Poieo commentedSubscribing
Comment #24
Shai commentedSubscribing
Comment #25
asak commentedsubscribing.
Comment #26
izmeez commentedsubscribe
Comment #27
will_in_wi commentedDo you have any kind of timeframe for a working version? I have a short timeline to upgrade a site to d6 which uses this module. The more I use addresses, the more I hate it, but I will make it work if necessary. Can you post a dev version of the 6.x port once it will upgrade from 5.x and allow entry and display?
Have you submitted the patch for cck mentioned in #21?
Thank you
Comment #28
Parkes Design commentedAwesome I've been waiting for this module...
Subscribing
Comment #29
jrabeemer commented+1 A very interesting module indeed!
Comment #30
m_d_mcbride commentedAlso very intrested in this module, especially since it will support multiples
Comment #31
cimb commentedsubscribing
Comment #32
Anonymous (not verified) commentedAlso it would be great if you built in hooks for Node Import.
Comment #33
notarealperson commentedAny update on this upgrade? Last update was 6/5, and the original post stated "a few weeks away" on 4/11. Regardless of the state of the upgrade it would be good to know so I know whether it's worth waiting or if I should look elsewhere for my needs.
Thanks!
Comment #34
BenK commentedSubscribing
Comment #35
rconstantine commentedSorry for no updates. As you may or may not know, this is going to require a patch to CCK itself as the current framework won't allow for the functionality we desire here. I am waiting to do this until the nested fieldgroups patch is included in the 3.x version of CCK. The maintainers want it in, but are having time issues themselves in reviewing it. So this is on hold again. Sorry folks. I do really want this as much as you all.
Note, the 3.x version of CCK offers a work around - multigroups. It at least lets you put all of the fields required for an address together as a unit. However, you don't get extra validation, or other functionality you would get from an address module.
Comment #36
donquixote commentedsubscribe
Comment #37
SeanBannister commentedSub
Comment #38
alan d. commentedHi
Just wondering on progress. Are active changes in HEAD or another branch in case someone can jump in and help. And this is a bit premature, but do you have any Drupal 7 plans yet? I'm starting a personal project that will probably take 5 months, so I doing this in D7 and I've already written three new multipart fields and a simple address one is on my list of requirements.
Any plans on an adapter class for your data sources? I am considering using the geonames database, which would allow a single autocomplete at the town / city level to populate the state / country fields automatically for any significant population on the planet. See TaxiSelect if you are wondering how such a claim is justified. A simple 3 table join would be able to do a similar thing for this module, or a single query if the data source is denormalised.
Cheers
Comment #39
PRZ commentedSubscribing
Comment #40
shady_gun commentedSo whats the status of this?? is the owner releasing drupal 6 version soon???
is there any development version of drupal 6 ..
if not, guess i will try to port it myself ...
cheers
Comment #41
will_in_wi commentedI switched to the location module in all of my sites. It has been around for quite a while and is supported by many other modules including gmaps.
Comment #42
aren cambre commentedI recommend abandoning this module: #617974: Please abandon Address field for CCK module
Comment #43
aren cambre commentedIs this module abandoned?
(This is the first step in the "abandoned modules process" for this module. If no response from module admins by 1/29/10, this needs to be transferred to the Drupal.org Webmasters project and assigned to the Project Ownership component.)
Comment #44
NewZeal commentedWhy are you so keen to abandon the module? Maybe the Usage Statistics don't mean anything but it appears that people still use it. Plenty of people still have D5 sites and to remove this module from here might leave them with no where to go if they wish to re-obtain the code.
It is true that in D6 users are now moving onto Location module. I know I have. Also the addresses module is getting the attention it needs to be fully functional.
Comment #45
aren cambre commentedJust trying to clean things up. If you could state this on the module home page, that would be helpful.
Comment #46
deviantintegral commentedI'd like to point out #424698: Location Integration which is now included in the module which could be used to migrate data to Location. It's probably the best solution for anyone hoping to upgrade to Drupal 6.
Comment #47
NewZeal commentedcck_address module is staying here for as long as Drupal 5 is downloadable from drupal.org to enable Drupal 5 users to retain access to it.