Luminate Online Version 25 Release Notes

Warning: Take action now to adopt the new checkout feature to meet Payment Card Industry (PCI) standards effective March 2025. Adopt the new checkout offering by February 15. For information, see the Checkout FAQs and step-by-step guidance in Update your Checkout Experience.

Tip: Register for a live workshop webinar to walk through these changes.

Version 25.1.1 Release Notes

January 2025

The Luminate Online 25.1.1 release includes security enhancements, product updates, and resolved issues.

What's New

Good Move

Child TeamRaiser Blueprints now display in the Good Move Notification Manager.

Team page updates now automatically send to Good Move, including the team story and photo.

Personal page updates now automatically send to Good Move, including a participant's page title, story, and photo.

New Checkout support Action required before March 2025

Tip: New eLearnings for checkout are available now! See Level Up with Luminate Online.

The following areas of Luminate Online now support the new checkout payment process. Canadian currency is also supported.

You must take action to update ALL areas of payment processing to use the new checkout payment processor. Make changes by February 15, 2025 to ensure you meet the March 2025 PCI compliance date.

Ticketed Events

Payments for ticketed events can now launch the new checkout feature. To configure your ticketed event for checkout, select a checkout-enabled merchant account on the Edit ticket information step of the event configuration.

eCommerce

Store purchases can now launch the new checkout feature. To configure your eCommerce store for checkout, select a checkout-enabled merchant account on the Store Administration configuration page.

Personal Fundraising

Payments and donations for personal fundraising campaigns can now use the new checkout feature. To configure personal fundraisers to use the new checkout, select a checkout-enabled merchant account in the personal fundraising campaign configuration.

Donations Classic

The new checkout feature is now supported in Donations Classic for online gifts. Offline gifts will be available in a future release. To configure Donations Classic forms to use the new checkout, select a checkout-enabled merchant account in the donation form configuration.

Embed a Donate Button

When using the Embed a Donate Button feature, the new checkout modal launches to guide donors through the payment process. The initial window now requires the following fields to meet PCI v4 and California AB 488 requirements:

Email

First name

Last name

Zip code

Country

To use the new checkout in the Donate button, use the code found in the Publish step from a donation form and campaign configured for the new checkout.

S1300 Tag Version of Blackbaud Checkout

When using the S1300 Tag version of Blackbaud Checkout, the new checkout feature now launches when using a donation form that is configured for new checkout and is in a campaign that is configured for the new checkout. Donors must now provide additional information before continuing. These new required fields enable the payment to meet PCI v4 and California AB 488 requirements:

Email

First name

Last name

Zip code

Country

After entering this information, donors select "Give securely" to launch the new checkout modal.

To use the new checkout in the S1300 Tag version of Blackbaud Checkout, reference a donation form ID of a donation form and campaign configured for the new checkout.

Event Manager Center

The Event Manager Center now supports the new checkout feature wherever payments are taken by Event Managers and Company Coordinators.

Improved Checkout Support for California Assembly Bill (AB) 488

The checkout process was enhanced to fully support compliance with California AB 488.

Resolved Issues

Issues were resolved in: Donations | Email | Events | Reports | System | TeamRaiser

Donations

Bug Description

3080276

Recurring pledge updates no longer include an updated modify date on the recurring pledge record resulting in sync issues with Luminate Web Services or other custom sync

Recurring pledge updates once again include an updated modify date on the recurring pledge record.

3141124

When donating on a single page standard designated giving donation form, selecting the button to calculate causes the amount entered to become "0" in modal

When donating on a single page, standard, designated giving donation form, selecting the button to calculate shows the correct calculated amount.

3143324

In a responsive donation form that uses the Checkout embedded data element at the top of the form, the digital wallet button appears at the bottom

The digital wallet button now appears in the same location as the Checkout embedded element.

3143411

In a standard or responsive donation form that uses the Checkout embedded element, digital wallets amounts are not updated a second time after closing and reopening the window

When closing and reopening a standard or responsive donation form that uses the Checkout embedded element, the updated amount is correctly reflected on the digital wallet screen.

3144684

The characters, "/>, appear on the Transaction summary screen when native Paypal is used with a checkout-enabled, multipage form

When using native Paypal on a multipage donation form enabled with checkout, no extra characters appear on the Transaction summary screen.

3156008

On a single-page donation form that uses checkout and provides a custom amount field, invalid decimal digits that are entered in the field, such as 12.123.232, open with a different gift amount instead of giving an error

Single-page donation forms that use checkout and provide a custom amount field now validate the decimal placement in the field and show an error if the amount is incorrect.

3156940

Some administrative pages and the Gift Service Center can result in a Page Not Found error due to page redirect security measures with NEXTURL blocking/sanitization

Updates were made to ensure that while continuing to maintain secure page redirects, administrators and constituents can still access Luminate Online pages.

3160472

After closing and reopening the modal checkout window, the modal is slow to reload and does not fully render

When closing and reopening the Checkout modal window, the checkout modal loads without delay and reflects any updated amount correctly.

3167414

When entering a custom donation amount in a custom amount field, the decimal point is removed on checkout-enabled forms

Gift amounts that include a decimal placement are validated and retained on a custom amount field on checkout-enabled forms.

3177573

The Checkout embedded element can break some HTML elements in a form causing issue with the form closing

When Checkout embedded is added to a donation form, the <div id=main-content> tag no longer causes the payment element to merge into the page wrapper, so the form now closes as expected.

3181409

Following the 24.5.1 release, some donation forms with custom code prevents the custom donation amount field to stop working which prevents submission of the donation form

Donation forms with custom code can now include a custom amount field for the donor to enter an amount of their choosing and submit the form.

Email

Bug Description

3048639

Some hard bounced email addresses receive email sends

All email addresses marked as hard bounced are filtered out of email sends.

Events

Bug Description

3085837

Duplicate Calendar Event ticket purchase notifications are sent to administrators if the constituent refreshes the page or goes back to print a confirmation

When an administrator configures notices to be sent when a Calendar Event ticket purchase is made, only one notice is sent to the administrator, even if the constituent refreshes the page or goes back to a previous page.

Reports

Bug Description

3098352

In Report Writer, the Transaction Details report shows whole numbers only for transaction and sustained giving information fields instead of amounts that include decimal numbers

The transaction and sustained giving amounts shown in the Transaction Details report results match the amount shown on a constituent record or mail merge.

System

Bug Description

3080274

When working as an administrator in Luminate Online, text can display in a language other than English

Administrator-facing text in Luminate Online displays in English except when in Preview which displays the language defined in the SITE_DEFAULT_LOCALE Site Option.

3115241

When using an authentication app for multi-factor authentication to log into Luminate Online, the IP address is not added to the allow list which results in the administrator needing to enter a code upon each login instead of once every 30 days from a particular location

Using an authentication app, or Time-based One-Time Password (TOTP) for multi-factor authentication now updates the IP address to the allow list so that a code is not required again for another 30 days.

3118436

The "if" tags in the S48 S-Tag are not counting external confirmed donations such as Facebook gifts

The "if" tags in the S48 S-Tag now include external confirmed donations such as Facebook gifts.

3126669

In a customized autoresponder email for a Survey, the S1 S-Tag does not render data in the subject line but does work in the email body

When editing an autoresponder for a Survey, you can now use the S1 Tag in the subject line to render data such as a first name.

3127033

In a customized Donation Full Refund autoresponder email, using the S120 Tag parameter, S120:dc:refundAmount, does not render an amount in the sent email, even though it displays in the preview

In a customized Donation Full Refund autoresponder, the S120 S120:dc:refundAmount parameter displays the refund amount in a live version of the email.

TeamRaiser

Bug Description

3035471

In certain cases, a browser session allows a TeamRaiser participant to create a team in a TeamRaiser that doesn't allow new teams

When two TeamRaiser events—one that allows new teams and one that does not—are opened in different browser tabs, registering for the event that does not allow teams does not allow for team creation.

3085782

TeamRaiser Follow-Up Autoresponders do not appear in the Interaction Summary or Autoresponders Sent list

TeamRaiser Follow-up Autoresponders now appear in the Interaction Summary and Autoresponder Sent lists after they are sent.

3112642

When organizational gifts are disabled, a Technical Difficulties error occurs when attempting to confirm a Local Company Gift

In TeamRaiser's Local Companies tab, links to Confirm or Reject now display only once for unconfirmed Local Company gifts, and not at all for confirmed gifts.

3118494

In TeamRaiser, URL shortcuts should reflect HTTPS not HTTP

URL shortcuts in TeamRaiser, including the Participant Center, now use HTTPS instead of HTTP.

3123253

In TeamRaiser, a duplicated participation type or group prevents a blueprint but the error does not describe the problem

When a participation type or group name already exists, pushing a blueprint no longer fails and uses a different variation of the participation type or group name by appending an asterisk to the end of the name.

For example, if a parent blueprint has a participant type named 'abc' (id: 1) and the child event renames this to 'xyz' (id:2) and creates an additional type of 'abc' (id:3), then after pushing changes on the parent blueprint, the names will result in:

abc (id:3) -> abc*

xyz (id:2)-> abc

That is, before changing back a participant type name to its parent participant type name, it resolves the conflicting name by appending an (*) to the existing one.

3142711

In Participant Center 2, importing contacts from Google Gmail is not working

You can once again import contacts from Google Gmail into the Participant Center.

3160480

On a two-step Delayed Self Pledge installment form that uses the new checkout modal, the checkout modal does not include the gift amount so the gift cannot be processed

Gift amounts appear and successfully process on two-step Delayed Self Pledge installment forms that use the new checkout payment modal.

Bug	Description
3080276	Recurring pledge updates no longer include an updated modify date on the recurring pledge record resulting in sync issues with Luminate Web Services or other custom sync Recurring pledge updates once again include an updated modify date on the recurring pledge record.
3141124	When donating on a single page standard designated giving donation form, selecting the button to calculate causes the amount entered to become "0" in modal When donating on a single page, standard, designated giving donation form, selecting the button to calculate shows the correct calculated amount.
3143324	In a responsive donation form that uses the Checkout embedded data element at the top of the form, the digital wallet button appears at the bottom The digital wallet button now appears in the same location as the Checkout embedded element.
3143411	In a standard or responsive donation form that uses the Checkout embedded element, digital wallets amounts are not updated a second time after closing and reopening the window When closing and reopening a standard or responsive donation form that uses the Checkout embedded element, the updated amount is correctly reflected on the digital wallet screen.
3144684	The characters, `"/>`, appear on the Transaction summary screen when native Paypal is used with a checkout-enabled, multipage form When using native Paypal on a multipage donation form enabled with checkout, no extra characters appear on the Transaction summary screen.
3156008	On a single-page donation form that uses checkout and provides a custom amount field, invalid decimal digits that are entered in the field, such as 12.123.232, open with a different gift amount instead of giving an error Single-page donation forms that use checkout and provide a custom amount field now validate the decimal placement in the field and show an error if the amount is incorrect.
3156940	Some administrative pages and the Gift Service Center can result in a Page Not Found error due to page redirect security measures with NEXTURL blocking/sanitization Updates were made to ensure that while continuing to maintain secure page redirects, administrators and constituents can still access Luminate Online pages.
3160472	After closing and reopening the modal checkout window, the modal is slow to reload and does not fully render When closing and reopening the Checkout modal window, the checkout modal loads without delay and reflects any updated amount correctly.
3167414	When entering a custom donation amount in a custom amount field, the decimal point is removed on checkout-enabled forms Gift amounts that include a decimal placement are validated and retained on a custom amount field on checkout-enabled forms.
3177573	The Checkout embedded element can break some HTML elements in a form causing issue with the form closing When Checkout embedded is added to a donation form, the <div id=main-content> tag no longer causes the payment element to merge into the page wrapper, so the form now closes as expected.
3181409	Following the 24.5.1 release, some donation forms with custom code prevents the custom donation amount field to stop working which prevents submission of the donation form Donation forms with custom code can now include a custom amount field for the donor to enter an amount of their choosing and submit the form.

Bug	Description
3080274	When working as an administrator in Luminate Online, text can display in a language other than English Administrator-facing text in Luminate Online displays in English except when in Preview which displays the language defined in the SITE_DEFAULT_LOCALE Site Option.
3115241	When using an authentication app for multi-factor authentication to log into Luminate Online, the IP address is not added to the allow list which results in the administrator needing to enter a code upon each login instead of once every 30 days from a particular location Using an authentication app, or Time-based One-Time Password (TOTP) for multi-factor authentication now updates the IP address to the allow list so that a code is not required again for another 30 days.
3118436	The "if" tags in the S48 S-Tag are not counting external confirmed donations such as Facebook gifts The "if" tags in the S48 S-Tag now include external confirmed donations such as Facebook gifts.
3126669	In a customized autoresponder email for a Survey, the S1 S-Tag does not render data in the subject line but does work in the email body When editing an autoresponder for a Survey, you can now use the S1 Tag in the subject line to render data such as a first name.
3127033	In a customized Donation Full Refund autoresponder email, using the S120 Tag parameter, `S120:dc:refundAmount`, does not render an amount in the sent email, even though it displays in the preview In a customized Donation Full Refund autoresponder, the S120 `S120:dc:refundAmount` parameter displays the refund amount in a live version of the email.

Bug	Description
3035471	In certain cases, a browser session allows a TeamRaiser participant to create a team in a TeamRaiser that doesn't allow new teams When two TeamRaiser events—one that allows new teams and one that does not—are opened in different browser tabs, registering for the event that does not allow teams does not allow for team creation.
3085782	TeamRaiser Follow-Up Autoresponders do not appear in the Interaction Summary or Autoresponders Sent list TeamRaiser Follow-up Autoresponders now appear in the Interaction Summary and Autoresponder Sent lists after they are sent.
3112642	When organizational gifts are disabled, a Technical Difficulties error occurs when attempting to confirm a Local Company Gift In TeamRaiser's Local Companies tab, links to Confirm or Reject now display only once for unconfirmed Local Company gifts, and not at all for confirmed gifts.
3118494	In TeamRaiser, URL shortcuts should reflect HTTPS not HTTP URL shortcuts in TeamRaiser, including the Participant Center, now use HTTPS instead of HTTP.
3123253	In TeamRaiser, a duplicated participation type or group prevents a blueprint but the error does not describe the problem When a participation type or group name already exists, pushing a blueprint no longer fails and uses a different variation of the participation type or group name by appending an asterisk to the end of the name. For example, if a parent blueprint has a participant type named 'abc' (id: 1) and the child event renames this to 'xyz' (id:2) and creates an additional type of 'abc' (id:3), then after pushing changes on the parent blueprint, the names will result in: abc (id:3) -> abc* xyz (id:2)-> abc That is, before changing back a participant type name to its parent participant type name, it resolves the conflicting name by appending an (*) to the existing one.
3142711	In Participant Center 2, importing contacts from Google Gmail is not working You can once again import contacts from Google Gmail into the Participant Center.
3160480	On a two-step Delayed Self Pledge installment form that uses the new checkout modal, the checkout modal does not include the gift amount so the gift cannot be processed Gift amounts appear and successfully process on two-step Delayed Self Pledge installment forms that use the new checkout payment modal.