My members who are first-time users of Wildapricot are complaining about the lack of closure during online registration. After clicking Confirm, where they might have expected a "Thank you for registering," they get the attached instead. "! This invoice is unpaid!" Of course it's unpaid. All invoices are unpaid when they're presented. Since we're operating in offline payment mode, there is nothing the member can do about it at the moment anyway. Please change this ugly non-assurance to something that gives some closure. The wording here is not just a gaffe for offline payers; it's a gaffe for everyone. People might not notice it after a few times registering, but it is still disrespectful to our members.

Not sure if it is here already here, but an internal [post login] member to all members communication like a list serve is badly needed. Members can connect with 1 on 1, but a way to communicate to all members wo option in for members to members communications is needed badly!

• member logs in
• member selects send message to all members
• member composes message and it is sent to all members opted in to receive mass members communications
• messages can be flag to admin
• admin can set to moderate messages first before they send
• members must login to access, view, and reply to mass messages

I am fine with the limited selection of font families, with long experience working on the web before we had all the web fonts. What I'm really struggling with is matching font families and general styling between the new editor and the older automatic email editor.

For example, our chosen website theme uses Open Sans. Great all around sans serif font. I can also use it in manual emails so that they are styled much like our website. But automatic emails do not have a similar or even decent sans serif font ('Basic' is just ugly) so I chose Trebuchet. Now the problem is that event email mix up the two, using what's available with automatic emails (Trebuchet) but including event details that match the website (Open Sans). The result looks amateur and like we don't know how to use this system.

And don't get me started on the color picker. One editor has our theme colors all right there! The other forces me to find, copy, and paste the hex code for every single hyperlink so they better match the colors and logo.

We use the membership poll for elections, which works great! But we also use the poll so that members can vote on proposed bylaws amendments. The body of the poll is limited on space. It would be great if this was not limited. Each question in the Q & A portion is also limited. Could there be an option for an unlimited question text box which would allow us to enter the current bylaw language and the proposed bylaw language the allow the user to vote. Not all questions are short and sweet. I think all users would appreciate the flexibility to add a question to the poll that was an unlimited text box.

I'd like to be able to email everyone with a given registration type. Right now the "registrants" tab allows me to sort by registration type but not filter. There are several other filters though.

Example: Registration type 1 is general attendee. Registration type 2 is VIP. I can easily email VIPs to let them know where to go at the event to take advantage of their VIP status.

Current workaround: email all attendees and include info for each registration type (quick but inelegant) or export all attendees, filter in spreadsheet and then use another email system to send emails by registration type (time consuming and requires use of two other tools).

Add a new attribute – something like “Enforce Uniqueness” – to the Common Fields setup window. It can be grouped under the Options heading just underneath the Required Field attribute. Users can tick mark the box or leave it unchecked. Then add some type of downstream verification check, ideally at the Dropdown List Level: When the user clicks into a field’s drop down list, check to see if Enforce Uniqueness is selected on that field. If Yes, compare the user’s selection from that list to the existing values for that field in the database. If there is a match (i.e., saving the selected value would result in a duplicate) then reject the entry and give the user a message like “The selected <name of field> already exists. Duplicates are not allowed.” Alternatively, it would be ok to check for duplicates when saving the contact data. WA is already doing field validation for Required Field during saving, so just extend that check for user fields deemed unique. It would be ideal to reject duplicates as early in the workflow as possible but checking during saving would also work.
ps. The creation of duplicate contacts is the biggest challenge we have with the system. We're a HOA, and since only the primary email is unique in WA, spouses and other family members are creating duplicate contacts with their own email addresses.