Skip to:

Opened 12 years ago

Closed 12 years ago

Last modified 2 years ago

#3962 closed enhancement (wontfix)

Address field type for extended profile

Reported by: sooskriszta's profile sooskriszta Owned by:
Milestone: Priority: normal
Severity: normal Version: 1.2
Component: Extended Profile Keywords:
Cc: sooskriszta


There should be an “Address” field type.

This should show a country dropdown...on selecting the country, it should show appropriate state, city dropdowns, along with other address fields.

Change History (8)

#1 @sooskriszta
12 years ago

  • Type changed from defect (bug) to enhancement

#2 @r-a-y
12 years ago

  • Component changed from Core to XProfile
  • Severity changed from major to normal
  • Version changed from 1.5.3 to 1.2

Related: #1327

#3 @DJPaul
12 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

No; while allowing the idea of linked xprofile fields is an interesting one, it'd be a ton of work to build a list of states and cities (not to mention this sounds very specific to the countries with states, like the USA), and it would be a lot of extra work for translators, too.

The ticket r-a-y links to is about importing a set of data which can be used to populate various profile fields; that's a better approach to bulk-loading this type of data into BuddyPress.

#4 @sooskriszta
12 years ago

I think the functionality that we are after is "conditional" fields. i.e. A list of states loading based on country selected.

The data (countries/states/cities/etc) may not necessarily have to be packaged with BuddyPress.

Come to think of it, conditional fields could have many more applications than just addresses.

#5 @sooskriszta
12 years ago

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Sorry, reopening - no disrespect intended. Just hoping to have my above comment read...not sure you get any updates after a ticket is closed.

#6 @boonebgorges
12 years ago

  • Keywords reporter-feedback added

The lead devs (and anyone subscribed to the omnibus mailing list) gets notifications for updates to all tickets, whether they're open or closed.

I guess I'm not clear on how the concept of 'conditional fields' would be cashed out in a way that is sufficiently general (so that we don't have to ship with a list of every country in the world, for example) and yet still useful to plugins. Can you give a fuller sketch of what this would be?

#7 @sooskriszta
12 years ago

Well, I can imagine "conditional" or "nested" fields in this way:

  • First the admin shall have to define a profile field as nested
  • Next, he will see options for individual fields inside there ... a bit like when you do multi-level bullets in Word....first you tell what is the top level field type, next you can say what is the 2nd level field type, and so on...(there shall be an "add another level" button just under where admin is selecting top level field type...and so on...)
  • For this to work, all the fields need to be closed (obviously). field types could be dropdowns, checkboxes, radiobuttons, etc
  • In addition to defining field type for each level, the admin will have to select condition from a dropdown (default being '=')...'=' '<>' 'includes'
  • Finally for the custom field, the admin will be able to upload a csv whose rows would indicate level of hierarchy

e.g. In case of address
lets say top level = country
2nd level = state
3rd level = city

the condition the user should set in the dropdowns for both 2nd and 3rd level is '='

the csv would look something like this:

canada, alberta, breton
canada, alberta, calgary
canada, alberta, vermillion
canada, british colimbia, dawson creek
canada, british colimbia, maple ridge
canada, british colimbia, richmond
canada, british colimbia, vancouver
u.s.a., alabama, birmingham
u.s.a., florida, miami
u.s.a., florida, orlando get the idea

This could be used for a variety of things...addresses, departments in a university, specializations for doctors...

At some point a glotpress-like mechanism could be used to maintain a central, collaborative database of common csv for country, region, city...

#8 @boonebgorges
12 years ago

  • Keywords reporter-feedback removed
  • Resolution set to wontfix
  • Status changed from reopened to closed

What you describe would definitely be useful for some instances, but it would take an enormous amount of work for what I think is a modest gain in terms of functionality. I'm going to close this again as wontfix, as I think that this is pretty clearly plugin territory, and I don't think it's worth the many dozens of dev hours it would take for BP core. That said, if someone writes a really dynamite patch, I think we can reconsider.

Note: See TracTickets for help on using tickets.