Alex Sirota
My feedback
115 results found
-
116 votes
Concurrent membership is not something easy to implement - it would require fundamental redesign of how membership works in WA. However, I have couple of thoughts here that I wanted to hear your feedback on.
As I understand, there are 2 sides of the problem:
1. Collecting additional dues for services. E.g. Member is associate and board member, so you need to collect both dues.
- This can be addressed using our extra fields functionality. Maybe it's a bit clunky, but it should work. E.g. setup associate member as primary membership and add extra charge checkbox for being a board member.
- You can easily filter down any members you need with advances search by that extra field.
2. Setting correct permissions on website pages - here there's no workaround we could suggest, but adding permissions based on saved searches seems to feasable option.
Am I missing something? Will the…
Alex Sirota supported this idea ·
An error occurred while saving the comment -
73 votes
Dmitry Smirnov
responded
How are you going to use QR codes on membership cards? Do you expect some additional functionality in WA, which will be able to read and process these codes?
Alex Sirota supported this idea ·
An error occurred while saving the comment Alex Sirota commented
Next Friday -- you can see a way to insert a QR Code into a membership card. It's a hack but it totally works - https://www.newpathconsulting.com/2020/01/cheat-sheet-9-adding-a-qr-code-to-a-wild-apricot-membership-card.html
-
163 votes
An error occurred while saving the comment Alex Sirota commented
I just found this step by step to create newsletter archives manually. It takes 10 steps and is pretty unwieldy but it exists.
https://gethelp.wildapricot.com/en/articles/35#archiveI wonder if this could be introduced eventually into the editor by simply creating an archive of the email (rather than a template) every time it is saved. I think just about all my customers would like to have an email archive in their site. Most modern email marketing packages have an HTML view of the email so it would be really nice.
In the new email editor the HTML file saved in the Files manager will have a new URL - https://gethelp.wildapricot.com/en/articles/1693. Maybe the new email editor will have saved archived newsletters eventually.
Alex Sirota supported this idea ·
-
22 votes
An error occurred while saving the comment Alex Sirota commented
I wonder why the same tax rules are not applied to the online store ? Only the default tax rule, if it is set at all, is applied but all the other tax rules are ignored. This really is a bug in my opinion.
Alex Sirota supported this idea ·
-
11 votes
Alex Sirota shared this idea ·
-
127 votes
Alex Sirota supported this idea ·
-
60 votes
An error occurred while saving the comment Alex Sirota commented
Check out our new Wild Apricot Reports Manager -- a solution powered by Google Data Studio with full support for accessing Wild Apricot database through a powerful reporting and visualization product.
Visit www.newpathconsulting.com/warm for more details.
Alex Sirota supported this idea ·
-
2 votes
Alex Sirota shared this idea ·
-
51 votes
An error occurred while saving the comment Alex Sirota commented
Along side multiple currencies, an ability to configure a bank "account" tagged to transactions would be useful. That way if Wild Apricot Payments allowed multiple bank accounts you could record transactions to different bank accounts, in potentially different currencies.
Alex Sirota 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
Alex Sirota supported this idea ·
-
252 votes
Alex Sirota supported this idea ·
-
14 votes
Alex Sirota supported this idea ·
-
87 votes
Alex Sirota supported this idea ·
An error occurred while saving the comment Alex Sirota commented
We have been investing lots of effort to develop a third party reporting solution that works with Wild Apricot and google analytics. Check it out
Https://waxm.newpathconsulting.com/warm
-
1 vote
An error occurred while saving the comment Alex Sirota commented
Sure thing -- we have published full documentation here
Https://waxm.newpathconsulting.com/watm
Alex Sirota shared this idea ·
-
5 votes
Alex Sirota supported this idea ·
An error occurred while saving the comment Alex Sirota commented
It would be useful to add a "short description" box with a max of 200 characters to an event that can be shown as a preview and used as a macro in email instead of the full description
The event speaker(s) should also be a separate piece of data that could be featured in an email apart from the description. This would make for more marketing-friendly calls to action in an email and remove the need to include the full event description which can get long.
-
36 votes
Alex Sirota supported this idea ·
-
29 votes
An error occurred while saving the comment Alex Sirota commented
@Oleg,
Now that you are able to generate SSL certificates on the fly with Let's Encrypt, even custom domains can be SSL encrypted. This is a good step in the direction of allowing the payment process to occur under the domain of the customer, rather than a third party payments page.
Removing the need to bounce to an outside domain name with wholly different branding is a good user experience boost, and also will allow tracking of goal completion in Google Analytics.
It's a good thing, and I hope you will consider this for future improvements to optimizing the ecommerce experience in Wild Apricot.
Alex Sirota supported this idea ·
-
31 votes
An error occurred while saving the comment Alex Sirota commented
@Bryan - Why not just subscribe to uservoice and link it into your site or embed it into a Wild Apricot page. That is what this service is
uservoice.com
An error occurred while saving the comment Alex Sirota commented
I second this idea - need to be able to up and down vote comments on discussions and be able to float popular comments "higher" into the discussion tree. Sort of like this Wishlist forum actually :)
-
12 votes
An error occurred while saving the comment Alex Sirota commented
To be sure we have identified an approach that seems to work but it does require temporary downtime which is not always allowed or appropriate.
Alex Sirota shared this idea ·
-
6 votes
Alex Sirota shared this idea ·
I see several areas of architecture in the current Wild Apricot system that could be affected in a serious way that requires deliberation:
1. Access control to pages - I am active in level1 and level2.
A page has access control to level1 but NOT level2. Can I see the page because I am in level1? But I should not be able to since I am in level 2 as well. That's a conflict. What's my primary access control to this page?
2. Access control to events - see #1
3. Access control to registration types - see #1
4. Membership fields - if you have membership fields for certain levels, I guess you would "combine" all fields from the levels assigned to you. I think there may be some issues here, still in terms of the UI as you are renewing one level - do you see all your membership fields or just the ones for that level?
5. The cascade of dependencies on the API, mobile apps, pretty much every single part of the system.
I think the only really effective and reasonable approach that doesn't affect so much of the system to have a "federated" approach where you setup multiple WA sites for each chapter and have a single sign on approach that enables you to "traverse" across multiple chapters. Of course each could have multiple different levels, effectively giving a member the perception they have different levels. At least here you could sign in with 1 email and be "directed" to the site you want to access. It would be cool for the sites to be modeled after each other too. This is directly related to the multi chapter issues brought up in another thread that ended up being resolved as simply: use a separate site when you need a separate business model, payment mechanisms, levels and policies.
Use one site when all the branches are modeled in the same way. This breaks of course when you have 1 site and DO NOT want the overhead of separate sites.