Port Zipcode (CCK) module to Drupal 7

Subscribing.

Subscribing

Subscribing

subscribe

subcribe

...less vague title & proper tags.

subscribing...

subscribing

"CCK" should be removed from name as part of port. See #157784: Name should just be Phone.

As I similarly suggested to that issue too, the project's name should be plain "Zipcode", while the 6.x .info file could call it "Zipcode CCK" and the 7.x .info file "Zipcode field" or "Zipcode fields". This would both make sense and at the same time clearly imply/explain why the one requires CCK while the other requires D7 core Field API.

Actually, the project name should be Postal Code, since that is the common term used world-wide. Zipcode is the American implementation of the postal code. Is there a way to rename a project?

Is there a way to rename a project?

I could only find this.

The link is asking for a login.

It wasn't when I checked 2 days ago :/

Anyways, here's what I could find (courtesy of Google cache):

Drupal project renaming

Added by Todd Nienkerk, last edited by Robbie Sternenberg on 2009-01-15

How to rename a Drupal project

• Check out all relevant branches from CVS
• Change all branches so that all instances of "OLDNAME_function" (and the like) are replaced with "NEWNAME"
• Create install hook for NEWNAME module that:
  • moves variable values from "OLDNAME_variablename" to "NEWNAME_variablename" (See Useful .install file functions)
  • renames appropriate tables/columns
• Make sure uninstall hooks are in place to remove variables, tables/columns, etc. (See Useful .install file functions)
• Commit oldest branch of NEWNAME module to CVS (this will be HEAD)
• Make new project page on Drupal.org
• Release 5.x version:
• branch DRUPAL-5
• tag DRUPAL-5--1-0
• Release 6.x version:
• overwrite local files with 6.x version and commit (HEAD is now 6.x)
• branch DRUPAL-6--1
• tag DRUPAL-6--1-0
• Shut down OLDNAME project on Drupal.org
• Unpublish all releases for OLDNAME module
• Create note on OLDNAME project page that says "This module has been replaced with _____"

...hope this helps.

Hey guys,

I'm just wondering if somebody is working on get this port done?

I have not seen anything about the port to D7 in this issue and I would like to know.

Thanks.

Maintainer here. I am not actively working on this module. I volunteered to be the maintainer because it hurt to see so many good patches waiting in the queue. However, I may need a D7 version within a few months for a project. If so, I will port it.

I appreciate that and thanks for the information.

Since this issue has been up for a year, I hope it's not presumptuous of me to say I've taken the liberty of writing a separate module for d7. Liam, et al: your version is amazing for D6 & CCK.
D7 just needs so many changes, that I'm offering my (sandbox version) as a possible alternative: Postal Code. I'd be very happy for any feedback. Countries available:

• USA
• Canada
• UK
• Germany
• France
• Italy
• Australia
• Netherlands
• Spain
• Denmark
• Sweden
• Belgium

Fantastic! I was planning on renaming the module to postal_code as part of the D7 upgrade. Because of the many changes, I was planning on using the D7 phone module as a model. I also wanted to get more of the country-specific code into the country-specific files.

If you've already got a start, that can be the start of the D7 version. Once the D7 version is working, there should be an upgrade path from zipcode.

Let me know if you need my help.

...this is good news!

I just filed #1564358: Initial release of Postal Code? / Current status / What needs testing ...a.k.a. "Are we there yet?". Should we close this issue here and take it there instead? If so, then perhaps people coming to this project's page deserve to be informed that there will be no D7 port but a complete rewrite instead (with a link to the other project). It would also be nice to let people know that you intent to provide an upgrade path from Zipcode to Postal Code.

Agreed.

The Drupal 7 version of this module will be called Postal Code. There is currently a sandbox version of Postal Code. The upgrade is discussed in #1564358: Initial release of Postal Code? / Current status / What needs testing ...a.k.a. "Are we there yet?".

Creating an upgrade path should be part of the process of writing Postal Code. I can't really help with this because I don't have a D6 site so I can't do any testing.