Cannot "null" a dropdown from a predefined values

As reported many times here, you cannot have an empty value in a drop down created from a predefined values table.

http://www.boonex.com/unity/forums/?action=goto&my_threads=1#topic/Drop-Down-Menu-Select-It.htm

This simultaneously screws up both the join form - because whatever is at the top will be entered as the value; and it screws up the searches, because you can only have one drop down in a search - otherwise it will take the default value of one of them - the top value.  There is no way to "null" it in either place.

For some reason we have had difficulty getting Boonex to accept or understand this issue - I even heard a developer call this "a feature".  This is strange, because it worked perfectly well in D6.   I believe there is a ticket for this for 7.1, but this should be fixed before this.  In fact, this is a critical but and D7 probably should not have been released without this working.

Rob

Quote · 8 Jan 2010

Hi Rob,

Do you or anyone else know if this is going to be sorted anytime soon.

Really how can you make a dating site without ''null'' dropdowns

 

Thanks

Chris

Quote · 17 May 2010

I haven't tested with D7.01 yet, and I am going to cry if they didn't fix it.  They probably didn't.  I don't think they care.

Quote · 21 May 2010

My comment on this on the Boonex 7.0.2 post was censored (it was polite), as was a detailed blog post I wrote - plus the Trac on this was incorrectly closed.    I have not installed 7.0.2 yet but I am assuming this has not been fixed - otherwise they would have just said so, rather than deleting my comment.  Does anyone know for sure?  I honestly believe almost everyone will come across this issue eventually.  Problems with the join form and search functions are central.

Quote · 17 Jun 2010
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.