Patrick Keogh
My feedback
6 results found
-
200 votes
-
182 votes
An error occurred while saving the comment -
4 votes
An error occurred while saving the comment I agree that the Event Manager permissions in the app need to be more fine-grained.
Right now, someone we have working on our front desk doing event check-in using the phone app needs to be an admin at least for the Event category. All we want that person to be able to do is check-in, not create or modify events and so on. The model that is used for Website admins would work.The Help File for the Admin App lists the Event capabilities as:
- add, modify, or delete an event, add or check in event attendees, add or modify event registration, delete an event registration, manage event waitlists.
This would be quite adequate as the sub-categories! -
49 votes
An error occurred while saving the comment The use case of having content go both to a blog and to an email blast must be pretty common out there and the current cut-and-paste workaround is not suitable for many users.
A bit astonished that after nine years nothing has been done to advance this!
-
6 votes
An error occurred while saving the comment I fully support this requirement.
A large percentage of clubs and societies have a process for election to a management committee which requires a member to nominate and be seconded by one or more other members.
The current answer appears to be "use Make", which is fine, but given how many customers would use this, how about WildApricot better document how to use this specific use case?
The workflow needs to be:
1. Member goes to a page on the web site where there is a form with (at a minimum) the position they are nominating for and the name (hopefully a lookup from Members) of a seconder.
2. After submission the seconder receives an email with the completed nomination form and can click on "Support" or "Not Support".
3. After this approval step it goes to a specified admin (don't care how) as a completed nomination.Just because I believe this is possible in Make does not mean I can see how to do it!
-
247 votes
An error occurred while saving the comment We need reporting of user logins.
High level broken down into categories like last day, last week, last month, last year, longer, never.Then the ability to drill down to find those who are not logging in etc.
We use bundles for family memberships. I expect that this is a fairly common use case. Right now it is not easy for a bundle member or administrator to register for an event for some or all bundle members.
For a ticket type which is only accessible to bundle members could we please just have a simple interface which presents bundle member names and the administrator just ticks the boxes for those attending?
Right now the only way I know of to accomplish this is time consuming, error prone and counterintuitive. I attach the "how to" that I wrote for our members but it is clear to me that they should not have to go through this!