Dmitry Buterin
My feedback
274 results found
-
81 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment An error occurred while saving the comment Dmitry Buterin commentedAn error occurred while saving the comment Dmitry Buterin commentedHi Robert, can you elaborate how you envision this? I am not clear how this applies to zip/address radius search.
An error occurred while saving the comment Dmitry Buterin commentedGood point Tim and good job on the map. I understand it dynamically links to the member directory, right?
An error occurred while saving the comment Dmitry Buterin commentedAbout member map - this is already possible. See
-
14 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedSorry, we do not currently have a way to name each blog post page title.
An error occurred while saving the comment Dmitry Buterin commentedWhat if we change blog post page title to post titles, would this address the issue for the most part?
-
15 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedRandy - there is no particular technical difficulty. Like all other requests on this forum it has to be prioritized based on relative commonality of a particular request.
An error occurred while saving the comment Dmitry Buterin commentedSorry, this has not been scheduled into development so there is no date.
An error occurred while saving the comment Dmitry Buterin commented@Arose - I am afraid this is not in our immediate development plan so the scenario you have described is indeed possible.
An error occurred while saving the comment Dmitry Buterin commentedSorry there is no way to do this now but you made a good case and I will merge your post to existing thread on the same subject.
An error occurred while saving the comment Dmitry Buterin commentedSo you are saying that such fields would be available for entry only on the membership application form but would not be editable by each member afterwards?
I understand the need but I wonder if there is another way to handle this. I suspect this might be confusing to users.
Would appreciate input from others.
-
49 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedThanks for your comments.
Let me ask you guys - how would you ideally deal with registration types when events are imported (one event can have multiple reg types = ticket types)?
An error occurred while saving the comment Dmitry Buterin commentedGuys, most of our users typically hold 1-2 events/month so it does not make sense for us to develop an import facility for events at this time, sorry.
I will still keep this thread on the wishlist and would appreciate comments from other users.
-
19 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedRon - this is being considered but has not been planned to a specific release.
An error occurred while saving the comment Dmitry Buterin commentedThis is a good idea and I think it deserves a separate thread- I will split it out.
-
22 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedIt's because Wild Apricot can be used with several payment providers and some of them did not allow changing the amounts once the payment starts (e.g. initial payment and recurring payment have to be the same). I can't think of a workaround unfortunately.
An error occurred while saving the comment Dmitry Buterin commentedThanks for posting on this, I hope to see comments and input from others.
-
12 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedI would really appreciate comments from others - if were to make this change, we want to ensure the suggested text is acceptable to other clients.
An error occurred while saving the comment Dmitry Buterin commentedGood point. I would appreciate comments and votes from others to help us prioritize this.
An error occurred while saving the comment Dmitry Buterin commentedThanks, this is quite helpful.
An error occurred while saving the comment Dmitry Buterin commentedCan you provide an example of how you would customize this and what screen it would apply to?
-
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
Dmitry Buterin supported this idea ·An error occurred while saving the comment Dmitry Buterin commentedUnfortunately we have to postpone this feature from our 2010 roadmap
An error occurred while saving the comment Dmitry Buterin commentedIf it is a publicly accessible blog, you can use Google Feedburner service to enable email subscriptions
-
74 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedThis is not possible now - but sounds like a useful idea.
Would appreciate input from everyone.
-
26 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedOK, got it, see those on page 3.
An error occurred while saving the comment Dmitry Buterin commentedWow, great to hear this!
Joanie, I looked at your member directory and could not immediately see any indicators about albums, what am I missing?
An error occurred while saving the comment Dmitry Buterin commentedJoanie,
The earliest it can happen is release 3.5 - around June-July (because next release 3.4 scheduled for March is already in final stages of development and we have our hands full). Whether it makes it into 3.5 or not is very much an open question now.
To do this properly requires server-side coding so our partners unfortunately can not help (somebody like Nicasio might be able to come up with some sopshisticated Javascript hacks but this is very tricky)
So for now there is really no reliable timeline on this, sorry.
An error occurred while saving the comment Dmitry Buterin commentedBob, we are hearing you and I will nudge this issue up in the queue.
An error occurred while saving the comment Dmitry Buterin commentedJoanie - this is along the lines of what we are considering - though it will be still some time before we get to this, it is not on the roadmap yet.
An error occurred while saving the comment Dmitry Buterin commentedThis is a good point. Any suggestions on how/what to show in the directory to facilitate the discovery of albums?
-
4 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedThis makes total sense. Hope to see votes and comments on this from others.
An error occurred while saving the comment Dmitry Buterin commentedSo just to reconfirm:
The issue is that when admin manually adds registrant to event, WA should clearly display/warn admin if member is any status besides Active.
Correct?
-
12 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedThese different prices are setup as registration types, correct?
In each type you can specify whether to show it or not to people who do not have access to it. -
111 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedRick, thanks for the comment.
An error occurred while saving the comment Dmitry Buterin commentedThis might also be applicable for people managing several separate chapters/groups within a single account, see http://forums.wildapricot.com/forums/308929-general-discussion-and-questions/suggestions/8822125-functionality-for-multi-chapter-organizations
I would appreciate input from others to help us flesh this out and prioritize.
-
86 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedThe timeline for version 5.1 will only be finalized after we release 5.0 - which will happen this summer.
An error occurred while saving the comment Dmitry Buterin commentedBecky - we have released many dozens of enhancements since 2009 - but you can find many others from 2009 or even before that are still in our pipeline, this is one of them.
Our main focus for the next ~6 months is to finish the CMS redesign in version 5 so we are putting everything else aside. So the earliest this will be considered is version 5.1 (and this is indeed one of the candidates for it)
An error occurred while saving the comment Dmitry Buterin commentedAnn, it's currently not possible to have different fields on different donation forms - so the best workaround is to have one 'donation purpose' field which people would select.
I suspect that if you engage a Javascript-savvy web-designer, he can come up with a hack to pre-set this field to certain value on each page - and maybe hide it altogether. Our partners can probably help, e.g. Nicasio - see http://www.wildapricot.com/partners/
An error occurred while saving the comment Dmitry Buterin commentedThere did not seem to be much demand for offline payment for donations. If this is still important for you, can you please create a new separate thread about this on the wishlist and elaborate when/why is this needed.
An error occurred while saving the comment Dmitry Buterin commentedMoving to the roadmap.
An error occurred while saving the comment Dmitry Buterin commentedWild Apricot does allow for multiple donation forms but they all use the same set of fields.
So my guess is what you need are multiple forms, with fields customizable in each form, correct?
About using different payment methods - actually I do not think it would be so hard. Can you please create a new thread on the wishlist about it?
-
5 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedI have many concerns about allowing anonymous users to create blog posts and threads - however if the primary need is to enable this for event attendees, this looks much more feasible (and the reall question becomes is to allow them to login to authenticate).
I would appreciate comments from others.
-
5 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedSorry our help page was misleading - we do not currently have it in our plans to implement tracking.
However, if this gets sufficient interest, we would definitely consider this - so I would appreciate hearing form others who need this and as much detail as possible - what/how you want to track/communicate to members.
-
239 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedInteresting, this has never come up before.
Can you elaborate how exactly are you usually using recurring payments for events? How many payments/amounts etc.
An error occurred while saving the comment Dmitry Buterin commentedThis has not been scheduled - so I would guess at least 12 months.
An error occurred while saving the comment Dmitry Buterin commentedMeagan - there is no such option for the moment. Before we consider that, we need to put some foundation in place - specifically, the ability to view/pay for invoices- which is in our design pipeline right now.
An error occurred while saving the comment Dmitry Buterin commentedGraham, what we have for membership does not really map to what is needed for events. In memberships we have a way to handle (full) regular/recurring membership dues. In events it's about collecting a total in a certain number of installments. It sounds similar on the surface but in terms of functionality and system interface, these things are not really related. So the only solution is to design and develop proper functionality for event installment payments - and we are still collecting input to understand different ways people handle that.
An error occurred while saving the comment Dmitry Buterin commented(I merged these two threads, hence the link issue)
An error occurred while saving the comment Dmitry Buterin commentedSee also this thread on installment payments:
I am thinking of merging them.
An error occurred while saving the comment Dmitry Buterin commentedChantay,
Our August release 3.5 will lay the groundwork for this but we are not doing any special enhancements for public/member interface, sorry to disappoint you.
For now the gist of the change is that admins will be able to record multiple payments to the same invoice (e.g. event registration) and track open balance. Public interface will still display full price, online payment will process full price - so installments will still only be possible with manual workaround, though it will become easier.
An error occurred while saving the comment Dmitry Buterin commentedIn our next update 3.5 (August 2010) it will be possible to record multiple payments to any invoice (including event registrations) and track open balance (vs. current implementation of paid/unpaid)
An error occurred while saving the comment Dmitry Buterin commented@skipat - sounds like a good idea. Could you post a new wishlist thread specifically about numeric fields? I have a feeling that others might find it useful for other reasons - which means we can prioritize it higher/sooner.
An error occurred while saving the comment Dmitry Buterin commentedThanks for the ideas.
This definitely sounds like a useful enhancement, though of course not a simple one as it should include things like:
- ability for people to go back to specific transactions and enter payments
- convert current pending/paid tracking to pending/partially paid/fully paid
- workflow rules
So I would appreciate additional ideas and insights from any other readers.
An error occurred while saving the comment Dmitry Buterin commentedFor me, this sounds very reasonable and necessary. So all I am saying is that I want other clients to weigh in and help us to analyze this further and prioritize against other items in our queue.
An error occurred while saving the comment Dmitry Buterin commentedThank you Peter.
I have changed the post title - I think this will make it easier for other clients to find and vote on.
Conceptually this makes total sense to me.
Technically this is a bit of a challenge since we basically need to separate membership fee from the the actual payment schedule and make alternative payment schedules available within the same membership level.
We have been thinking about this ourselves and your post is very timely. I hope we will get more feedback and votes on this so that we can prioritize it higher.
However, since it is a substantial change, I do not expect us to start actual development for at least 6 months - and (I hope) the recession will be mostly over by then...
-
113 votesEvgeny Zaritovskiy responded
For me personally, this a great suggestion and I’ve been thinking about it for long time myself. Ideally, I’d really like completely redesign our membership levels to concurrent subscriptions model. Subscription gives you access to some information or provide privileges. There can be multiple ways of buying it – e.g. for a year or two, recurring or not, etc. Altogether, subscription-based model is very robust and easy to understand. Please, vote!
Dmitry Buterin supported this idea ·An error occurred while saving the comment Dmitry Buterin commentedI would appreciate additional comments from anyone with a similar need.
Specifically, I would love to get detailed examples of what exactly would be included in each subscription. (I am mulling over an idea where people would have one membership level but would separate be able to buy one or more subscriptions, e.g. for access to some content areas)
An error occurred while saving the comment Dmitry Buterin commentedSorry, this is still on the wishlist - not even on our roadmap so for now it is not clear when we might be able to address this - if at all.
An error occurred while saving the comment Dmitry Buterin commentedThis is interesting, I would really like to hear from other users on this
An error occurred while saving the comment Dmitry Buterin commentedThis has not come up before so I encourage everybody who needs this to comment and vote for it.
-
3 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedI have tweaked the title to make this broader. For now only system fields have date type but we plan to allow custom date fields so this becomes even more relevant.
An error occurred while saving the comment Dmitry Buterin commentedGordon, as you can see, there were no other comments on this request - so for now we will have to keep it lower on our list than many other threads here.
-
37 votesDmitry Buterin supported this idea ·
An error occurred while saving the comment Dmitry Buterin commentedWould love to hear from others - would this be useful?
Sorry about that! Can you email me directly at db@wildapricot.com and give me a link to your page and couple of examples of members not plotted?