I installed the module, added a new profile select field "Country" and single line text field "Zip Code". Then I visited admin/user/profile_locality and selected those 2 fields for the corresponding module fields. The Country dropdown is completely empty. When I visit admin/user/profile_locality there are no options to select in the "default country" dropdown.

Comments

johnhanley’s picture

johnhanley commented

Hmm, you're going to need to give me a little more information in order for me to help. This includes:

1) the profile field names
2) a list of other enabled profile related modules
3) perhaps screen shots of the configuration pages

Any other details you can think of to help diagnose the problem.

John

charlie-s’s picture

charlie-s commented

Thanks for the help John.

1) I'm using these profile fields:

  • profile_zip_code
  • profile_country

2) Profile (core), Advanced Profile Kit, Profile Locality

3) http://imgur.com/E6bWJ

I should also note that I checked the DB logs after installing this and found no MySQL errors or anything like that.

johnhanley’s picture

johnhanley commented
Category: bug » support

I'm not acquainted with the other third-party profile modules you mentioned, but it's quite likely that they're not playing nice with each other. I would suggest you pick the one that best suits your needs and not use multiple modules that provide overlapping functionality.

For complex profile requirements, I would suggest you use Content Profile.

charlie-s’s picture

charlie-s commented
Status: Active » Closed (works as designed)

There was only 1 contrib module above. Profile (core) refers to the Profile module that ships with Drupal and is a requirement for Profile Locality. I have disabled APK as it is actually an extension of Content Profile and it turns out I am not actually using that module.

I tried to run the install code manually and I've discovered the error: LOAD DATA LOCAL INFILE is not supported in my MySQL version. I'll import the data manually.

Thanks for your help.

johnhanley’s picture

johnhanley commented

@csdco, thanks for following up.

Just out of curiosity, what version of MySQL are you running?

charlie-s’s picture

charlie-s commented

5.0.45

A bit of research shows that the command worked even back in MySQL 4, but it looks like it's a bug in 5.0.x or 5.0.45 which apparently was a popular edition with some standard hosting builds. No biggie.

johnhanley’s picture

johnhanley commented

Huh, I had no idea this bug existed. How obscure.

Anyway, thanks for letting me know.