Pesky Little Bug Fixes
Unable to set a password using special characters (FB 29709, ZD 201609)
It was not possible to reset a password using any of the following special characters : #$%^*_+=~`{}[]|;’?. This is now fixed.
Error using Advanced Search in the directory (FB 29668)
If a large number of filters were selected in the directory Advanced Search, an error would appear. This has been fixed.
Rejected memberships did not refund credit card in the advanced interface (FB 33470, FD 5995)
If a new member joins with a credit card and is pending membership approval, the credit card was not refunded when rejecting their membership. This has been fixed to provide you with the opportunity to refund the card in one workflow.
Special characters were not displaying in some areas (FB 32636, FD 2374)
There were some areas of Membee, such as event confirmation emails and listing descriptions, where special characters would not show up. This has been resolved.
Incorrect transactions when cancelling part of an event sale (FB 32814)
If part of a multi-item event sale was cancelled, and the option to writeoff and refund was selected, the transactions were incorrect in some scenarios. This has been resolved.
Directory map pin was not displaying (FB 32769, FD 2789)
When a single listing was returned in a search in the online directory the map pin was not always displaying. This has been fixed.
Social media logins were appearing when they are unavailable (FB 33084, FD 3511)
There were some cases where the social media login buttons that are no longer available were still showing up on the Create / Reset password page. This is now fixed.
Participation Report was timing out (FB 32432, FD 1672)
If large amounts of data were picked up by the Participation report, it could timeout. We optimized the report to prevent this from happening.
Added the {OrgNumber} Merge variable to specific email templates (FB 29628)
The {OrgNumber} merge variable has been added to the invoice emails sent for members with print, stored credit card, and bank draft billing methods.
Address Type Order in a favorite Event Invoices report was not being applied (FB 32732, FD 2663)
If you saved a favorite for the Event Invoices report where you set the address type order, the setting was not being maintained if you edited an event sale, selected to print the invoice and selected that favorite. This has been fixed.
Slowness when visiting the Activities tab (FB 33393, FD 4933)
Some historical event attendance data could cause slowness when going to the Activities tab on a record. This has been resolved.
Some columns in the Notes & To Dos report were not aligned correctly (FB 29868, FD 1023)
When exporting the Notes & To-Dos report, it was possible that some of the data was not aligned in the correct columns. This has been fixed.
When a registrant is checking out returns to registration page, it does not redirect correctly (FB 33340, FD 5063)
If you set up Authorize.net as your payment gateway and a visitor registering for an event clicked on Cancel on the payment screen it was not redirecting back to the event registration page correctly. This has been fixed.
Unable to save Facebook field with an underscore (FB 29871, FD 969)
Members will now be able to successfully save a Facebook URL that contains an underscore via the online Profile.
Uploaded event header image of 1250px was resized to 1000px (FB 29713)
The header images uploaded to an event using a 1250px layout were being resized to a maximum of 1000 pixels wide. This is now fixed, so an image 1250 pixels wide or more will take up the full width of the event header.
Error when member logs out (FB 29713)
It was possible when a member logged out of a Membee feature or a page that used Membee’s Login Plugin on a WordPress site, to get an error. This has been fixed.
Tax shows $0 when the price column was disabled (FB 33326, FD 4887)
If an Event Item had a fixed price but the price column was not selected to display, the tax line would display $0.00 This has been fixed, so the tax line will show the expected tax amount.
City field not filled in automatically when contact was selected as an attendee (FB 29850, FD 389)
When an existing contact person’s record was selected as an attendee during an event sale, the City field wasn’t automatically filled in. This has been resolved.
Renewal Prerequisite Reminder can now use years as a metric (FB 29835)
We fixed the user notifications for Renewal Prerequisite Reminder automations, so they’ll now show “years” instead of “days.
Welcome email sent via Online Profile did not fill in the {MemberNumber} variable (FB 29817)
The {MemberNumber} merge variable didn’t work when the Welcome email was being sent through the online Profile. This is now fixed.
Merge variables in the new member notification email were not populating (FB 32809, FD 2924)
If you were collecting information for a common custom field on an entry form and set up the email Membee users receive to notify them of a new member to include that information, it was not showing up in the email (the information was being stored on the record, just not displaying in the email). This has been fixed.
Event sale assigning to the person when setup to assign to an organization if reviewing event registrations was enabled (FB 32710, FD 1870)
If you set up Membee to manually review, assign and approve each event registration and it was set up to assign the event sale to an organization in cases where the person and the organization were both members, the sale was being assigned to the person. This has been fixed.
Event Views tracking did not increase when viewed through a direct link (FB 29733)
The “Event Views” field on the event Setup tab in Membee did not increase if the event was accessed through a direct link. This has been resolved.
Price level visible to other members when it should only display for members with a specific status (FB 32688, FD 2599)
If you set up an event item to be conditional based on a subset, such as a status and there were more then one price level set up to be available based on different statues (ex. a gold and silver level) all levels would show when a member logged in instead of just the price levels they were able to purchase (they would not be able to purchase the level, but they were able to see it when they should not have been). This has been fixed.
Default values on an entry form were not applied when used internally (FB 32464, FD 1656)
If you have set up an entry form to set a default value(s) for a parameter(s) that value was not being set when a Membee user filled in and submitted the form from within Membee. This has been fixed.
Error when member tried to delete a contact from the online profile more than once (FB 29750)
If you have Membee set up so you need to review and approve every change made by members via the online profile update and a member made a change to a contact, then deleted that contact they would get an error when they tried to edit the organization again. This has been fixed.
Retention & Milestone email could send multiple times if Join Date is on February 28 (FB 29864, FD 973)
If a Retention & Milestone automation was set to gather members 1 month after the Join Date, and a member’s Join Date was on February 28, the email could be sent multiple times. This is fixed.
Headshot image on a sign up form was required even when it was not displaying (FB 29629)
If “Editable & Required” was selected for the Headshot Image field on a signup form, but the field itself was unchecked, it would still be considered required when filling in the form online. This has been fixed.
Name listed twice on an event invoice (FB 33380, FD 4713)
In some rare instances when an event sale was made the organization name or person name would be listed twice on the invoice. This has been corrected
Error when navigating past 10 categories in the directory (FB 29827)
When a directory had more than 10 categories, you would get an error when navigating past the 10th category in the list. This is now fixed.
Error when entering a long search term in the sales tab (FB 29870, FD 1089)
When searching on the Sales tab of an event in Membee you could get an error if you entered a long search term. This has been fixed.
Adjusting credit memo returns no results after clicking a record unless you click “Search” (FB 29765)
If you were searching for a member when adjusting an existing credit memo, the transactions would not appear unless you clicked the search button. This is now fixed so that the transactions appear immediately when selecting the org/individual record.
“About” in listing would appear blank (FB 29797, ZD 204532)
If a directory listing contained only the tag <br>, it would cause the “About” description to appear but it would be blank. This has been fixed.
Email was not sent when sign up form was set to send a welcome email but not allow them to setup their login (FB 29530, ZD 196156)
When “Send an email to welcome the person but do not allow them to set up their login” was selected on signup forms, the email was not sent. This is fixed.
Directory populate report with a parameter did not pull the correct data (FB 29663, ZD 200305)
When running the directory populate report using a common or person parameter to filter so that a specific group of members are pulled was not pulling the correct information. This has been fixed.
Event item set to be visible to a specific parameter was not working correctly (FB 29776, ZD 202655)
When a parameter value was selected for “Choose a subset”, the price level still showed online if the logged in person didn’t have the value selected. We resolved this, so the items will only be visible to the expected people.
Error when navigating past the 10th charitable receipt on a record (FB 29419, ZD 194777)
If you were on a member record with more than 10 charitable receipts, there was an error when you tried to navigate past the 10th receipt. This is fixed.
Unable to edit transation that was setup to calculate new and retained dollars (FB 29775, ZD 203139)
If a payment was made on an item for either membership or event billing and that item was set up to calculate new and retained dollars, you were unable to edit the transaction (for example change the payment date after the initial payment was applied). This has been fixed.
Current period shows “period is complete” incorrectly (FB 29793, ZD 203579)
If an invoice was posted and written off, and then another invoice was posted for the same membership period, the Current Period panel would incorrectly show “The period is complete”. This has been resolved.
New member’s join date not set correctly to the following month if the record already exists (FB 29802, ZD 204696)
If you had set up a new member sign-up form to set the join date to the first day of the next month and a person, who already existed in Membee as a non-member used the form to sign up, the join date was being set to the day the form was submitted instead of the 1st day of the next month. This has been fixed.
Previous member appears in new member list (FB 29685, ZD 200514)
It was possible for an organization or person who were previously a member to appear in the new member list, in the directory, if they had a join date within the criteria set. This has been fixed.
What Does “(FB ####, FD #### or ZD ####)” Mean?
These are the tracking IDs as a bug fix or enhancement works its way through our internal processes. FogBugz (FB) is the system we use to track and prioritize enhancements and fixes in our development process. Freshdesk (FD) our awesome help desk system that you use to submit tickets to Membee customer service – you are currently reading this on Freshdesk too! Zendesk (ZD) was our previous support system.
Sometimes, the bug fix or enhancement is generated by us in which case you won’t see a “FD” number in addition to the FB number noted.
Freshdesk and FogBugz are integrated which makes fast and easy from us to quickly promote something coming in from a client (through Freshdesk) to FogBugz for evaluation and the assigning of a priority by our Development team.
