Profile "Country codes Field" module 6.x-0.2 released

Hi Robert. Glad you got it working. One thing I would say is to give some thought to the name of this project, as it serves a very specific purpose - that is, overriding a specifically named custom profile field. Perhaps the modules name should include something to indicate this, as at the moment, it sounds like it is a field that can be used anywhere. How about profilefield_countrycode, profile_countryfield, or profile_countries. Alternatively, could this not also be done by creating a cck widget - which would then be much more flexible and more suited to the name countrycodes_field (or just country_field)? Just a thought...

Indeed, with Fields now being in core in D7, doing it as a CCK widget could position this as a premier solution that is somewhat "future proof." And, just a thought, perhaps it could be worked into the theme_username implementation in the RealName module.

bookmarking, greetings, Martijn

Can you please publish modules rather than letting these get lost in a closed issue, even if it is just getting them into CVS. This helps other developers to see what is already out there, it helps to prevent duplications and allows others to contribute back to existing modules.

Speaking of duplications, I've spent a couple of days creating a simple country module as I needed a country field in Drupal 7 project that I have just started playing with.

It provides the following three things:

• A base country table, using shameless rip from this module merged with the continent patch (http://drupal.org/node/255215) and Drupal core countries. Schema used is.
  

  CREATE TABLE `countries_country` (
    `iso2` char(2) NOT NULL COMMENT 'ISO2 country code.',
    `iso3` char(3) default NULL COMMENT 'ISO3 country code.',
    `name` varchar(80) NOT NULL,
    `printable_name` varchar(80) NOT NULL,
    `numcode` smallint(6) default NULL,
    `continent` char(2) NOT NULL COMMENT 'Continent code.',
    `enabled` int(11) NOT NULL default '1' COMMENT 'Whether the country is enabled.',
    PRIMARY KEY  (`iso2`)
  ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='Maintains a country database.';
  

• A simple UI to edit / add countries. Countries from core can be disabled but not deleted.
• A country FAPI element, 'country'. A simple prepopulating select list based on enabled countries. It has a inbuilt filter for all/enabled/disabled countries. It also has a simple continent filter.
• A country field, called Country, with the same characteristics as the FAPI element.

The code is committed @ http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/countries/

Should I go ahead and publish this? It's really late here so I haven't reviewed the above module to see the overlap.

@Alan D: I though Roball had published his contribution.

Regarding your own contribution (which I have not yet looked at). Perhaps you should seek to try and get the additional features that you need included in this module, or as a sub module of this one. There are already over 500 people using the countries_api module, and several other modules depend on it too. It seems a little silly to publish yet another project with pretty much the same functionality. My view is that there should only be 1 module with the iso2 iso3 country data (this one). That means only only place to keep these values up to date. I think there are plenty of other projects out there that could already benefit from using countries_api for its iso country needs (ubercart, location etc etc).

Please consider joining forces before you start your own project.

I’ll let Roball update this thread to let the world know about his progress in this. Updated the title to indicate that this is a Profile feature

I’ll created another issue about the other things. @see http://drupal.org/node/597748

Thanks for the update.

We had a complex user profile requirement recently so I know the headaches with Drupal profile module. We rewrote the field management of the Profile module to do what we required as the content profile module just didn't cut it. I guess now we have a easily extendable profile module for the future, at least till Drupal 7 comes out!