Jeniffer, integration of 2 different platform via frames will never work smooth comparing to a single platform.
Thanks for sharing, Alex. This is something we keep in mind but not yet focusing on due to a number of internal reasons.
All of them?
Eric, I merged your requests with existing one. This is not in the works as of now and I have no expectations set so far. As soon as we start working on it, we will comment here and your and others will be automatically notified via email.
Jennifer, the answer is no - this is why it is still in the wishlist.
Our roadmap is here: http://help.wildapricot.com/display/DOC/Product+roadmap
Thanks for comments.
I think that having multiple payment providers should be implemented only when we implement ability to customize payment methods - see http://forums.wildapricot.com/forums/308920-archive/suggestions/8833330-customize-payment-methods-labels-and-descriptions
My idea is that you need a way to setup multiple payment methods in first and where you allow to use each one (or several simultaneously). Having several payment providers is an extension to this customization - like one of payment methods is connected to a different provider.
Can you elaborate please? Some examples as well?
Nothing special, just sitting here and collecting votes. No plans so far to implement it.
Could you elaborate this please?
Merged, thanks Alex
How would you change it to make it clear?
Can you please provide more details?
Hi, thanks for sharing. Why is it so important?
Hi Judi, thanks for the feedback! What kind of reports are you talking about?
Hi K Gane, thanks for the feedback. This particular request is not in our priority list and there are no expectations so far. The Wishlist forum is where we give our customers opportunity to voice their requests, we it does not mean that we're implementing all the requests right away. Currently, we're working on other things - you can see them if you filter the Wishlist by "Work in progress" status.
Murray, why is integration with external mailing systems "a must"?
Matt - thanks for sharing.
I actually agree with you in general and we will get there. I still think that there for quite a lot of organization internal email system is good enough and easy to use, but for others integration with MailChimp and similar systems will work much better.
Wild Apricot does track emails opening and links clicking - http://help.wildapricot.com/display/DOC/Tracking+emails
@ stanleyfelix - see http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8825584-generating-membership-cards-and-certificates-6344 thread on badges
On the very next release 4.3 we're adding ability to manage bounces. The next step we plan (as Dmitri mentioned earlier) is to have pre-built email template to select from when blasting newsletter.
Talking about integration with constant contact (or other systems) - this is not something in our nearest plans and again as Dmitri mentioned we are more dedicated to evolving WA tools instead.
Not soon, you're right :(
I think that ideally we need to create our own API to get an access to WA data (i.e. member records, event attendees, etc.). Then based on that third-party companies can creates services to sync data between different services - like WA <-> mailchimp, WA <-> constant contact.
This depends on privacy settings of member fields - when name field is accessible, it shows the name.
Can you elaborate what is important specifically? I mean, what do you ideally want to have. There are different ideas/problems being discussed here, I just want to make sure.
Thanks for commenting - but do not expect any change here soon, sorry. I will continue monitoring this thread to adjust the importance of the request.
But the question is - why? You do not want to reveal real name but want to substitute it with some profile name (nickname?). What is profile name in this case? Can you give us some examples of such profile names?
Unfortunately, this is not possible now.
Any comments from other on this are welcome.
14 votesFrank responded
Very interested. I would love to know how many organizations are considering something similar.
Nope, we're focusing on top voted items now. You can check what we're busy with if you filter by status work in progress.
This is a great suggestion! Thanks for posting it.
Walt, this was not done on purpose. Just on of things to work on in future (but not this year).
No plans yet, Liz. Not soon for sure.
Well, easy or hard, we cannot do it right now - it has to go into our product roadmap in first.
For now, I separated your comment into a dedicated thread and will keep it here. Wishlist is a place for us to collect new features and changes requests, we use it when we plan system updates.
Would it solve your problem, if we add an option for common field setup to make a field "Read only", same as we have now for membership fields? Rating itself can be a simple text field in this case, edited by admin.
Could you please elaborate your case?
Nice workaround, Gary! (though still a workaround and we need to get it solved someday)
Sorry, I'm not are I understand. Can you please elaborate? What is missing in current flow?
Charles, this topic is not about us, Wild Apricot, but about our customers and their members. So the second part of your comment makes total sense to me.
It does force to pay full amount
No, we're not working on it yet. See our Roadmap - http://help.wildapricot.com/display/DOC/Product+roadmap
We hear you, but we've been putting all our efforts into version 5 (to be release soon). Now, we're slowly getting into other requests and the key focus for us is to close as many long outstanding posts as we can. This one is among them, but we haven't had any progress on analysis yet.
Sorry to say that, but no. But we have not forgotten about this, just had no resources to get to this yet.
Sorry for the late update.
The first step was finished and emails can now be carbon copied to contact’s alternative emails. To do so the contact fields which store the alternative emails must be explicitly marked on the email setting page.
Unsubscribing will unsubscribe all alternative emails simultaneously because they all belong to the very same account. The person clicking “unsubscribe” is warned about this on the unsubscribe page.
For now we paused the development of this feature. but not for good. :) So I’m changing this wish status back to “collecting comments”.
Thank you everyone for a valuable feedback.Evgeny Zaritovskiy supported this idea ·
Working on it.
"This is becoming a seriously big issue ... Please, please, please, move this up the list!"
The most recent update is that this particular idea is a part of 2017 focus on Email Development team in Wild Apricot. As soon as they have some progress here, they will share it.
I'm very sorry this this is a big issue and we haven't had any progress over it.
This is not intentional, priorities just change all the time. We now never promise any release date. When we start working on something, we change it to "Work in progress".
well, it's not a kickstarter :)
this has a good number of votes and it is in out top list.
No estimation though.
We will update the status to "Work in progress" when we start working on it. Nothing more I can add now, sorry.
It is not very hard, but it is not a couple of clicks either.
Most probably, this is not something we will change soon as we're focusing right now on top voted ideas.
Sorry, we do not provide estimates.
Also unfortunately with the system of that scale (9000+ accounts, 6M+ contacts) there is not easy/simple change, everything requires thorough testing and resources. Our product roadmap is here http://help.wildapricot.com/display/DOC/Product+roadmap
Oh, Susan, as soon as you commented or voted for a feature in the wishlist, you will be automatically notified about any change related to the topic.
I see... Well, as soon as we are close to development of this, we will get this into consideration. Thanks for sharing, Walt, this is exactly why we want to share our design thoughts in first place!
Hm, the idea about having alternative email is to not have 2 contacts in database, right? So, you have 1 contact (e.g. for a husband) and you put alternative email into his contact record (wife's). The only reason you do this is so WA can automatically notifies BOTH emails when something happens or when admin sends emails, etc. Otherwise, what is the point of keeping spouse's email at all in contact records?
Unfortunately, we are not able to fit it into our original schedule in Dec 2015, and it also won't fit into our Jan 2016 release. I do not have information after this date, so for now I cannot promise any release date. I will update everyone as soon as I have more information.
Please, accept my and development team apologies for this.
We're balancing a lot of things - see our Roadmap at http://help.wildapricot.com/display/DOC/Product+roadmap
This issue is there (but we will start from 1 alternative email)
Thanks for sharing, but I have no suggestions for you to workaround that.
This is something we want to address as a part of another thread - http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8825986-family-child-memberships-8131 - focused on family memberships. There we'll be analyzing all scenarios and finding best solutions.
What kind of information tied to primary contact are you talking about specifically? Could you give some examples of contacts with some example data (emails, etc.) that you're trying to keep? I cannot understand your contact's connection map you're trying to implement.
But in general I can comment that current contact database model basically consider each contacts a separate record with its own set of data and when you use use search, it uses data specifically from this contact data. Bundles are the only exception and allows to group contacts and show all related contacts when looking into details of specific ones. Probably, some of your problems can be resolved using bundles, but I'm not sure - need to get examples of contact details as I asked in the beginning.
Our current inclination is to have something like a single "backup" email for each contact - not multiple emails. This makes email blast scenario simpler to implement - like admin can select if he wants to force a copy to "backup" email or use only primary email. Contact could also select if he wants always to receive a copy to his backup email or use it only in special cases (like forgot password, etc).
We think that bundle scenarios (like families) should be considered in terms of bundles in general, not just emails. This means that we need to rethink and change whole bundle management and this is a different aspect of discussion - see
Sorry - no progress yet here. I'm not expecting any change here in 2011
Thank you, Jim. We have this requests in our forum already, I've merged yours here.
So far, we're have no actual plans on doing something about this, but when we do, we will comment here and you will be notified.
As soon as we have, we publish it here. So far, we have no plans yet.
Joined to existing thread - it belongs here, to custom database field validators.
I think that we need to have some kind of common validation patterns plus ability to use regular expressions. And admin (in fields management form) can choose if he want the field to be validated and choose a proper validation pattern or defined custom (regular expression). Then the system will just validate the field against the pattern.
In more ideal situation I can think of a special system page (or may just some theme override configuration file?) where admin can control validation patterns himself somehow (e.g. through regular expressions or even providing some js code) and then use them in fields customization. This approach would require advanced skills from administrator.
No update, sorry. I probably there will be no update here till the end of the year.
Thanks for sharing, Daniel. Could you elaborate what you mean by this?
This is a very elaborated suggestion, thank you very much for your time. This is quite a big project - to properly and seamlessly integrate with Meetup - and of now it is not in our immediate pipeline.
We will continue collecting feedback to see how much this functionality can be of use for our customers. The more votes we receive, the more chances that we're going to look into it closer.
Could you elaborate? Why do you need this?
Could you please share more? I'm not sure I fully understand what it is you're asking for. May be, some examples?
Why not using system field "Member since"? It adds the date of application automatically