Walt Bilofsky
My feedback
231 results found
-
8 votesWalt Bilofsky
shared this idea
·
-
16 votes
An error occurred while saving the comment -
12 votesWalt Bilofsky
supported this idea
·
-
123 votes
An error occurred while saving the comment Walt Bilofsky
commented
Agree. This is the largest step percentagewise in the pay structure - 400% Most of the others are 250% or 300%.
We are close to 500. We will never need quadruple the number of contacts, but if we go a little bit over our price will almost double.
Walt Bilofsky
supported this idea
·
-
5 votes
An error occurred while saving the comment Walt Bilofsky
commented
You can do this now by inserting the entire link, starting with "mailto", as the link URL.
That said, not everyone knows HTML, so I'll vote for making this an optional field in the link dialog.
Walt Bilofsky
supported this idea
·
-
6 votesWalt Bilofsky
supported this idea
·
-
314 votes
Evgeny Zaritovskiy
responded
Collecting comments now.
An error occurred while saving the comment Walt Bilofsky
commented
I have a design proposal.
The way we now create recurring events with separate registrations is to make one event and then copy it, one by one, to each date for that event. This is tedious.
We can already use the current system to create one event with a list of recurrences. So I propose a button that will turn this recurring event into separate events, one for each recurrence.
Of course, right after we click the button, we will realize that we need to correct something. So we need button #2 to delete all those recurrences in one click. so we can start over. Maybe save the first recurrence, which we can use to start over from.
Maybe we only need to change part of the series of events. So we need to be able to specify a date for button #2, and delete all events before that date, or after that date.
Oh, but deleting is permanent. We could delete and then realize that we have deleted too many events. So instead of only deleting, an option for button #2 is to set them to admin-only view. And an option to set them back to public view. And as a safety feature, only allow deletion if they are first set to admin-only.
This should be fairly simple. The only new data structure is to remember the group of recurring events so this button #2 can operate on all of them at once.
We may want to make a change to a subgroup of a recurring event. To do this, make a copy of one of the events. The copy will not be associated with the recurring event. Then delete the subgroup, make the change in the copy, and create a new recurring event from it, covering the dates that were just deleted.
An error occurred while saving the comment Walt Bilofsky
commented
Alex, that didn't quite work for me. Can you email me at bilofsky@toolworks.com?
An error occurred while saving the comment Walt Bilofsky
commented
Alex, thanks for any help. I don't know my CSS from my CSElbow, but can follow installation instructions.
The event is at https://tyc.org/event-3076030. I've temporarily shortened the recurrence list to keep the button on the screen.
An error occurred while saving the comment Walt Bilofsky
commented
The Case of the Disappearing Registration Button:
I posted a weekly class through the end of next year, using the single recurring event. We need people to register for the series, so the existing implementation would work.
Except - the Register button is 7 screens down, underneath the long list of 63 sessions. Sherlock Holmes couldn't find it, let alone our attendees.
While we wait for this second scenario to be implemented, could we please have a fix for this button placement? Either put it above the list of time/dates if the event is recurring, or display just the first few time/dates with a "More" link. Elementary!
An error occurred while saving the comment Walt Bilofsky
commented
@Amy - we have the same issue and I have a workaround for it.
See our yacht club's page at http://tyc.org . We have race, cruise and social events. Each of those categories is an event tag. The tags are used to display the appropriate events on the corresponding page in addition to the main calendar.
These one-off events also appear in Upcoming Events on the home page.
For recurring events, I use the tag "recurring social". These are excluded from Upcoming Events and get their own upcoming gadget right below. That solves the problem you mention.
I am not seeing the problem reported by Anonymous.
An error occurred while saving the comment Walt Bilofsky
commented
@Schneibs: I see you found this thread with the workaround. For others interested, see https://forums.wildapricot.com/forums/308926-designers/suggestions/10173666-how-to-hide-session-label-in-event-title-from-up .
An error occurred while saving the comment Walt Bilofsky
commented
Our old web site uses Calcium from Brown Bear Software. This has a simple interface for repeated independent events.
When an event is created, an optional repetition can be specified, as you do for Scenario 1.
When a multiple instance event is edited or deleted, there is a choice to edit or delete the current event, all the events in the series, the current and all subsequent dates, or the current and all previous dates.
If an edit or delete affects multiple events, any previous changes made in those events is lost. The edited version replaces all the specified instances.
The only drawback is that if some future dates have been removed from the series (for a holiday, for example), changing the series puts them back. But you could handle that case better.
Walt Bilofsky
supported this idea
·
-
4 votes
An error occurred while saving the comment Walt Bilofsky
commented
This should be added to https://forums.wildapricot.com/forums/308932-wishlist/suggestions/36649381-email-text-formatting . You can't vote for that one because it is marked "Resolved", although it isn't. But you can still comment.
-
2 votes
An error occurred while saving the comment Walt Bilofsky
commented
It's still there. Maybe you were using a simple event? Recurring events is only available for advanced events.
-
2 votesWalt Bilofsky
shared this idea
·
-
41 votes
An error occurred while saving the comment Walt Bilofsky
commented
Over the years, we've slid over our contact limit a few times due to non-member event registrations. Used to be, nothing happened. When I asked, WA support said that if it became a problem, I would be contacted. And of course I deleted contacts and got back under the limit.
But the last time - since Personify took over WA - we received a brusque email threatening that functions creating contacts could "be temporarily deactivated (online member application, event registrations, adding members manually, online donations etc.)" No deadline was given - I didn't know whether I had two weeks to deal with it or two minutes.
So that makes this change even more necessary.
An error occurred while saving the comment Walt Bilofsky
commented
Walt Bilofsky
supported this idea
·
An error occurred while saving the comment Walt Bilofsky
commented
The problem is that contacts are added willy-nilly when, most commonly, a non-member registers for an event. So the number can balloon and they have to be deleted by hand to stay under the limit.
But unless I'm missing something, the only loads that a non-member contact places on the system are to register for events and receive emails. And they are less likely to do that than members.
So the request to have a higher contact limit than membership limit makes sense to me.
Contacts can set a password and log in. Is there any use to that?
-
89 votesEvgeny Zaritovskiy
responded
I’m making this not just about events, but other lists too – this is a common usability problem.
An error occurred while saving the comment Walt Bilofsky
commented
When returning to a list (member list, contact list, event list, etc.) using the Back link, it should return to the list entry that was being viewed, NOT to the beginning of the list.
There are times when we need to look through a list and edit some but not all of the entries. That is incredibly tedious when we have to find our place in the list again for every single item. When the list is longer than 50 and we always return to the first page, it's impossibly annoying.
Back should mean Back!!!
Walt Bilofsky
supported this idea
·
-
5 votesWalt Bilofsky
supported this idea
·
-
50 votesWalt Bilofsky
supported this idea
·
-
36 votes
An error occurred while saving the comment Walt Bilofsky
commented
Shouldn't the Wishlist suggestions above, and this one, and also https://forums.wildapricot.com/forums/308932-wishlist/suggestions/20507482-allow-member-contact-macro-on-webpages be merged? And a number of other macro suggestions too.
An error occurred while saving the comment Walt Bilofsky
commented
Another example of the utility of admin-defined macros: Define {President} to be the name of the current organization president.
This could be used on a web page listing the officers, in the signatures of many automatically generated emails that should come from the president, etc.
Then when a new president takes over, just change the macro.
Walt Bilofsky
supported this idea
·
Walt Bilofsky
shared this idea
·
-
9 votesWalt Bilofsky
supported this idea
·
-
47 votesEvgeny Zaritovskiy
responded
I have merged several similar suggestion together – they all about previewing various site functions from members perspective. For example, wen pages, registration and application forms, etc.
Walt Bilofsky
supported this idea
·
-
12 votes
An error occurred while saving the comment Walt Bilofsky
commented
Thanks for the instructions for a workaround. However it is not very convenient, and will not work for Edge and IE, which are about 10% of browser users. So please keep this request open.
Walt Bilofsky
supported this idea
·
-
56 votes
An error occurred while saving the comment Walt Bilofsky
commented
Jon, here's how I handle this: If the husband is fred@wa.com, then for his wife Nancy I use the login fred+n@wa.com.
You have to disable all emails for Nancy, and if she wants to log in under her own account you need to set her password. But typically if they share an email address they don't mind sharing Fred's login.
An error occurred while saving the comment Walt Bilofsky
commented
Walt Bilofsky
supported this idea
·
-
1 voteWalt Bilofsky
shared this idea
·
Merge with https://forums.wildapricot.com/forums/308932-wishlist/suggestions/8825587-listserv-i-e-ability-to-submit-forum-posts-by-ema .