Dmitry Buterin
My feedback
274 results found
-
10 votes
An error occurred while saving the comment An error occurred while saving the comment Good point Paul and we will be looking into this.
An error occurred while saving the comment For now the workaround is:
Set member status to Pending-New first, then save, edit again and set to Active - this should send the activation email.
-
20 votes
An error occurred while saving the comment I think technically this is very similar problem to what is discussed at http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8825569-affiliate-program-integration-2986
-
61 votes
An error occurred while saving the comment Hi Nancy, a feature that's already included in version 5 is bulk-archiving current selection. So the big question is - can you run an advanced search of some kind that would you give you a list of all people to be archived? Sounds like this should be possible - then your work will be much simplified when we release 5.0
An error occurred while saving the comment We are actively looking for examples of specific bulk update operations .
An error occurred while saving the comment We had a request about bulk-delete members - see http://forums.wildapricot.com/forums/308920-archive/suggestions/8833459-bulk-archive-or-delete-contacts-and-members-2811 I will merge your post into that thread as it makes more sense from a broader perspective.
You have listed the following possible bulk operations:
- deleting contacts
- archiving contacts
- changing renewal dates
- changing group participation
I would appreciate ideas from others as well.
BTW, for now one way to do this is via export/import (except for deleting)
An error occurred while saving the comment Whatever warnings we give, If somebody ends up erasing important member data, they will beg us to restore their data from backup - which is a very time-consuming operation (our backups are for server failures so easy to restore all data but not just member records just for one organization). So we currently think that the only way to go about this is if we implement full undo - which is not easy.
An error occurred while saving the comment Understood - and in-system bulk changes is one of the things in our plans. Though we have to design it very carefully as it has huge potential for accidental screw-ups. (and 'Undo' is not an easy option when we are talking about hundreds or thousands of records updated)
-
31 votes
Evgeny Zaritovskiy
responded
Updated title to reflect that it’s not just about levels copying – which is about adding new levels, but also about copying of (some) settings from one level to some or all others
An error occurred while saving the comment Regarding emails - our plan is to create a library of template emails and then different levels would be able to use the same template if desired.
What other configuration parameters would be different/same between levels? (We are trying to anlayze if copying levels is the best way to go)
-
77 votes
An error occurred while saving the comment Password is now asked twice on all forms.
An error occurred while saving the comment We will monitor feedback on this and prioritize accordingly. For now, we have quite a few items which have been outstanding for long time and seem to have more feedback than this particular issue. I do not expect us to be able to get to this for at least 6 months, probably more, sorry.
An error occurred while saving the comment Your comment is appreciated and well taken.
This item is not yet on our roadmap, sorry we have to deal with a number of other things first.
An error occurred while saving the comment I will move this to wishlist.
An error occurred while saving the comment I agree - I do that too (and I think most people do). So having two fields has very limited benefit in my mind.
-
366 votesEvgeny Zaritovskiy
responded
I merged another very similar thread into this one, they should be solved together – the registration to multiple events should be simple and fast if possible. There are a number of suggestions in comments on how to achieve this.
An error occurred while saving the comment Luchia,
Thanks for bringing this up. I understand your point and it sounds to me that the long-term solution for this would be to allow selecting registration type for each guest (and for admins to limit which ones are available for guests).
See this thread http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8826058-allow-to-select-registration-type-for-guests-7910
Would you agree? If so, I will merge this post into existing thread.
An error occurred while saving the comment Thanks for your comment, I will merge it with a related thread.
An error occurred while saving the comment Kim,
Now that we have the ability to register multiple people in one transaction, it sounds that the only thing is missing from what you described is ability to select different registration types for each registrant, correct? (currently all guests would have to use the same registration type)
An error occurred while saving the comment In version 3.3 we are releasing the ability to register multiple people in one transaction. I think it addresses the original request to a large degree. The initial suggestion is still interesting though.
An error occurred while saving the comment Appreciate the details - this is very useful in our analysis.
Just to set expectations - unfortunately I do not expect this to go into development for a while. It's a complex change which needs careful analysis and design and there are many items in the queue which are more commonly requested and thus are prioritized higher.
An error occurred while saving the comment Joe,
thanks for posting those additional separate requests as I suggested. However so far they had no additional responses from other clients. So I will merge them into this issue and we will keep tracking interest specifically in team registrations functionality.
An error occurred while saving the comment I would appreciate input from others who might have use for something like this. Please post your comments here.
An error occurred while saving the comment Joe, I appreciate the feedback. In our work on multiple guest registrations we have reviewed dozens request we have received of the last 3 years and tried to design the simplest and most common solution to meet the needs of as many people as possible.
So we will monitor further feedback on this and prioritize accordingly. I would also suggest posting some specific enhancements in separate threads - they might get more votes/comments in this way, for example create a separate thread about limiting the number of guests.
An error occurred while saving the comment We do now have the ability for people to register to several events and then pay once for all of them. Does this meet your needs?
An error occurred while saving the comment In our next version 3.3 it will be possible to register multiple people for the same event.
However one transaction to handle registrations to several events is a whole separate issue.
I would appreciate input from everyone.
-
10 votes
An error occurred while saving the comment Let's focus this thread specifically on the logout button for widgets.
I am not sure what you mean re "http://www.thefreedictionary.com/muscular" - can you please email support with detailed example?
-
28 votes
An error occurred while saving the comment Normally embedding videos should be quite straightforward, see http://help.wildapricot.com/display/DOC/Adding+Video+clips
I would appreciate input from others on this, i.e.:
- what aspects of adding videos are hard/cumbersome
- what are the common services you use for hosting video
-
22 votes
An error occurred while saving the comment Larry - thank you very much for these details, this is great for our product design analysis.
-
53 votes
We have started analysis for this issue, and it seems that key problem is how Wild Apricot handles level changes close to renewal date. The system is currently designed to collect the full new level amount and set renewal date according to new level renewal policy. All prepaid amounts for old levels are disposed. Moreover, since no prorating occurs, the new level might be effective only for a few days.
As a first step, we suggest to redesign how level change is working and add prorating there:
- Level would be changed immediately, as now
- Remaining portion of old membership level payment will be applied to new level
- For new levels with specific renewal date (e.g. annual levels with renewals Jan 1st) apply the pro-rating settings for new applications:
- Allow member to pay only a pro-rated amount of the new level fee (e.g. six months before renewal…An error occurred while saving the comment Thanks for the detailed description. What we have now is that WA does not really deal well with level changes which happen at the same time as renewals - it assumes they should be handled separately. This is definitely something we would tackle - it's on our roadmap.
An error occurred while saving the comment Hi Erica, thanks for posting about this. We have been thinking about this for some time.
I would appreciate comments from everyone, e.g.:
- if you have different renewals dates for these two levels, how do you deal with that
- how do you typically round remaining balance (by day, by month etc.)
An error occurred while saving the comment I am surprised nobody else commented on this yet - it does sound like a common need.
Might be the thread title, I have edited it to make it more self-explanatory.
We currently plan to implement pro-rating of membership fee for new memberships in version 3.4.
Once that is done, it should become a good foundation to rationalize the level upgrade pro-ratement calculations.
In the meantime I would appreciate thoughts and ideas from others on this thread,
An error occurred while saving the comment It sounds like actual upgrade of level would be deferred until the expiry of the current membership term.
We have not considred this - good to know. We assumed that user would want to be at level b right now - not from the renewal date.
Very interested to get feedback from others.
-
13 votes
An error occurred while saving the comment Appreciate the detailed write-up - we will take a look at this but I am afraid we will not be able to allocate any resources to this particular task anyway for a while.
An error occurred while saving the comment I will move your post to Wishlist so that we can get feedback from other users. I know that different forums use different terms so I would appreciate feedback from others on their opinions for best terms.
An error occurred while saving the comment I would appreciate feedback on this from others
-
31 votes
An error occurred while saving the comment Anyone else who would want this?
Please comment here.
-
9 votes
An error occurred while saving the comment There is currently no way to set this up in Wild Apricot.
Sounds like a useful suggestion.
I would appreciate input and examples from other users.
An error occurred while saving the comment @Sabobird - you are absolutely right.
An error occurred while saving the comment @HippoTraining: There is a number of emails for new members, setup in each level. Can you elaborate how you comments maps to what we already have?
An error occurred while saving the comment This is done in each membership level.
See https://help.wildapricot.com/display/DOC/Membership+application+form
-
43 votes
An error occurred while saving the comment Christopher,
Your point is well taken.
It is on our roadmap for 2010 to provide ability to finely select event announcement recipients - including by groups. See http://forums.wildapricot.com/forums/308920-archive/suggestions/8833867-ability-to-select-recipients-for-event-announcemen
An error occurred while saving the comment Thanks for weighing in!
As we are still collecting feedback on this, it has not been moved to the roadmap yet so the timeline is not firmed yet.
An error occurred while saving the comment Chair - would it be different from moderator? What powers would he/she have?
-
22 votes
An error occurred while saving the comment Actually identfying misuse is much harder. Google might be showing several unique visitors for many different reasons, e.g.:
- same person logged in from home/office
- same person using different browsers
- same person using some kind of cookie-blocking
- or different people using the same login.
We can not reliably distinguish these cases - neither can Google or anybody else.
An error occurred while saving the comment I would like to hear more from others - how important this issue is, what is desirable etc.
An error occurred while saving the comment I guess you are talking about tracking and limiting access by IP address. This is not really feasible due to NAT routers, dynamic IPs etc.
What I think should be doable is restricting access so that only one person can be logged in under the same member ID at any one time. What do you think of this?
An error occurred while saving the comment Good point, makes sense.
Let's see how many other clients consider this important..
In any case, there is no way we can add this in the near future - too much other stuff already in the pipeline.
-
146 votesEvgeny Zaritovskiy
responded
Old design proposal, not working on it yet and can be changed if we start working on it – https://drive.google.com/file/d/0B0f9kMyQqlBsZ3FQOWRiMERRNkk/view?usp=sharing
An error occurred while saving the comment John,
Thanks for posting.
The reason we are reluctant to add Boolean search is because for non-technical people (majority of our users) it might make things confusing and unnecessarily complicated. I would appreciate examples of searches you need to run but currently can't in WA so that we can look at possible solutions.
About access to all fields - please email us at support @wildapricot.com with details
About exporting subset of fields - understood, there is a separate thread on that.
An error occurred while saving the comment Paul, as you can see, this thread did not have any comments before yours so for now we are not really planning it in our roadmap - seems to be less important to our users than dozens of other things. So we will wait to hear more input here.
-
12 votes
An error occurred while saving the comment Thanks Rob, appreciate your input, good thoughts.
FYI - we do have a way right now to 'clone' an account - which we occasionally do on requests from clients and consultants. The logic is a bit arcane (what it copies and what it does not copy) so we plan to revise it in the future, but I think it can be a close approximation for what you have described above.
An error occurred while saving the comment Thanks. Individual transaction deletion should be available in our next version 3.5 in August.
An error occurred while saving the comment After analyzing this and also reviewing the changes in upcoming version 3.5 (e.g. payment transaction log is replaced with several other tables; it will be possible to delete individual financial transactions etc.), we have realized that we need to look at this broader.
Generally speaking, once people finish evaluating a trial account and upgrade, they frequently want to delete all the test data. So we want to figure what are the possible scenarios, e.g.:
- Delete pretty much all object in the trial account
( exceptions: keep web pages, membership levels, custom fields, all settings, discount coupons, custom report layouts, saved searches, uploaded files)
- Some kind of selective delete:
-- contacts/member/donor records
-- events
-- event registrations
-- donations
-- financial transactions (invoices/payments)
-- sent emails/email drafts
I would appreciate comments and insight from everyone
An error occurred while saving the comment This has not been addressed yet.
An error occurred while saving the comment Ian,
The reason we have not been able to address this before is due to two key reasons:
- very complex and very fragile data architecture behind (basically can't ensure data consistency if financial transactions are deleted)
- desire to ensure that our clients have a full audit log of transactions (which by definition should not be clearable)
In our next version 3.5 we are rearchitecting the financial management side and will provide the ability to delete individual transactions.
I have split out your post into a new thread as you have good suggestions about Clearing functions we should provide.
So if you have lots of test data and can't live with it until next update (~end of July), you can open a new clean account and contact our tech support to use instead of current one.
An error occurred while saving the comment Sorry, there is no way to do it now. This makes good sense so I will move the thread to Wishlist forum.
-
21 votes
An error occurred while saving the comment URL of member profile is now available as a macro - added in 2.37 update.
An error occurred while saving the comment It is doable - just a matter of priorities. Let's see what other say to help us prioritize it.
An error occurred while saving the comment This sounds quite doable if you can find a good Javascript guy - assembling links on the fly is not a big deal. We had a partner who was showing externally stored member pictures in exactly this way.
An error occurred while saving the comment I am happy it works now for you, but we did not change anything.
I usually run IE and FF myself in these cases to see both public and admin view - since they do not share cookies.
-
15 votes
An error occurred while saving the comment Good point. Do you see this as a global or per-forum setting?
-
22 votes
An error occurred while saving the comment We would appreciate further input on this from everyone. Obviously it is hard to impossible to ensure accessibility for all pages/functions in one go so we would appreciate more details - which of Wild Apricot specific pages/functions currently are the biggest bottlenecks in your organization accessibility-wise?
An error occurred while saving the comment Thanks for your input. This makes perfect sense and we will consider this in our development plan (though it will be a while - quite a bit of other stuff in the pipeline already)
There have been a number of changes since this thread was started.
As of now - version 4.1 - members are automatically added in 'Pending - new' status and member entry screen is now only one page.
So the focus of this thread has been changed - to focus on stop silent sending of any emails on admin actions - while giving admins a way to send them manually if needed.