Luminate Online Version 25 Release Notes

Warning: Take action now to update payment processing areas with checkout. Get step-by-step guidance in Update your Checkout Experience.

Note: March 13: The full requirements of PCI 4.0 will begin to be enforced on March 31, 2025. Your organization has its own PCI audit date to comply with those requirements. To ensure your organization is ready, update all of your payment forms before your PCI audit date. To ensure that Blackbaud is compliant before Blackbaud's audit, we will run an Auto-Compliance Migration Script from May 1-16th to enforce payment processing updates. The script will update allunchanged forms with the checkout modal, potentially causing layout and processing changes. This script cannot update API forms, which you must manually update. See Auto Migration FAQs.

Release 25.2

Release 25.1.1

Tip: You can access concise eLearning modules that guide you through payment changes on Level Up with Luminate Online. You can also register for an on-demand workshop recording on the payment updates.

Version 25.2 Release Notes

March 2025

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

Note: Version upgrades for TinyMCE (Content Editor/WYSIWYG), jQuery, and PrototypeJS are planned for the 25.3 release.

Product Updates

Checkout support for recurring gift updates

Sustaining donors updating their billing or gift information in the Gift Service Center for a gift associated with a checkout donation form will see classic Blackbaud Checkout to complete their update. This update ensures PCI v4 compliance and applies to the original and current versions of Gift Service Center and supports Canadian currency.

Note: Donors who update billing information or recurring gifts on non-checkout donation forms will not see a change until May 1 when credit card fields will no longer be available on non-checkout donation forms.

We've also introduced new API methods, updateRecurringCheckoutPaymentInfo and validateRecurringCheckoutPaymentInfo, to support updates made by a logged-in user.

In Luminate Online, administrators making updates on a sustaining donor’s behalf in Sustaining Gifts area of Donation Management now also see classic Blackbaud Checkout modal when completing updates on a form enabled with checkout. See Update Sustaining Gift Payment Details.

Digital wallet button placement in embedded checkout

When a supporter chooses a digital wallet payment option on a form with embedded checkout, the button to process the payment now appears centered below the billing fields.

Checkout Support for Offline Gifts in Donation Classic

Offline gifts in Donation Classic now support the new checkout payment processing feature, expanding on the online support offered in the 25.1.1 release. This update includes support of Canadian currency.

To configure offline forms in Donations Classic for checkout, select a checkout-enabled merchant account in the donation form configuration. After the update, the checkout modal will appear for payment processing.

For more details, see Checkout in Donation Classic.

PayPal and Blackbaud Transaction ID

To help with reconciliation between PayPal and Blackbaud transactions, PayPal now displays the Blackbaud Transaction ID under the custom_ID category when viewing a Blackbaud transaction in your PayPal business account. Previously, the custom_ID value displayed "Blackbaud."

API Documentation Updates

To enhance payment updates for the checkout process, we've introduced new APIs:

updateRecurringCheckoutPaymentInfo - This method, designed for the Gift Service Center, allows logged-in users to update their credit card information for recurring gifts using a secure token.

validateRecurringCheckoutPaymentInfo - Also supporting the Gift Service Center, this method ensures all required values are provided when updating payment information for logged-in users.

donateACH - This method processes direct bank debits through the United States Automated Clearing House (ACH) and Canadian Automated Clearing Settlement System (ACSS) with legacy merchant accounts.

Continued support of Legacy Blackbaud Checkout

To allow for the use of Legacy Blackbaud Checkout to continue so your customizations can persist in forms, we've updated our infrastructure to ensure that you can use the Legacy Blackbaud Checkout, launched with the S1300 tag, within a checkout-enabled campaign and form.

See Checkout using the S1300 Tag.

Credit Card Updater shows last attempted card update

With Credit Card Updater, you can now see whether the last attempted card update was successful in the Blackbaud Merchant Services Web Portal. This information is helpful to know when to contact a donor for updated card information.

In the Blackbaud Merchant Services Web Portal, go to Reports, Credit card updater. Under Status, you'll see the whether a card was marked as Updated or Could not update.

For more information, see Credit Card Updater in the Blackbaud Merchant Services documentation and Credit Card Updater Service in the Luminate Online documentation.

Resolved Issues

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

Donations

Bug	Description
3096784	In the Gift Service Center, when a donor updates their billing information and the recurring gift amount at the same time, the billing information is updated but the recurring gift charge remains the original amount Donors can now visit the Gift Service Center and successfully make an update to their billing information and recurring gift amount within the same update.
3185633	Some one-time and recurring gifts are declined due to California Assembly Bill 488, even though they originate from Canadian zip codes Donations coming from a Canadian zip code are no longer suppressed when an organization is in a bad state in regards to California Assembly Bill 488.
3187227	The Luminate Online API method, validateDonateCheckout, does not validate all required fields in the ghost form When validate=true is included in the call, the validateDonateCheckout API method now validates each required field in the standard donation form that is used as the ghost (or background) donation form for a customized, API donation form.
3189562	In rare cases, when attempting to donate to a form using the new checkout modal, donations are not accepted when choosing a defined amount, but succeed when manually entered. Other times, they decline with the error, "Error: Amount exceeds maximum transaction limit." On forms customized with a donation amount placeholder, the checkout modal now loads without error.
3195765	Remove California law check for cash and check transactions An update was made to ensure that the enforcement of California Assembly Bill 488 does not limit the recording of cash or check transactions.
3195803	NaN is displayed as amount for offline ticketed events fr_CAs When in the French Canadian (fr_CA) locale and working with offline ticketed event transactions, the total amount displays as expected.
3199414	Entering an invalid amount in a basic donation form that includes Suggested Levels processes the transaction but displays an error An update was made to prevent an invalid amount from being passed through a donation form.
3201530	Although support for recurring PayPal and Venmo gifts is not yet available in the new checkout, the embedded element on a 2-page or greater donation form shows PayPal as an option when selecting recurring gift options Support for recurring gifts via PayPal and Venmo in the new checkout will be available in an upcoming release. Until that support is available, the options of PayPal or Venmo do not display when a monthly gift is selected on a checkout donation form.
3202470	On a checkout embedded donation form that uses a merchant account configured for classic PayPal and checkout, the Google Pay option displays after switching from Credit Card to PayPal On a checkout embedded donation form that uses a merchant account configured for classic PayPal and checkout, the Google Pay option no longer displays after switching from Credit Card to PayPal.
3207307	When modifying a sustaining gift as an administrator, a Technical Difficulties error occurs Administrators who do not have permission to update a sustaining gift no longer see the option to edit a recurring gift.
3208651	On a responsive donation form, the checkbox to use the same donor information as the billing information does not autofill the fields On a responsive donation form, the checkbox to use the same donor information as the billing information autofills the fields as expected.
3208849	On a multi-page, responsive or standard donation form that uses checkout, the Transaction Summary does not display on the last page and is blank When the Transaction Summary data element is included on a checkout-enabled standard or responsive donation form, the Transaction Summary displays to the donor.
3219286	Direct Debit is missing on offline forms using new checkout When entering an offline transaction on a constituent record, direct debit is available as a payment option for forms configured with new checkout.
3227419	Unable to refund PayPal transactions in Luminate Online with the new Checkout experience due to the error, "Failed to Process Refund - Please contact Support" You can now refund PayPal transactions successfully within Luminate for transactions made with the new Checkout modal. Note: This resolution has already shipped and is available now.
3233935	On a checkout-enabled form with custom JQuery code, attempting to pay for a TeamRaiser registration can encounter an error in the billing information area, such as "We are experiencing temporary difficulties with the payment network. Please try again later." Paid TeamRaiser registration forms successfully complete when the form has custom JQuery code and is enabled with the configuration option, Donations 2 Registration Transaction Processing.
3234987	On a donation form using the S1300 version of checkout modal, the Give Securely button cannot be clicked after closing the modal On a donation form using the S1300 S-tag version of checkout modal, the Give Securely button is able to be selected after closing the modal.
3235268	Update the embedded to display digit wallet buttons correctly We need to update the embedded form to display the correct buttons on the donation form. If we use Credit card or Direct Debit option, then it should display the `Process` or Donate or whatever button is used to submit the donation. If any of the digital wallet option is selected then this button should be swapped by the digital wallet button. If credit card or direct debit payment method is selected then we should see the LO button name that is being used. If any one of digital wallet is used then it should display the digital wallet button name.
3236122	Checkout modal does not launch in Ticketed event because the Transaction ID was not found with the error, "We're sorry. Your transaction did not complete successfully." Updates were made to a customized template so that the checkout modal processes the Ticketed Event transactions successfully.
3236647	On a checkout embedded form, the Direct Debit Mandate shows on forms in the United States when selecting recurring direct debit payments when it should be for the United Kingdom A review has confirmed that the direct debit recurring gift mandate is applicable not only in the United Kingdom but also in the United States to comply with Nacha regulations. This mandate must be displayed to recurring gift donors as required.
3239645	Transactions processed through a checkout-enabled form can sometimes have a different reference number between Blackbaud Merchant Services and Luminate Online Transactions that process through a checkout-enabled form now have a matching Luminate Online reference number (`valued_transaction.reference_number`) and Blackbaud Merchant Services reference number (`REFERENCE_NUMBER`).
3243613	When using checkout and classic PayPal on a TeamRaiser registration form, redirecting to an external payment site does not work unless the message box is closed and the Process button is selected When selecting classic PayPal on a checkout-enabled TeamRaiser registration form, the redirect to the external payment site is successful.
3247275	Not all pages in the checkout modal show in Spanish Although multi-language support for the checkout modal is on the way, currently, all pages are displayed in English. This update addresses the mixed-language issue by ensuring that the modal pages are shown exclusively in English.
3248388	Unable to select direct debit in the Checkout embedded data element configuration until the donation form's campaign is configured to use the checkout merchant account When editing the Checkout embedded donation data element, you can now select the option for direct debit even if the donation form's campaign is not yet configured to use the checkout-enabled merchant account.
3248407	On a Calendar Ticketed Event or in eCommerce, PayPal and Venmo do not show as a payment option when the merchant account is enabled with the new checkout Calendar Ticketed Events and eCommerce checkout processing now include PayPal and Venmo as payment options.
3249744	On a checkout-enabled donation form using a merchant account that supports new checkout and Classic PayPal Direct, the Process button does not load correctly when selecting credit card after selecting PayPal On a checkout-enabled donation form using a merchant account that supports new checkout and Classic PayPal, the Process button loads correctly after selecting Paypal then selecting a different payment option.
3250771	On a constituent's Transactions tab, Venmo transactions show as "PayPal" In Constituent360, when viewing the Transactions tab for a constituent, Venmo transactions show as "Venmo."
3255045	Using `donateCheckout` API results in occasional "404" errors when connecting to payments In this instance, the error occurred because `donateCheckout` was used without first calling `getDonationFormInfo` or `getTeamRaiserConfig` to retrieve required values, such as `zone`, before passing payment information. To avoid errors, call `getDonationFormInfo` or `getTeamraiserConfig` before `donateCheckout` on your API forms. Documentation update was made in donateCheckout to list the order of API methods and data flow, and in the Troubleshooting Checkout FAQs, the following entry was added: Feb 19, 2025: Why is the donateCheckout API returning, "Error: There was a problem encountered while processing your donation"? Sometimes, the donateCheckout API method can result in the error, "There was a problem encountered while processing your donation," when the payment zone is not passed as an argument in the method. When this occurs, transactions will not process and the call gives a 404 error that the resource is not found. To resolve this, ensure that you first execute either getDonationFormInfo or getTeamraiserConfig before calling donateCheckout.
3258384	ACH recurring donations are not assigned a reference number creating multiple issues - reporting/relo syncing/refunding/constituent matching Recurring gifts made via ACH through the new checkout feature are now assigned a Reference Number.
3261673	Checkout modal formatting is not displaying correctly on mobile devices The checkout modal donation form now loads with centered formatting and appropriate size on mobile devices and small screens. Note: This resolution has already shipped and is available now.
3271124	The Sustaining Gift Credit Card Update screen shows an error when modifying a recurring gift In Fundraising, Donation Management, Sustaining Gifts, the credit card type selection options are now removed, and you can once again use the Enter New Credit Card option to update the credit card.

Bug Description

Bug	Description
3021533	Email sent from a Participant Center shows an unexpected sender address We've introduced a new Site Option that allows the product to use the sender email address specified in the TeamRaiser configuration instead of the site-wide sender email address set in the NOTIF_FROM site option. By default, emails sent from a Participant Center use the sender address defined by the NOTIF_FROM site option. Now, if you prefer to use the sender email address configured in the TeamRaiser settings, you can enable this new site option. To use the event-specific sender email address instead of the site-wide setting, follow these steps: 1. Go to Setup, then Site Options. 2. Click Go. 3. Find PC_EMAIL_USE_EVENT_LEVEL_SENDER_EMAIL_ADDR. 4. Set the value to `TRUE` and save. Next, set the sender email address in the TeamRaiser event: 1. In Fundraising, TeamRaiser, Edit the TeamRaiser event. 2. Go to Edit Event Options, Advanced Event Options, Define Event Options, Sender Address. 3. Add the desired sender email address and save your changes. Now, if a sender email is specified in the TeamRaiser event configuration, emails will use that address. If not, the site-wide setting is used. For multi-center sites, if an email address is specified for a center, that address is used. If neither the event nor the center have a specified email address, the site-wide value set in the NOTIF_FROM site option is used.
3125634	When selecting an end date for a recurring delivery of a classic email message, the day of the week does not match the date selected When configuring the end date for a recurring email delivery, the day of the week shown matches the date selected.
3238169	In the 25.1 release with JQuery 3.7.1 enabled, the Cancel button for scheduled emails does not work We've made an update to ensure that when jQuery 3.7.1 is implemented in the 25.3 release, the Cancel button for scheduled emails works as expected.

3021533

Email sent from a Participant Center shows an unexpected sender address

We've introduced a new Site Option that allows the product to use the sender email address specified in the TeamRaiser configuration instead of the site-wide sender email address set in the NOTIF_FROM site option.

By default, emails sent from a Participant Center use the sender address defined by the NOTIF_FROM site option. Now, if you prefer to use the sender email address configured in the TeamRaiser settings, you can enable this new site option.

To use the event-specific sender email address instead of the site-wide setting, follow these steps:

1. Go to Setup, then Site Options.

2. Click Go.

3. Find PC_EMAIL_USE_EVENT_LEVEL_SENDER_EMAIL_ADDR.

4. Set the value to TRUE and save.

Next, set the sender email address in the TeamRaiser event:

1. In Fundraising, TeamRaiser, Edit the TeamRaiser event.

2. Go to Edit Event Options, Advanced Event Options, Define Event Options, Sender Address.

3. Add the desired sender email address and save your changes.

Now, if a sender email is specified in the TeamRaiser event configuration, emails will use that address. If not, the site-wide setting is used. For multi-center sites, if an email address is specified for a center, that address is used. If neither the event nor the center have a specified email address, the site-wide value set in the NOTIF_FROM site option is used.

3125634

When selecting an end date for a recurring delivery of a classic email message, the day of the week does not match the date selected

When configuring the end date for a recurring email delivery, the day of the week shown matches the date selected.

3238169

In the 25.1 release with JQuery 3.7.1 enabled, the Cancel button for scheduled emails does not work

We've made an update to ensure that when jQuery 3.7.1 is implemented in the 25.3 release, the Cancel button for scheduled emails works as expected.

Events

Bug	Description
3239549, 3238203	Unable to Copy events You can once again Copy an event.
3240455	In the 25.1 release with jQuery 3.7.1 enabled, event ticket type re-ordering does not work We've made an update to ensure that when jQuery 3.7.1 is implemented in the 25.2 release, event ticket type re-ordering works as expected.

Bug

Description

3239549, 3238203

Unable to Copy events

You can once again Copy an event.

3240455

In the 25.1 release with jQuery 3.7.1 enabled, event ticket type re-ordering does not work

We've made an update to ensure that when jQuery 3.7.1 is implemented in the 25.2 release, event ticket type re-ordering works as expected.

Good Move

Bug	Description
3140578	Unable to remove Good Move Download widget from the Thank You page You can now delete the Download Good Move component from a Thank You page.
3157906	Apostrophes in Good Move show in the app as â€™m Apostrophes display as expected the Good Move app.
3211310	Push notifications send upside down ? in alert details to Good Move when a customer uses ' or ; special characters Special characters that are used in push notification content display in the Good Move app as they are written by the administrator.

Bug

Description

3140578

Unable to remove Good Move Download widget from the Thank You page

You can now delete the Download Good Move component from a Thank You page.

3157906

Apostrophes in Good Move show in the app as â€™m

Apostrophes display as expected the Good Move app.

3211310

Push notifications send upside down ? in alert details to Good Move when a customer uses ' or ; special characters

Special characters that are used in push notification content display in the Good Move app as they are written by the administrator.

Integration

Bug	Description
3143393	Creating a custom donation data element with a name that is already in use causes query problems with Luminate Web Services The system now prevents the creation of custom donation data elements that use a name already in use.
3258384	ACH recurring gifts are unable to sync to Raiser's Edge integration, and Queue Problem Management shows the error, "Unable to find RecurringPledgeID by reference" We've made an update to ensure that all records contain a reference number so that data syncs to Raiser's Edge complete successfully.

Bug

Description

3143393

Creating a custom donation data element with a name that is already in use causes query problems with Luminate Web Services

The system now prevents the creation of custom donation data elements that use a name already in use.

3258384

ACH recurring gifts are unable to sync to Raiser's Edge integration, and Queue Problem Management shows the error, "Unable to find RecurringPledgeID by reference"

We've made an update to ensure that all records contain a reference number so that data syncs to Raiser's Edge complete successfully.

Reports

Bug	Description
3177801	Some reports do not include transaction details for payments made with digital wallets through the new checkout solution Digital wallet transactions coming through the new checkout solution are fully captured in reporting as expected. The Transactions Details report no longer contains blank transaction fields, and the Donations by Transaction report includes all transaction data. The populated data also addresses issues with the Raiser's Edge-Luminate Online (RELO) data sync. In reports, the Tender Type shows as XCheckout to indicate it is not a credit card payment. The Tender Instance (Payment Method) indicates the payment type, such as Apple Pay, Google Pay, Venmo, etc.
3234011	The Donation by Form report does not consistently complete on sites with large volumes of data The Donation by Form report now successfully handles large volumes (millions of rows) of data. The documentation for the Donations by Form report was updated to recommend filtering data to limit results instead of using the "All Dates" default for large datasets.

Bug

Description

3177801

Some reports do not include transaction details for payments made with digital wallets through the new checkout solution

Digital wallet transactions coming through the new checkout solution are fully captured in reporting as expected. The Transactions Details report no longer contains blank transaction fields, and the Donations by Transaction report includes all transaction data. The populated data also addresses issues with the Raiser's Edge-Luminate Online (RELO) data sync.

In reports, the Tender Type shows as XCheckout to indicate it is not a credit card payment. The Tender Instance (Payment Method) indicates the payment type, such as Apple Pay, Google Pay, Venmo, etc.

Transaction report data showing Tender Type and Name

3234011

The Donation by Form report does not consistently complete on sites with large volumes of data

The Donation by Form report now successfully handles large volumes (millions of rows) of data.

The documentation for the Donations by Form report was updated to recommend filtering data to limit results instead of using the "All Dates" default for large datasets.

TeamRaiser

Bug	Description
3024500	When approving multiple TeamRaiser Personal Pages in a single browser session, the first page visited appears across all events In TeamRaiser, visiting different Personal Pages for approval no longer encounters issues when the approvals are done in the same browser session.
3134430	Attempting to change the soft credit on an eCommerce purchase for TeamRaiser causes an error Applying a soft credit on an eCommerce purchase in TeamRaiser correctly applies the credit.
3195764	Following the 24.5.1 release, an error occurs when attempting to do an offline registration while in the Canadian, fr_CA, locale When in the Canadian locale, you can now successfully complete an offline registration for a TeamRaiser event.
3236971	Custom TeamRaiser URLs do not work correctly after a template change added "/admin/" to the URL path Custom URLs in TeamRaiser no longer automatically include "/admin/" in the path so that links can redirect constituents as expected.

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

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

Warning: 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

Jan 30 Update: The use of Copy for Ticketed and RSVP events is now restored.

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.

After the update, the checkout modal will appear for payment processing.

See Checkout in Events.

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 Change the Store Merchant Account configuration page.

After the update, the checkout modal will appear for payment processing.

See Checkout in eCommerce.

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 in a new campaign, select a checkout-enabled merchant account in the personal fundraising campaign configuration.

To configure personal fundraisers to use the new checkout in an existing campaign, Edit the campaign, then select a checkout-enabled donation form and campaign in the edit campaign details section.

After the update, the checkout modal will appear for payment processing.

See Checkout in Personal Fundraising.

Donation Classic

The new checkout feature is now supported in Donation Classic for online gifts. Offline gifts will be available in a future release.

To configure Donation Classic forms to use the new checkout, select a checkout-enabled merchant account in the donation form configuration.

After the update, the checkout modal will appear for payment processing.

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 comply with guidelines and 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 that is associated with a campaign configured for the new checkout.

S1300 Tag Version of Blackbaud Checkout

With this release, you can either continue offering your existing configuration for the S1300 Tag version of Blackbaud Checkout or set up a new S1300 Tag form using the new checkout.

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.

See Checkout using the S1300 Tag.

New in this release, all donors must now provide the following additional information before continuing to payment to comply with guidelines and requirements:

Email

First name

Last name

Zip code

Country

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

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.

3189086

Toggling between embedded checkout and PayPal Direct results in an error when attempting to process the donation

Donors can select back and forth between the options of embedded checkout and PayPal Direct successfully.

3213503

When a donor fails to provide a required field in a form that uses Checkout embedded, the error is not easily visible at the top of the page

When a donor doesn't provide a value for a required field on a form that uses the embedded (inline) Checkout payment element, the page now adjusts to show the error message when the "Process" button is selected.

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.
3189086	Toggling between embedded checkout and PayPal Direct results in an error when attempting to process the donation Donors can select back and forth between the options of embedded checkout and PayPal Direct successfully.
3213503	When a donor fails to provide a required field in a form that uses Checkout embedded, the error is not easily visible at the top of the page When a donor doesn't provide a value for a required field on a form that uses the embedded (inline) Checkout payment element, the page now adjusts to show the error message when the "Process" button is selected.

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.