Nothing to comment so far, this is in the wishlist. As soon as we take it into works, we will post an update here.
Everything we're working on now and our nearest plans are presented on our Roadmap
Thanks for the comment. I'll take this into consideration when we are at the design stage - but this is still some time ahead.
Hi skipat - sorry for a late reply!
Is it enough to send e-mail to all event attendees (similar to reminder) or you need a way to select specific group within attendees? If we are talking about specific group within attendees, do you have any idea how would you define such a group?
We have redesigned email settings and extended subscription options for event announcements and email blasts as well. See details in presentation: https://docs.google.com/presentation/d/1bj4iE_bnw_mhLM2u5KMoH6WTCh4n0oPZkDXdB2folt4/pub?start=false&loop=false&delayms=3000
(Walt - thanks)
Robin - if something is in wishlist, then it's just waiting its turn to get attention from a product management team (me and smoother folks). So far, this has been postponed; no further details that I can provide, including forecasts.
Re "post a WA response within say a week", "For all open wishes – post a status update say every month or 3 weeks". Personally, I see no point in saying same thing over and over again - "this is not in our plans and I have details on future plans". As soon as something gets into analysis, we change status in "Work in progress" and this is the biggest notification we can make.
We're monitoring all the comments for all threads, but not always comment back. Most of comments just add more details into existing items and this helps us with prioritization for the future. Basically, more votes - higher chances for it to be prioritized, but this is not promised, as we have internal business plans as well and a lot of background activities that require resources.
Frankly, I believe with the number of overall suggestions on the wishlist, we're doing pretty good: we collect feedback, we make reasonable progress with it, we communicate. Can be better, I agree, but overall I feel quite good on how we manage the forum here.
This is not yet something we’re looking into.
Sorry, Lucy, no ETA yet. This was in the roadmap, but things have changed. This still in our short list, but I cannot promise dates.
1 and 2 is in the solution design we prepared, #3 is not going to be covered here for now.
I understand your frustration, but we have a limited number of resources and majority of them are focused now on the next 5.0 release - see http://www.wildapricot.com/blogs/newsblog/2013/08/28/wild-apricot-software-news-august-2013
Just a typo - I meant "in our queue" - which means we are aware of this but it's not in development yet.
This is still in our queue and no chance it fits in 2011
Elise, if your member directory is set up to be available only to members, then it is protected from spam.
No in development plans for now
Unfortunately this is not going to fit into 2011
Just to clarify: are you talking about self-service account cancellation feature as described in this help article - http://gethelp.wildapricot.com/en/articles/53 ?
Good idea, thanks for sharing. Is anyone else interested in this kind of enhancement?
Gerald, I hear you on this one. The problem is that our priorities and roadmap is already compiled and being worked on, we cannot really add something into next release.
On a positive side, our events development team is monitoring comments like this ones and if we believe that we have to change our current priorities, we will.
Liza, we understand the importance of this feature and I totally agree that it is very useful for word of mouth scenarios. Unfortunately, it is not in our nearest plans. We will update this post as soon as we start working in it.
I'm sorry to hear this, Scott - but it is what it is. Current system does work for someone, but I agree it is not the best and very inconvenient. We're listening and currently focusing on highly requested suggestions, but this one is still not in focus.AdminApricot Kernel (Product Manager, Wild Apricot) supported this idea ·
We do read, but this is not something we're working on right now. As soon as there is something new to share, we will post it here right away.
Can registration types with code help?
I can answer on behalf of her - no, unfortunately. It's almost impossible to guess actual timeline for any feature as it depends on too many other things. We used to try and almost always missed it do we decided not to do this anymore.
Not in 2013, sorry - but we are currently performing analysis and design.
Again, why not creating a single registration option (with reduced price) that requires code to use (this is possible to do in WA)? You can email the code to 500 people with instructions to use specific registration option and enter the code during registration.
Sorry, no plans yet. Why hidden registration types do not work for you? Or you want to suggest registration without actually showing any price until code is entered?
That makes sense, thank you for more details. What if instead of having 3 registration types for 1, 2 or 3 day rates you create it as "extra-cost" with 3 radiooptions? This would reduce total number of reg types to 4.
And I also think if we make a change in the system and allow to have "extra-cost" value to be negative, can it work as discount? In your case there could be additional "extra-cost" checkbox like "I'm student" which gives a certain amount of discount.
I would be glad to hear your comments.
I believe that this particular situation can be resolved by just creating a separate registration type on event with reduced price. No need in special discount coupons.
Scott, thanks for sharing and was nice meeting you at the PersoniFest!
Thanks for mentioning it here - we already have this comment in out internal database of ideas but not here.
Ho Donna, there have been no progress on this particular request and it's not in our radar so far and can make no promises on dates (as with any other feature).
For now, we simply count how many people commented in a specific wishlist thread. The more authors a thread has, they higher is its priority.
Thanks for sharing the details. This is still in queue, but when we are ready to proceed with it, we will be using your information in our analysis.
No, not done yet - this is why it's still in Wishlist forum.
Thanks for your comments, Nick, but you'll have to make your decision on what Wild Apricot currently does, not what it may suggest in future. We cannot promise any timeline for any new feature, it depends on too many conditions and missed our plans many times, so you cannot rely on that in your decision making.
Can you please provide more details? For example, how would it work in your particular organization. This would help us in our analysis.
Not working, that’s correct.
Jenni, I understand it sees unfair and your expectation were different. So were ours, but situation changed and we had to adjust our plans.
As of now, we do not have plans to work on this in 2018.
That's because there have been no progress so far.
Moved your reply to proper thread - it's more related here.
Not earlier than we release new CMS which is going to be a base for new modules.
Look nice, thanks for sharing!
Robin, let me answer as a Product Manager of Wild Apricot.
First of all,
thank you for being active contributor into Wishlist forum. I can see that you have supported over 100 ideas for several last years. I (and all of us in Wild Apricot) appreciate feedback form customers as this helps us in further product planning, analysis and design.
I understand your position. Everyone wants (including me) to have their ideas implanted as fast as possible, not after several years. I wish we can do this, but goes to the next point.
Wishlist forum has over 2000 open ideas in the Wishlist forum (and over 30K users) and this particular one has (only) 25 votes. Why I say "only"? We have about 200 other ideas with more votes than this particular one. We need to prioritize somehow. Number of votes is on of the key metrics in the prioritization - but not the only one, see next point.
Wishlist is a great source of customer feedback, but this is not the only source of our product prioritization. We have our own business plans (e.g. business growth), other feedback channels (e.g. Support), security requirements (e.g. PCI DSS, GDPR), infrastructure works (hosting, code deployments, performance), decreasing tech debt (refactoring of code) and so on. All these requires some kind of balance and resource planning. We are paying attention to Wishlist and user votes contribute a lot into prioritization, but not just it.
I looked into suggestions that you voted for over time and I can see that we have closed a number of them over time - which means we are working on it. For example:
- Prioritize Test Emails Ahead of "Final" Email Blasts
- Allow secondary/alternate emails for members
- Restricted access to documents and images (member only files)
- Registrant to view and change his event registrations
- RSVP - Simplified event registration
- Generating membership cards and certificates
Some more are in progress right now:
- Membership Trends Reporting
- Uploading documents and photos in forum and blog posts
- Mapping location of members
Altogether, last year we closed about 1500 of votes on the wishlist (mostly top voted requests). We're paying attention to the forum and making progress over it.
we do not share dates on purpose. Long time ago we were promising some releases dates but our expectations were always breaking. Situation changes all the time - people come and go, development can stuck at some unforeseen issues, a feature takes longer than expected and we see other opportunities. There is a lot of operational hidden activities that influence the end results that we decided not to promise at all.
My (our) position is simple: Wild Apricot is what it is now and it provides what it provides. We are committed to improve it over time, but this is a bonus, an extra thing. We won't be promising any dates and won't commit to anything. Instead, we openly share where we are and if we started working on something, we change status as "Work in progress" and it tells the world that at some point we may release it. "May" because situation can change and it can go back to backlog (postponed).
So, in short, this is not something we're going to have in 2018.
Robin, I do no want to seem rude and forgive me if I sound like one. As I said, I appreciate your active contribution and we do have progress over ideas that you voted for. But product prioritization is a sophisticated thing and we cannot give any promises.
Sorry, we have no alternative solutions and this is not in our immediate plans so far, not for this year for sure.
You can pay for 2 years with 15% discount starting form after April 3rd.
We're not planning to change our pricing model soon, but I'll keep the requests here so other people can comment as well.
In the latest update 1.3.1 profile screen was made a default screen after login. We understand that it is not a complete solution for the problem, however we hope it will be helpful.
Making custom branding on App Store level is going to be a nightmare for Wild Apricot. It means that each app for each organization has to be published separately (uploaded, reviewed by App Store staff, enabled by WA). With our number of organization and number of employees, not worth of investments - until we charge some extra for it.
Branding inside the app, though, makes total sense for me and can be quite easily done.
Because we have other things to prioritize, with more votes on them.
Would having a backup without possibility to restore it be interesting? Because importing a backup backup is much harder to implement.
Did you try to contact our support? We could have helped you to restore your content.
Re timeline: we were focusing on something else.
Sorry to hear about your accident. No, nothing changed in version 5 and we're not working on backup feature right now. See this thread about our plans and current progress - http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8827717-roadmap-2015-plans-releases-expected-dates
In this long discussion topic we've discussing what specifically people need from backup feature. Is it just
a) having a way to somehow download all the information in order to keep some copy on our own servers, but without restoring ability
b) or is it also about restoring, so you're not just backing up, but can restore from it too.
The difference is very big from implementation point of view. Doing A is much faster and easier, but has no real purpose except keep data on our computers and being able to manually open files and copy/paste data.
Option B is much more time consuming for us to design and develop.
I'll keep this in mind - we will update our procedures against aliens invasion (last time we hardly managed)
Does it have any benefit, if there is only backup option (more like export - images, web content, etc.), but no import / restore back? The problem is that to have both is quite a substantial chunk of work and it's not clear yet when we're going to do something about this.
We continue our development. Here is what was going on in the last month:
We’ve finished the Event details screen:
Users will see the main information about an event here as well as add it to their calendar.
There is a registration types list also. Let’s pretend we scrolled down the previous screen a bit:
Now we can see general info about all registration types. We also can register on it or understand why we can’t do it.
Note the “View all sessions” button on the first picture? It appears if an event has multiple sessions and shows a separate screen with more details:
Our next step will be the “registration on event” process.
PS: Just want to remind you about our beta version we created a while ago:
Feel free to check it and leave any feedback you will have. We really appreciate it.
We’re going to start working on it soon.
No updates so far.
No immediate plans so far.
See http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8827717-roadmap-2015-plans-releases-expected-dates for our current up to date status.
Yes, we're aware of the API, thanks. We will definitely be looking this (when we can)
Lori, I missed that you were speaking initially about QB Online, that explains everything - it does not support IIF files importing. Thanks for sharing your comments.
Lori, what kind of integration you are expecting to have? What are your typical scenarios / tasks that you want to automate? More details here will help us in future with proper analysis of the possible solution.
Sorry, this forum is not about WA webinars
I'm really sorry, but I cannot understand what you're specifically asking for. Integration between Wild Apricot and external system?
I opened the post for commenting - may be some other developers will be willing to help and share the experience.
Sorry, I cannot help with instructions on now to setup streaming to members only.
Randall, thanks for your very elaborated thought on this matter. As of now, we have no plans to change our Web Content module that dramatically - this is going to be quite a big business enterprise. I'll share this with our CMS dev team so we keep thinking on how to improve and simplify our CMS, but I do not expect anything big to come our of this.
No, this is not in our plans, thanks for sharing your idea. Why do you think we should have it? Would be glad to get some details on the idea.
I'm sorry to hear that. Unfortunately, this not in our nearest plans as of now.
Can you please look into http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8827180-event-manager-for-specific-events-only-with-limite ? Is it a better way of doing it after all?
I agree. We just did very first step in this direction back in 4.4, but it was not enough even close. Current thread is to make a proper support of limited event managers.
The thread you mentioned we considered done when we released version 4.4 http://help.wildapricot.com/display/DOC/Release+4.4 and introduced Event organizer http://help.wildapricot.com/display/DOC/Event+emails?from=6QQaAw#Eventemails-Eventorganizer functionality with corresponding email routing ability.
You mean that even if they want, they should not be allowed to access any other event, except their own?
In other words, you want different people to be responsible for different events without ability to change other events, right?
We made some moves into this area - see http://forums.wildapricot.com/forums/308920-archive/suggestions/8831335-event-specific-administrators-10260 - but this was very first step.
What you are speaking about, is evolution of this into more organized and automated forkflow. We've had comments about that and we have this in our design queue, but there is no timeline for that.
Thanks for sharing your ideas!