Luminate Online Version 19 Release Notes

Release 19.10.1
Release 19.10
Release 19.8
Release 19.5
Release 19.2.2
Release 19.2/19.2.1

Version 19.10.1 Release Notes

Product Updates

Security Improvements

We've enhanced CAPTCHA on Luminate Online donation forms to ensure further protection against fraudulent activity.

We've added additional security enhancements.

Donation form option clarification

We've updated the Validate API Donation Requests option description in Luminate Online's donation form configuration to clarify that the option is not compatible with API integrations such as Facebook Fundraising integration with TeamRaiser offline donations.

Resolved Issues

Bug	Description
LO-4297	Processing a TeamRaiser registration or donation on a responsive, one-page layout form can create duplicate TeamRaiser transactions One-page TeamRaiser donation and registration forms prevent duplicate transactions.
LO-6002	Following the 19.10 release, custom fields no longer display the custom label on a constituent record Custom field labels display as expected on a constituent record.
LO-6025	In Calendar Events, the Email Opt-in option is not selected despite the option being selected in the database The Email Opt-in option displays as selected when viewing Calendar Events if the option is selected in the database.
LO-6026	Some reports no longer display a column for Accepts Email In Reports, the Accepts Email column displays as expected.

Version 19.10 Release Notes

Product Updates

Participant Center 3

A new and fully-redesigned Participant Center 3.x, also called PC3, offers many new enhancements, including responsive behavior to mobile phone and tablet views! Participant Center 3 makes it easy for you and your participants to create a customized page.

See Participant Center 3.

Offer direct debit payments on donation forms

Donors can now pay for one-time or recurring gifts with direct debit on donation forms that use a Blackbaud Merchant Services (BBMS) gateway. Direct debit (ACH) payments are currently available in the United States.

How do I configure my donation form to offer direct debit payments?

To offer direct debit payment on your donation forms:

Set the Bank ACH Account to your Blackbaud Merchant Services gateway.

Go to Setup, Payment Capabilities.

Note: Access to Setup, Payment Capabilities is available to administrators who use BBMS and have the Merchant Account Self Provisioning permission. If you don't see this option and feel you should, contact Blackbaud Support. See Payment Capabilities for more information.

On the Merchant Accounts page, Edit your merchant account.

In the Bank (ACH) Account option, select your Blackbaud Merchant Services gateway.

Click Finish.

Set the Blackbaud Merchant Services gateway on the donation campaign.

Go to Fundraising, Donation Management.

Edit the donation campaign.

On the Choose Financial Options page, select your Blackbaud Merchant Services gateway in the Merchant Account option.

Donation forms associated with the donation campaign now display the Checking Account option in the payment section.

Enhancements to Facebook Fundraiser integration

TeamRaiser event participants now have an easier time managing the integration of their event's Personal Page and their Facebook Fundraiser.

Upon login to a Personal Page, an automatic check verifies that the linked Facebook Fundraiser is still published. If the Facebook Fundraiser is deleted, connections are automatically unlinked so that participants can easily link to a new Facebook Fundraiser.

To support this feature, we've added a new CR endpoint, confirmFundraiserStatus, to the TeamRaiser API.

Security improvements

When an administrator enters an invalid passcode consecutively 6 times, Luminate Online now enforces a temporary lockout for a period of 30 minutes. In the event of a lockout, the login screen displays notice of the locked account.

Resolved Issues

API

Bug Description

Bug	Description
LO-1356	Constituent API `create` method sets `email.accepts_email` to TRUE when the `email.accepts_email` parameter is not provided which may opt constituents into email by default When making a call to the Constituent `create` API method, the `email.accepts_email` parameter now defaults to FALSE so that constituents are not opted into email by default when the value is not specified.
LO-2244	The TeamRaiser API `processRegistration` method does not restrict team size maximums when secondary participants are included When using the `processRegistration` method to create new TeamRaiser registrations for members of a team, the team's maximum size is respected even when secondary registrations are included.

LO-1356

Constituent API create method sets email.accepts_email to TRUE when the email.accepts_email parameter is not provided which may opt constituents into email by default

When making a call to the Constituent create API method, the email.accepts_email parameter now defaults to FALSE so that constituents are not opted into email by default when the value is not specified.

LO-2244

The TeamRaiser API processRegistration method does not restrict team size maximums when secondary participants are included

When using the processRegistration method to create new TeamRaiser registrations for members of a team, the team's maximum size is respected even when secondary registrations are included.

Donations

Bug	Description
LO-5622	In the Blackbaud Merchant Services Portal, the Luminate Online confirmation code is not included on a chargeback Luminate Online confirmation codes are now included in the details of each transaction in Blackbaud Merchant Services so chargebacks can be easily identified in Luminate Online.
LO-2765	Custom donation elements on donation forms permit logged-out constituents to opt into email You can no longer select the Email, Accepts Email option when adding a True/False type custom donation element to a donation form so that constituents who are not logged in are not opted into email subscriptions.

Bug

Description

LO-5622

In the Blackbaud Merchant Services Portal, the Luminate Online confirmation code is not included on a chargeback

Luminate Online confirmation codes are now included in the details of each transaction in Blackbaud Merchant Services so chargebacks can be easily identified in Luminate Online.

LO-2765

Custom donation elements on donation forms permit logged-out constituents to opt into email

You can no longer select the Email, Accepts Email option when adding a True/False type custom donation element to a donation form so that constituents who are not logged in are not opted into email subscriptions.

eCommerce

Bug	Description
LO-5615	When eCards are used for eCommerce products, the Thank You page displays the eCard recipient's name instead of the donor When eCommerce products use eCards, the Thank You page now displays the donor name for the donation acknowledgment.

Bug

Description

LO-5615

When eCards are used for eCommerce products, the Thank You page displays the eCard recipient's name instead of the donor

When eCommerce products use eCards, the Thank You page now displays the donor name for the donation acknowledgment.

Bug	Description
LO-5650	Update email classification of soft bounce Soft bounce definitions were updated.
LO-5770	Email Campaign Filters incorrect for Message Open filters To clarify Email Campaign filter behaviors, when multiple delivery filters are applied to an Email message, the filter summary now separates the filters with the word "AND" instead of "OR" on the Delivery Details page.

Bug

Description

LO-5650

Update email classification of soft bounce

Soft bounce definitions were updated.

LO-5770

Email Campaign Filters incorrect for Message Open filters

To clarify Email Campaign filter behaviors, when multiple delivery filters are applied to an Email message, the filter summary now separates the filters with the word "AND" instead of "OR" on the Delivery Details page.

Reports

Bug	Description
LO-5422	In Reports Classic, using the option, "Show all team members as well as team summary," in the TeamRaiser Team Summary Report causes the registration upsell cost per registrant to display as multiplied by 100 Selecting the "Show all team members as well as team summary" option for the TeamRaiser Team Summary Report no longer displays the registration upsell cost per registrant as multiplied by 100.
LO-5505	The Report Writer TeamRaiser Gift Details report shows $0 for a transaction value in the Original Value Transacted field Now, when running the Report Writer TeamRaiser Gift Details report, the Original Value Transacted field displays the correct transaction value.

Bug

Description

LO-5422

In Reports Classic, using the option, "Show all team members as well as team summary," in the TeamRaiser Team Summary Report causes the registration upsell cost per registrant to display as multiplied by 100

Selecting the "Show all team members as well as team summary" option for the TeamRaiser Team Summary Report no longer displays the registration upsell cost per registrant as multiplied by 100.

LO-5505

The Report Writer TeamRaiser Gift Details report shows $0 for a transaction value in the Original Value Transacted field

Now, when running the Report Writer TeamRaiser Gift Details report, the Original Value Transacted field displays the correct transaction value.

TeamRaiser

Bug Description

Bug	Description
LO-5884	Unanswered survey questions during registration cause Technical Difficulties errors and issues with the S48 S-Tag due to NULL pointer exceptions Survey questions that are unanswered by registrants are now captured as unanswered (blank) instead of `NULL` so that registration workflow behavior works as expected.

LO-5884

Unanswered survey questions during registration cause Technical Difficulties errors and issues with the S48 S-Tag due to NULL pointer exceptions

Survey questions that are unanswered by registrants are now captured as unanswered (blank) instead of NULL so that registration workflow behavior works as expected.

Version 19.8 Release Notes

Tip: The new Blackbaud Checkout Donation Form Kit is ready to download for quick, easy set up of Blackbaud Checkout so you can give your donors a modern, responsive donation form!

Product Updates

Blackbaud Checkout for GBP

Blackbaud Checkout now accepts the United Kingdom's GBP (British Pound) currency.

Janrain is now Akamai Identity Cloud

If your organization uses Janrain for social login and sharing authentication, be aware that Janrain is now branded as Akamai Identity Cloud following an acquisition earlier this year. At this time, existing Janrain integrations require no updates. You'll simply notice the rebrand and updated website for the company. You can still reach your Janrain dashboard at https://dashboard.janrain.com/.

Our help documentation is updated to reflect the rebrand to Akamai Identity Cloud. However, some documentation may continue to use the legacy name, Janrain where applicable.

Security Improvements

User-side login pages no longer allow the browser to autocomplete the password fields.
Luminate payment processing now handles the new "Fraudulent activity detected" message from Payflow Pro and declines the transaction.

Resolved Issues

Advocacy

Bug	Description
LO-3055	In Vote Center, after selecting the option to require a phone number and clicking Next, then Back, the phone number option is no longer selected In Vote Center, phone numbers are now automatically set as a required option to ensure that messages are delivered to the targeted official.
LO-3986	The S93 S-Tag does not display default text when used in an email sent to constituents that have no physical address in their record The S93 S-Tag, which displays a constituent's representatives as determined by a physical address, now displays default text (such as "Your U.S. Senator") when used in an email sent to constituents with no address in their record.

Bug

Description

LO-3055

In Vote Center, after selecting the option to require a phone number and clicking Next, then Back, the phone number option is no longer selected

In Vote Center, phone numbers are now automatically set as a required option to ensure that messages are delivered to the targeted official.

LO-3986

The S93 S-Tag does not display default text when used in an email sent to constituents that have no physical address in their record

The S93 S-Tag, which displays a constituent's representatives as determined by a physical address, now displays default text (such as "Your U.S. Senator") when used in an email sent to constituents with no address in their record.

API

Bug	Description
LO-3055	The TeamRaiser getGifts API method does not return a check number for offline check donations when the checkNumber parameter is included When the TeamRaiser `getGifts` API method call includes the `checkNumber` parameter, the response now includes the check number for offline gifts with a check number.
LO-3914	Calls to the TeamRaiser `getTeamsByInfo` method sort the response incorrectly when ordered by total The TeamRaiser `getTeamsByInfo` method no longer displays some teams with $0 totals at the top of the list.
LO-4780	When using the `addGift` method, users are unable to specify a past gift_date when confirmed=true When specifying a `gift_date`, the `addGift` method now always respects the entered value.
LO-5355	`CRTeamraiserAPI.setTeamCaptains` does not always set the specified participant as a captain When using `CRTeamraiserAPI.setTeamCaptains` when the `fr_team.captain_cons_id` changes to identify a new captain, the `fr_registration.is_captain field` now also updates to reflect captain status for the new "default" team captain.
LO-5396	An empty API response occurs for server-side servlets when credentials are incorrect Calls to a server-side servlet that use incorrect credentials no longer return an empty response.

Calendar Events

Bug	Description
LO-3055	An unclosed <div> element on the billing information page of the Calendar Events template causes the layout of elements in the page header to break A missing closing </div> tag was added to the template for the billing page in Calendar Events so that formatting issues in page layout no longer occur.
LO-5420	No Message Catalog entry exists for "Order Limit" In the Message Catalog, the text for "Order Limit," which is seen when clicking on a Ticket Type for a calendar event, is now available for modification.

Bug

Description

LO-3055

An unclosed <div> element on the billing information page of the Calendar Events template causes the layout of elements in the page header to break

A missing closing </div> tag was added to the template for the billing page in Calendar Events so that formatting issues in page layout no longer occur.

LO-5420

No Message Catalog entry exists for "Order Limit"

In the Message Catalog, the text for "Order Limit," which is seen when clicking on a Ticket Type for a calendar event, is now available for modification.

Donations

Bug	Description
LO-3982	The Designee Div tag on a donation form is not set up properly and can't be targeted with CSS When using the Designated Giving Donation Level data element on a donation form, setting the Display Style to Fixed Designation Choice now correctly displays the <div> tag code and can be targeted for CSS styling.
LO-5655	When Blackbaud Checkout uses a donation form with Honor Gift fields, the button to move to the next screen doesn't work When using Blackbaud Checkout with a donation form containing Honor Gift fields, the buttons to move the donor through the checkout process work as expected.

Bug

Description

LO-3982

The Designee Div tag on a donation form is not set up properly and can't be targeted with CSS

When using the Designated Giving Donation Level data element on a donation form, setting the Display Style to Fixed Designation Choice now correctly displays the <div> tag code and can be targeted for CSS styling.

LO-5655

When Blackbaud Checkout uses a donation form with Honor Gift fields, the button to move to the next screen doesn't work

When using Blackbaud Checkout with a donation form containing Honor Gift fields, the buttons to move the donor through the checkout process work as expected.

Library

Bug	Description
LO-5616	In the Document Library, Excel documents download in the wrong format and display an error when opened The Document Library now saves a Microsoft Excel document as an .xlsx file so that an error no longer occurs when opening the document.

Bug

Description

LO-5616

In the Document Library, Excel documents download in the wrong format and display an error when opened

The Document Library now saves a Microsoft Excel document as an .xlsx file so that an error no longer occurs when opening the document.

Reports

Bug	Description
LO-3406	When an eCommerce purchase is made through a TeamRaiser, the eCommerce Purchase report does not find the store ID which can result in false results Purchases made through an eCommerce store that was set up for a TeamRaiser event are now included in the TeamRaiser eCommerce Purchases Report results.
LO-4506	In Report Writer, the Event Attendees Report does not include all survey answers for Ticketed Event types The Event Attendees Report results now include the answers to all survey questions for Ticketed Event types.

Bug

Description

LO-3406

When an eCommerce purchase is made through a TeamRaiser, the eCommerce Purchase report does not find the store ID which can result in false results

Purchases made through an eCommerce store that was set up for a TeamRaiser event are now included in the TeamRaiser eCommerce Purchases Report results.

LO-4506

In Report Writer, the Event Attendees Report does not include all survey answers for Ticketed Event types

The Event Attendees Report results now include the answers to all survey questions for Ticketed Event types.

S-Tags

Bug	Description
LO-5421	S334:pagename doesn't work on secure pages The S334 S-Tag now returns the "pagename" value when S334:pagename is used on secure PageBuilder pages.

Bug

Description

LO-5421

S334:pagename doesn't work on secure pages

The S334 S-Tag now returns the "pagename" value when S334:pagename is used on secure PageBuilder pages.

TeamRaiser

Bug	Description
LO-1346	When the value for a registration response is deleted and saved through the Participant Center, it shows up again after refreshing the browser When a registration response is deleted in the Participant Center, refreshing the browser no longer causes the previous value to display again.
LO-4805	The event donation form URL is malformed on the status page which prevents soft credits from working The event donation form URL on the TeamRaiser status page now uses upper-case characters for proxy ID and type to ensure that soft credits are recorded properly.
LO-5390	Merging two constituent records where one is linked to a TeamRaiser registration connected to Facebook, and the registration moves to the other constituent ID (cons_id), a donation error occurs when donating within Facebook: "A temporary problem occurred when trying to complete your request. Please try again later" Now, when attempting to merge two constituent records where one of the records is registered for a TeamRaiser event with a Facebook Fundraiser ID, validation occurs to ensure that the record with the associated Facebook Fundraiser is the master record.

Bug

Description

LO-1346

When the value for a registration response is deleted and saved through the Participant Center, it shows up again after refreshing the browser

When a registration response is deleted in the Participant Center, refreshing the browser no longer causes the previous value to display again.

LO-4805

The event donation form URL is malformed on the status page which prevents soft credits from working

The event donation form URL on the TeamRaiser status page now uses upper-case characters for proxy ID and type to ensure that soft credits are recorded properly.

LO-5390

Merging two constituent records where one is linked to a TeamRaiser registration connected to Facebook, and the registration moves to the other constituent ID (cons_id), a donation error occurs when donating within Facebook: "A temporary problem occurred when trying to complete your request. Please try again later"

Now, when attempting to merge two constituent records where one of the records is registered for a TeamRaiser event with a Facebook Fundraiser ID, validation occurs to ensure that the record with the associated Facebook Fundraiser is the master record.

Web Services

Bug	Description
LO-5395	The Web Services Console accepts any password for the API administrator login Luminate Online API administrators must use their specified password to log into the Web Services Console.

Bug

Description

LO-5395

The Web Services Console accepts any password for the API administrator login

Luminate Online API administrators must use their specified password to log into the Web Services Console.

Version 19.5 Release Notes

Product Updates

Security improvements

All eCommerce pages now served securely: All shopping pages, including non-shopping cart pages, are served on secure (HTTPS) pages, similar to securely-served payment pages.

Account lockout due to multiple invalid login attempts: Luminate Online now enforces a temporary lockout period of 30 minutes if an administrator or user enters invalid credentials consecutively 6 times. In the event of a lockout, the login screen displays notice of the locked account. Password reset remains available to use, but new login attempts are restricted until lockout time completes.

API password obfuscation: When you Manage Administrative Accounts, the Edit server API configuration page now obfuscates API administrator passwords.

Web Application Firewall: Luminate Online now provides added protection to websites from targeted attacks with a Web Application Firewall (WAF), a Payment Card Industry (PCI) compliant, cloud-based security service.

Security and fraud blocking for API donation requests: In the event of fraudulent attempts on a donation form via API calls, a new option stops the fraudulent activity.

Warning: This feature is not compatible with API integrations, such as Facebook Fundraising integration donations. If you aren't sure whether your donation form is used for those integrations, contact Blackbaud Support to help you determine whether you should enable this feature.

When enabled, donation forms validate API requests against the required fields and limits (such as minimum donation), enhancing fraud protection over API donation forms and eliminating dummy data that comes from API fraud attempts. For steps to enable this option, see Identify the Donation Form.

Returning Teams API updates for customized TeamRaiser registrations

Luminate Online API developers can now build custom interfaces to allow TeamRaiser registrants to re-create teams from a previous, associated TeamRaiser! Returning TeamRaiser team API updates enable one-click registration for returning teams.

getRegistrationDocument now returns a response for previousTeamId when previous teams are permitted.

processRegistration now handles previousTeamId to return a team from the previous associated TeamRaiser. See the Team Matching section here.

getTeamsbyInfo includes a new parameter, include_unreturned_teams. When a TeamRaiser has a previous, associated event and has returning teams enabled, this parameter runs an additional query for teams on the previous, associated TeamRaiser that have not reformed and combines the list to the current list of teams. The query to get the list of unreturned teams supports filtering by team name, company info, captain name, captain screen name, team division, etc.

getEventDataParameter can now retrieve multiple event settings for a TeamRaiser event in one call by using the edp_names parameter.

Resolved Issues

Calendar Events

Bug	Description
LO-5392 LO-4791	Calendar Event forms load slowly due to integration of Luminate Online with Raiser's Edge or Luminate CRM An update was made to improve website performance of Calendar Event registrations for customers who use an integration of Luminate Online with Raiser's Edge or Luminate CRM.

Bug

Description

LO-5392 LO-4791

Calendar Event forms load slowly due to integration of Luminate Online with Raiser's Edge or Luminate CRM

An update was made to improve website performance of Calendar Event registrations for customers who use an integration of Luminate Online with Raiser's Edge or Luminate CRM.

Documentation

Bug	Description
LO-3628	The processRegistration API documentation was updated to include the recordOnly parameter and clarify payment information behavior for the method.
LO-3670	The Group Performance by Message Variant Report documentation was updated to clarify that the report returns data for current members of a delivery group only. So when a constituent is removed from a delivery group after an email variant is sent, the constituent's delivery data is no longer available in the report.

eCommerce

Bug	Description
LO-5288	Sales tax is applied on shipping charges for non-taxable items When a cart contains only tax-exempt items, shipping tax is not charged even in states that have a shipping tax.

Bug

Description

LO-5288

Sales tax is applied on shipping charges for non-taxable items

When a cart contains only tax-exempt items, shipping tax is not charged even in states that have a shipping tax.

System

Bug	Description
LO-5425	The Site Option, VELOCITY__BLACKLISTED_EMAILS, is case sensitive The Site Option (SDP) to blacklist emails, VELOCITY_BLACKLISTED_EMAILS, is no longer case specific so that email addresses are blocked no matter whether the characters are upper or lower case.

Bug

Description

LO-5425

The Site Option, VELOCITY__BLACKLISTED_EMAILS, is case sensitive

The Site Option (SDP) to blacklist emails, VELOCITY_BLACKLISTED_EMAILS, is no longer case specific so that email addresses are blocked no matter whether the characters are upper or lower case.

TeamRaiser

Bug	Description
LO-5078	The team_roster.html page doesn't respect fr_CA multilocale for all text When viewing the team_roster.html page as a TeamRaiser participant who has a preferred language of French (fr_CA), the column header text now displays in French instead of English.
LO-5306	Facebook decline returns iATS error: authorizeCustomer IATS Error [0] : [INVALID BANK ACCOUNT] : [REJECT: 41] iATS Payments services updated payment processing so that Facebook integrations that process donations through iATS are no longer declined with the error, "INVALID BANK ACCOUNT."

Bug

Description

LO-5078

The team_roster.html page doesn't respect fr_CA multilocale for all text

When viewing the team_roster.html page as a TeamRaiser participant who has a preferred language of French (fr_CA), the column header text now displays in French instead of English.

LO-5306

Facebook decline returns iATS error: authorizeCustomer IATS Error [0] : [INVALID BANK ACCOUNT] : [REJECT: 41]

iATS Payments services updated payment processing so that Facebook integrations that process donations through iATS are no longer declined with the error, "INVALID BANK ACCOUNT."

Version 19.2.2 Release Notes

Product Update

We've enhanced validation of the donation form zip code field to prevent erroneous entries, such as when a browser autofills the fields.

Resolved Issue

Bug	Description
LO-4791	Calendar Event forms are taking a long time to load due to RELO integration An update was made to improve website performance of Calendar Event registrations for customers who use Raiser's Edge - Luminate Online integration.

Bug

Description

LO-4791

Calendar Event forms are taking a long time to load due to RELO integration

An update was made to improve website performance of Calendar Event registrations for customers who use Raiser's Edge - Luminate Online integration.

Version 19.2/19.2.1 Release Notes

Product Updates

Email Bounce Report

Quickly see what's going on with your email deliveries in the new Admin Bounce Detail Report. You'll see all bounced email addresses, the bounce type (hard or soft), and the bounce reason.

Review the report, then take action to resolve bounced email addresses so you can maintain a reputable sender status.

For an understanding of the bounce error codes in the REASON column, see Knowledgebase article 190038. Also see Bounced Email in the Email Resource Center for additional guidance on next steps.

For information on how to run the report, see Administrator Bounce Detail Report.

Blackbaud Checkout Canadian Support

Blackbaud Checkout, a simple mobile donation experience, now supports Canadian payments!

Note: ApplePay support for Canadian payments with Blackbaud Checkout is coming soon.

TeamRaiser improvements for mobile

Enhanced keyboards display on mobile phones and tablets so now it's even easier for your donors to enter a phone number and email address on a TeamRaiser donation form.

Performance and security enhancements

Improvements were made to secure and enhance performance of data in Luminate Online.

API updates

Updated methods

Content:getMessageBundle - Retrieve specific messages, such as instructions, labels, or error messages) in a specific language from the Message Catalog

Content:getTagInfo - Preview page content rendered by a session tag (S-Tag) or conditional tag

Constituent: logSocialShare - Log a record whenever a URL is shared to a specified social site with a certain user ID

TeamRaiser:validateDiscount - Validate TeamRaiser discount codes and apply the discount to the participation type for the current user

Get Personal Page information without authorization

Just like other TeamRaiser API methods listed in the Version 18.8 Release Notes , the GetPersonalPageInfo method no longer requires authorization.

Get Team information from the Team ID

The getTeamPageInfo method now includes an optional team_id parameter to identify a team. When a team does not have a captain, you can use the new team_id parameter instead of cons_id.

Resolved Issues

APIs

Bug	Description
LO-4682	API Web Application Description Language (WADL) file doesn't work for CRTeamraiserAPI after 16.3 The WADL file for CRTeamRaiserAPI is available again.
LO-5026	Constituent "create" API can create duplicate constituents where the only difference is capitalization in the name When creating TeamRaiser registrations through the Constituent API create method, duplicate constituent records are no longer created due to a different capitalization of the name.

Bug

Description

LO-4682

API Web Application Description Language (WADL) file doesn't work for CRTeamraiserAPI after 16.3

The WADL file for CRTeamRaiserAPI is available again.

LO-5026

Constituent "create" API can create duplicate constituents where the only difference is capitalization in the name

When creating TeamRaiser registrations through the Constituent API create method, duplicate constituent records are no longer created due to a different capitalization of the name.

Calendar Events

Bug	Description
LO-4952	Users created through a Calendar Event do not get opted out of email even when they select to opt out when registering Calendar Event registrants are correctly opted out of email when the "Opt In" box is not selected.
LO-4967	For multi-locale, survey questions in French render in English on the confirmation screen and autoresponder on Calendar Events For the French version of a Calendar Event on a multi-locale site, a registrant's answer to a custom question now displays in French instead of English on the confirmation screen and confirmation autoresponder email.

Bug

Description

LO-4952

Users created through a Calendar Event do not get opted out of email even when they select to opt out when registering

Calendar Event registrants are correctly opted out of email when the "Opt In" box is not selected.

LO-4967

For multi-locale, survey questions in French render in English on the confirmation screen and autoresponder on Calendar Events

For the French version of a Calendar Event on a multi-locale site, a registrant's answer to a custom question now displays in French instead of English on the confirmation screen and confirmation autoresponder email.

Constituent

Bug	Description
LO-5045	Constituent Transaction Information (CTI) recalculation error with the LIFETIME_TOTAL_TRANS_AMOUNT value The Constituent Transaction Information (CTI) recalculation process that displays results in the Previous Year Total Amount and Year-to-Date Total Amount fields was corrected to once again process recurring transaction information.

Bug

Description

LO-5045

Constituent Transaction Information (CTI) recalculation error with the LIFETIME_TOTAL_TRANS_AMOUNT value

The Constituent Transaction Information (CTI) recalculation process that displays results in the Previous Year Total Amount and Year-to-Date Total Amount fields was corrected to once again process recurring transaction information.

Content Editor

Bug	Description
LO-3497	Cannot select an image for editing when using the Content Editor (WYSIWYG) in certain versions of Google Chrome, Mozilla Firefox and Microsoft Internet Explorer Images in the Content Editor (WYSIWYG) are selectable and editable once again when on recent browser versions of Google Chrome, Mozilla Firefox, and Microsoft Internet Explorer.

Bug

Description

LO-3497

Cannot select an image for editing when using the Content Editor (WYSIWYG) in certain versions of Google Chrome, Mozilla Firefox and Microsoft Internet Explorer

Images in the Content Editor (WYSIWYG) are selectable and editable once again when on recent browser versions of Google Chrome, Mozilla Firefox, and Microsoft Internet Explorer.

Documentation

Bug	Description
LO-5009	Interaction Type documentation updates needed The documentation for Default Interaction Types was updated to include all Interaction Type IDs.

Bug

Description

LO-5009

Interaction Type documentation updates needed

The documentation for Default Interaction Types was updated to include all Interaction Type IDs.

eCommerce

Bug	Description
LO-5011	The PREMIUM_MAX_IMAGE_WIDTH Site Option and Global eCommerce settings do not override the default maximum image width of 150px A new Site Option now allows you to override the default maximum image width for eCommerce images in catalog and details. Set the PREMIUM_PRODUCT_DETAILS_MAX_IMAGE_WIDTH Site Option to a maximum width to control the sizing of images on the product details page. The default is 150 pixels.

Bug

Description

LO-5011

The PREMIUM_MAX_IMAGE_WIDTH Site Option and Global eCommerce settings do not override the default maximum image width of 150px

A new Site Option now allows you to override the default maximum image width for eCommerce images in catalog and details.

Set the PREMIUM_PRODUCT_DETAILS_MAX_IMAGE_WIDTH Site Option to a maximum width to control the sizing of images on the product details page. The default is 150 pixels.

Bug	Description
LO-4708	Remove "Sender ID" from Sender Policy Framework (SPF) error message The in-product message prompt that displays when there is an issue with the domain name used for an email message was updated to remove "Sender ID" since that technology is no longer used. The previous message stated: "Error: Sender ID/Sender Policy Framework: The domain name in the From address you used for this email is not configured to identify Convio as an authorized sender." The new message states: "The domain name in the From address used for this email doesn't identify Luminate Online as an authorized sender. To ensure your email is not mistaken for spam, review the Luminate Online information in the SPF Sender Authentication Help, then update your SPF protocol."
LO-4955	Some Hard Bounces are being logged as Soft bounces in the email log An update was made to log specific error codes as hard bounces.

Bug

Description

LO-4708

Remove "Sender ID" from Sender Policy Framework (SPF) error message

The in-product message prompt that displays when there is an issue with the domain name used for an email message was updated to remove "Sender ID" since that technology is no longer used.

The previous message stated: "Error: Sender ID/Sender Policy Framework: The domain name in the From address you used for this email is not configured to identify Convio as an authorized sender."

The new message states: "The domain name in the From address used for this email doesn't identify Luminate Online as an authorized sender. To ensure your email is not mistaken for spam, review the Luminate Online information in the SPF Sender Authentication Help, then update your SPF protocol."

LO-4955

Some Hard Bounces are being logged as Soft bounces in the email log

An update was made to log specific error codes as hard bounces.

Payments

Bug	Description
LO-4947	Blackbaud Merchant Services Credit Card Updater does not process some card updates An issue was resolved with Blackbaud Merchant Services Credit Card Updater so now cards are updated correctly through Blackbaud Merchant Services and Luminate Online.

Bug

Description

LO-4947

Blackbaud Merchant Services Credit Card Updater does not process some card updates

An issue was resolved with Blackbaud Merchant Services Credit Card Updater so now cards are updated correctly through Blackbaud Merchant Services and Luminate Online.

TeamRaiser

Bug	Description
LO-3845	TeamRaiser Coaching Emails filter out intended recipients TeamRaiser Coaching Emails targeting specific members chosen from the Team Membership Filters are sent to the intended audience as expected.
LO-4805	The event donation form URL on the TeamRaiser status page uses lower-case characters for proxy information causing issues with soft credits The event donation form URL on the TeamRaiser status page now uses upper-case characters for proxy ID and type to ensure that soft credits are recorded properly.
LO-4894	Facebook Fundraising donations are unsuccessful in reaching Luminate Online Donors donating to a Facebook Fundraiser integrated with TeamRaiser no longer see the following error message when attempting to donate: "A temporary problem occurred while trying to complete your request. Please try again later."
LO-4912	Secure Luminate Online configuration does not set TRC servlet to Secure Logged-in TeamRaiser registrants who visit a secure (HTTPS) TeamRaiser site that uses the S39 S-Tag are now directed to a Participant Center after clicking a link for an event, instead of a user log in page.