Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Would be good to rally to finish up the major outstanding issues and put out a stable release of this module.
Crazy that both the Phone & Phone Number module don't have stable D7 releases at this point. Really wish that we'd have had one well supported phone option rather than two approaches to supporting phone numbers that don't really have sufficient developer resources.
Comments
Comment #1
crutch CreditAttribution: crutch commented+1
Comment #2
Nephele CreditAttribution: Nephele commentedIs this module actually still being maintained? It's been nearly a year since there were any updates, even though issues (e.g., #1160186: support for Feeds importers) have been RTBC for months, and the maintainer hasn't even responded to any issues since last September.
I'm asking because if this module actually has a future, I'd be willing to contribute code/patches/etc. For me, the phone module is currently unusable because of #641984: Single phone field supporting all formats. Debugging cck_phone is easier than fixing phone -- especially considering that cck_phone was originally created because ckng presumably thought it was easier to start from scratch than fix phone.
On the other hand, if this is module is dead, that implies that #1812184: [meta] Rewrite and merge phone and cck_phone is where the community should be investing its effort. Or is there some other option?
Comment #3
ckngDev version is stable for production. No stable release because would like some features to be in before posting a stable, which at it stands, likely won't happen, see below.
cck_phone is not dead and considering next logical step is libphonenumber as discussed in other threads, and phone current maintainer willing to merge, that would be the direction. So all planned features are on hold to get libphonenumber support in, as most are already covered by libphonneumber.
Comment #4
ckngBTW, I know about #1160186: support for Feeds importers, I read every issue queue, in fact. Like I mentioned previously, dev is stable, would like to test the patch personally before committing it since only 2 persons actually reported back on the patch. IMHO, anybody dealing with feeds importer should have no issue applying that patch.
Comment #5
roball CreditAttribution: roball commentedThen I don't understand why you are not willing to tag a 7.x-1.0-beta1 release of that "stable" branch.
Comment #6
mgiffordThis hasn't been formalized or anything, but really don't think that the process of keeping a module in dev until all of the features are built into it is a best practice. #2186377: Highlight projects that follow Best Practices
I'm with @roball