Because if a designer was signing up for a profile, they use that same list – if Paris wasn't on there, I'd have to add it manually when someone needed to sign up.

It's not the best solution – this is where my programming inability shows through. Going to be revamping that soon, but right now, it's on there so people can sign up with it. :)

Oh, ok, but why did you include "Nantes"? It's unlikely Nantes was already there and it just happened that a designer found it?

I don't see why there couldn't be a different list for signup and for search; or the ability to add cities during signup...

Because someone emailed me and asked me to add them under that location. :)

Yeah, probably, I just haven't thought it through yet. I'm still not a rockstar programmer — I figured out that I can make a list in the model which would be referenced by the registration, search, and also apply to the property in the profile model. Initially it seems like having the same list in two different locations and slightly different in each seems like a bad idea, but also having random locations on the search list without results is too. Though maybe I could write something in the search view that will remove listings from the form if they don't have any profiles associated with them...

</n00b>