We need the ability to hide the field label if there is no response in the field. Whether this is checkboxes, radio buttons, picture, etc. If there is no response in the field, the label will not display on the contacts profile.

We wish to use this with the picture field to implement a badge program where contacts/members can earn badges of recognition from our organization. I can have a separate picture field and upload the image to that field when the contact/member earns a particular badge. However, it looks sloppy if there are 9 badges and a person has earned 5; then there are 4 field labels with no image. It would look much cleaner if the labels only appeared on the contact profile only if the badge image was there (field was populated)

Dear Wild Apricot,

I am setting up an account that has various membership levels plus it allows people to sign up just for an email newsletter without membership. It would be really nice to have a separate profile page (or the ability to set fields for the profile) based on membership or non-membership. The profile page shows invoices as well as subscriptions to forums to forums, for example, to people who are non-members. I think this is confusing.

Also, it would be nice to have be able to set when fields are required or not based on whether someone is a member. For example, I would like to have the first and last name be optional for people signing up for email newsletter but have it required for members.

Thank you.

When we use normal text fields and members want to post a lengthy URL (for example to a Facebook Page that includes browser parameters in the string) it totally destroys the page layout since the long URL will not be "word wrapped" into multiple lines but remain one single liner that extends the layers divs.

Solution: Have a NEW membership/contact field type named "Link field" where a member just be able to fill in legit URLs and the field encloses the URL in a link tag where you can either then have it displayed as "Link" in the member profile or as a short significant name of choice.

It would be very helpful to be able to add a common field which can be changed only by the administrator, but still be seen by non-members or members (depending on what options have been selected under common fields). This way a rating could be input by the administrator, without being accessable by the member, but still be viewable by anyone.

For example the admin adds a new common field called 'Ratings' - Options set at 'for administrator access/input only' - Others access set at 'Anybody'- this would allow the administrator to manually add a rating to a member as such:

Rating: 5/5 Star Rating (1 vote)

(Common field name: input by admin)

Is this possible at all???

We had an old discussion about adding new type for a custom field - numbers:
http://forums.wildapricot.com/forums/308920-archive/suggestions/8834458-create-numeric-fields-7304

When we started our analysis work on this problem, we realized that we have no clear vision of what is underlying problem that our clients want to resolve with this new field type.

Most comments were about export into Excel, so it can properly recognize numbers. But from our point of view, export itself is a workaround to another problem - something is missing in Wild Apricot functionality and you try to substitute it with export. This means that adding new field type will not truly resolve initial problem, so at some level it's not a real system improvement and we usually try to avoid such system changes.

On the other hand, we might miss something important and Numeric field type can really be useful and fulfill some of an organization necessities (please, do not mix Numeric type with dates and other field types - for dates we can clearly see scenarios). For example, to validate user input when your members apply for membership (but in this case what in particular the field is about?)

So can you please help us:

1) We need your reasons and examples of why your particular organization would benefit from having Numeric field - ideally, not as a workaround of a bigger problem.
2) Do you need to have ability to search on this numbers like "less" or "greater" or "between"?
3) Do you need integer type, decimal or both?
4) Do you need special validation rules for the field like "cannot be less than..." or "not greater than"?

Hi guys,

I love the advanced search feature, with one exception. The "Radio Buttons" field should be searchable like a checkbox field is. This is the search for a radio button field:

Whereas the checkbox search looks like this:

I think they should have essentially the same options. There are some questions that I do not want members to have the option to choose multiples of - for example region. They can only live in one region, so I do not want them choosing 3-4 regions.

However, I'd like to be able to run a search for those who are NOT in ANY region, and so forth. The checkbox search is far more functional than the radio button search.

Thanks in advance for your help.