Minor Enhancements
Updated Braintree Release
A new version of the SDK was released with new security enhancements. We have updated the integration between Membee and Braintree to the 5.15 release of the SDK. If you received a notice from Braintree about this new version, you do not need to do anything! :)
Pesky Little Bug Fixes
Promo code not applying correctly when selling multiple complimentary items (FB 29639, ZD 198923)
If you were completing an quick event sale where you were selling a multiple quantity of complimentary items and items where a promo code was applied, the promo code was not calculating correctly. This has been fixed.
Event Details – By Purchaser showing incorrect balances for certain purchasers (FB 29697, ZD 200729)
If a single purchaser had multiple outstanding event invoices, the Event Details – By Purchaser wouldn’t show their total balance correctly. This has been resolved.
Organization’s auto-reewal changes back to billing when editing contact type (FB 29385, ZD 193461)
If an organization was set up for auto-renewal and the contact with the stored card had their Contact Type updated, the organization’s billing method would be set back to ebilling.
Accents in the first or last name were not accepted in the online profile (FB 29698, ZD 200974)
First Name and Last Name can now be updated with accents through the online Profile.
Custom export did not show selected columns when editing through a saved report (FB 29359, ZD 191992)
When a custom export is edited through a favorite Event Details report, not all fields selected would show up. This was fixed.
Tax charged on previous and new membership (FB 29708, ZD 201598)
When a membership was changed online, tax for both the old and item was charged. This was fixed.
Contact deleted from one organization was deleted from all organizations in the online profile (FB 29684, ZD 200922)
If a contact was associated with more than one organization and that person was deleted via an online profile update from one organization, they were deleted from all organizations. This has been fixed so that the person would remain a contact of the other organizations they are associated with (and just be removed from the organization making the profile update).
Online profile returned an error when using underscores in fields (FB 29665, ZD 200199)
If a member was adding information to a custom field and used an underscore (“_”) in the text, Membee would not save the information and display a message that an underscore could not be used. This has been fixed.
Only some additional sections in the online invoices were displaying but not all (FB 29705)
If you set up additional sections on your eBill where you included the option to change to a different membership level in more than one section, not all sections would appear on the ebill. This has been corrected
The value “|” caused an error when editing or adding custom CSV exports (FB 29671, ZD 200724)
If you had a “|” in the values for a list of parameters, you would get an error when you tried to add or edit a custom CSV export. This has been fixed.
Reinstating membership was reactivating incorrectly if the member was cancelled via the Batch Membership Management report (FB 29460, ZD 196128)
If a membership invoice was previously written off with the Batch Membership Management report, it could be incorrectly reactivated when reinstating membership. This has been fixed so that the correct invoice will be reactivated during reinstatement.
New member feed was showing new members with a future join date (FB 29621, ZD 198565)
If you set up a new member feed and did not link it to a directory it was possible that members with a join date in the future would show up in the feed (when they should only show up once their join date is within the range set for the display of new members). This has been fixed.
Booth number not always appearing in the Event Account Balance report (FB 29647, ZD 199321)
If a booth number was added to the details for a sale, that booth number did not always show up in the PDF of the Event Account Balance report. This has been fixed.
The organization type-ahead did not work if the organization label used an apostrophe (FB 29667, ZD 200694)
If you collect the employer information on a sign-up form for an individual and you set a field label for the employer that included an apostrophe (ex. Employer or Business Name/Nom du employeur ou d’entreprise) The type-ahead feature that allows the new member to find existing organizations was not working. This has been fixed.
Account balance report showing incorrect balances (FB 29545, ZD 196629)
If payment was applied to both an event and membership invoice, the correct balance wouldn’t show if the Module Source filter was set in the Account Balance report. This was resolved.
Sign-up forms on Safari returning reCAPTCHA error (FB 29710, ZD 201816)
A reCAPTCHA error was generated when filling out signup forms on Safari and this has been fixed.
Incorrect invoice reactivated when reinstating membership online (FB 29700, ZD 201011)
If two invoices were written off for the same membership period, the wrong invoice could have been reactivated when a cancelled member reinstated their own membership online. This was resolved.
Error with date fields returns when storing credit card in the profile (FB 29551, ZD 196489)
After updating a stored credit card through the profile, date fields will now remain in the correct format.
What Does “(FB ####, 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. ZenDesk (ZD) is our awesome help desk system that you use to submit tickets to Membee customer service – you are currently reading this on ZenDesk too!
Sometimes, the bug fix or enhancement is generated by us in which case you won’t see a “ZD” number in addition to the FB number noted.
ZenDesk and FogBugz are integrated which makes fast and easy from us to quickly promote something coming in from a client (through ZenDesk) to FogBugz for evaluation and the assigning of a priority by our Development team.
