wmorrison
My feedback
11 results found
-
124 votes
An error occurred while saving the comment wmorrison
supported this idea
·
-
13 votes
There is the integration available with Integromat platform, which helps to build automated workflows.
We also provide several templates for quick start, and one of them allows you to copy Wild Apricot events into google calendar. So you can share this google calendar and your members can subscribe to it.
You can try the integration by this link https://www.integromat.com/en/integration/2276-copy-wild-apricot-events-into-google-calendar
Help page: https://gethelp.wildapricot.com/en/articles/1653
Blog post with video tutorial: https://www.wildapricot.com/blogs/newsblog/2019/02/14/create-integromat-scenario
wmorrison
supported this idea
·
-
46 voteswmorrison
supported this idea
·
-
22 votes
An error occurred while saving the comment wmorrison
commented
The function would be to allow a defined membership type to join a community zoom meeting. Other membership types would not be able to.
Using the zoom registration function members with the right membership type could click on a link in the calendar to join the meeting. Others would get an upgrade message.
It would be great to figure out how the scheduling process could place the meeting information into the WA calendar.
wmorrison
supported this idea
·
-
202 voteswmorrison
supported this idea
·
-
180 votes
Evgeny Zaritovskiy
responded
Merged together several closely related by meaning ideas – so we can properly resolve them all together, in different live scenarios
wmorrison
supported this idea
·
-
225 voteswmorrison
supported this idea
·
-
275 votesEvgeny Zaritovskiy
responded
Please review results of our analysis and design:
https://docs.google.com/presentation/d/1aBh3RKOIAbC-YOkpQtRJ8kv9kH3ZlXSID7Ezl1bCAlg/pub?start=false&loop=false&delayms=3000Post your comments/ideas right here. Until we see major disapproval, this is what we will develop in one of future releases.
wmorrison
supported this idea
·
-
71 votesEvgeny Zaritovskiy
responded
Please review our current proposal: https://docs.google.com/presentation/d/123zVAgAcSLQb02vC6v8zj-6qoEAEW56cJ-3ioqv5WEc/pub?start=false&loop=false&delayms=3000
wmorrison
supported this idea
·
An error occurred while saving the comment wmorrison
commented
My community is not advanced enough to use RSS and I cannot expect members to check the site and further, the blog(s) daily.
The forums component has it right - subscribe and have a number of subscription options.
Please add this as soon as possible. As is, the blog component is not practical for the community that want assurance that posts are reaching its members.
Thx
Will Morrison
-
267 votes
Dmitry Smirnov
responded
Even though it is not a direct implementation, I hope this could be helpful:
We just launched integration with Integromat platform, which helps to build automated workflows. We also provide several templates for quick start, and one of them allows to copy google calendar events into WA events. So if you share a google calendar for events submission, then the scenario could copy submitted events into your Wild Apricot account.
You can try this integration by this link https://www.integromat.com/en/integration/2275-copy-google-calendar-into-wild-apricot-eventswmorrison
supported this idea
·
An error occurred while saving the comment wmorrison
commented
I would like to see this too. In addition, once approved the event would optionally be provisioned with a wiki page for the organizers to pull together the details.
-
170 votes
An error occurred while saving the comment wmorrison
commented
Hi,
Is there a way to see either the number of addresses and/or the actual email addresses of those subscribing to a forum?
Currently there is no way of determining the number of readers.
Thx
Will Morrison
I agree with the initial description. I would like to see the option of check out time of enabling to pay N number of billing cycles in advance. This gives the user full control, more so than re-occuring payments which can continue longer than the user intends and results in refund requests.
A second priority would be re-curring that is time bracketed.
I would add that the current state is extremely system centric and is not giving users the choice they want on the sensitive topic of payments in a modern platform. This feature has been around since the famous opt in / opt out debates twenty years ago!