Web space is a premium and managing the space is a vital element of more content. Currently posting a blog posts text up to 10 lines and offers the read more option. If we can limit the opening post to a more concise presentation to say 5 lines or less it forces us to be more content rich with our opening line and we can register more read more clicks. The strategy is not to tell too much in ten lines, but just say enough in 5 lines or less so our users are prompted to read more.

I hope this makes sense and others can appreciate a short catching message instead of telling too much and a user doesn't click read more.

In our 2.36 update we have released Groups functionality - ability to organize members into groups - such as 'Board of Directors', 'Volunteer Committee', etc. These groups are independent of membership levels - one group can include members from different levels. These groups can be used to keep track of member participation in committees, restrict access to website pages to a particular group, or for advanced searches and emails. Seehttps://help.wildapricot.com/display/DOC/Member+groups

We are contemplating a number of possible further enhancements to this and would love to get your feedback.
Here are our initial ideas:

1) Group moderators. Group moderator is a member of group who does not not have any WA administration functionality but can add/remove members to group.
Note: To do this it will be necessary to let group moderator access the full list of members and member details.
- Should moderator be able to send mass emails to group members?

2) Administrator role with web editor access limited to particular group pages.
Current functionality allows you to setup account-wide web editors and group-specific read access to web pages. This enhancement would allow you to assign a web editor in a particular group - who would only be able to edit/create pages in that group.
- Is this the same person as group moderator in 1)?
- Should this person be able to add any functional - or only content pages?

3) Group-limited events. (And probably an admin role to add/edit group-specific events)

4) Administrator role with member record edit rights for a particular group. This can come handy if you are using groups for chapters.

5) Ability for people to apply to groups during the membership application process - with workflow to review and confirm their participation in a group.

Currently if an event is announced using the event email settings the organizer's email address will go to all recipients. The only way to protect the email address of the organizer is require that the event organizer be listed using a more generic administrative email address but this will reroute all event email reports on registration away from the organizer as well.

This proposal is that there be an option to use the admin email return address but to include a hyperlink to the organizer's personal message system contact web page.

The status of this option would map the organizer's profile for the personal messaging system. If PM privacy setting says members only and the email goes out to non-members, the option would be grayed out. Under the same settings if the email goes out to members only, then the option would be grayed in.

Many membership organizations (golf clubs, etc.) have policies to continue invoicing members even in the event that a member fails to pay the invoice for the preceding membership term. The primary reason that organizations do this is that their membership policies have been tailored to cover the underlying fixed costs faced by the organization. In such organizations the policy generally is to require that the member opt out of the membership by communicating that intention in some fashion to the organization, rather than simply by stopping payment.
Currently on Wild Apricot if a member does not pay an invoice the system will not issue a new invoice for the next period. For an organization operating on communicated opt out policy this adds workload to the administrators; in order to generate new invoices an administrator has to renew each membership and issue the new invoice manually.

This proposal is to allow memberships to continue to be renewed and have invoices generated, even if the invoices for previous terms have not been paid. Within each membership level this would be an option that could be toggled on or off and it would have a period count for how many periods of unpaid invoices would be generated before the membership is tagged as suspended or lapsed.

As a developing a web store is under consideration, some consideration should be given to adding this proposed functionality to renewable services purchased through the store as well.

When a password is generated by the application, it seems quite secure. However, when people change their passwords, they usually don't make them as secure as they should be. Is there a way to reject a new password if it isn't secure? Or provide a "meter" that shows just how secure their new password really is so that they can reevaluate their choice? I know of some Javascript coding for this purpose (http://javascript.internet.com/passwords ), but I'm not sure if it's possible to use any of it in a CMS environment like yours.

Thank you for your attention!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
scottishlass
"You can't! It's impossible! I'm far too busy, so ask me now before I can become sane." - Edna "E" Mode