Known Issues in Luminate Online

January 2020

This document summarizes current known issues in Luminate Online. Each issue description includes a workaround if appropriate. After an issue is resolved, it is removed from this page and published as a Resolved Issue in the Luminate Online Release Notes.

Advocacy | Constituent360 | Donations | Email | Events | Facebook | Integration | MultiCenter | Open APIs | Payments | Personal Fundraising | Reports Classic | Report Writer | Surveys | TeamRaiser | WYSIWYG (Content Editor)

Advocacy

Issue Description
41832

Vote Center alerts only publish when the administrator clicks Next or Save in the Autoresponder process step.

43103

On the Request Letter Download, some target names display "Vacant Vacant" for legislators who have left office. T here is no workaround.

Constituent360

Issue Description
66710

The constituent record search does not distinguish between characters with diacritical marks, such as "ñ," and regular characters. The constituent record characters in the database must match the characters that are entered in the search field to return results.

For example, if the database has the name "José Piñera," then a search for "Jose Pinera" yields no results.

Donations

Issue Description
33162

In Donations Classic, the Enter a new gift or pledge drop-down in the Gift Entry section lists all Donations Classic forms, regardless of a form's status.

Email

Issue Description
59527

Custom autoresponders do not send when the sustaining gift is canceled by an administrator. When a sustaining gift is canceled by an administrator, only the default autoresponder sends to the constituent.

Events

Issue Description
48191

The Calendar tools used in Events and TeamRaiser's Event Search may not work in the Google Chrome browser.

Facebook

Issue Description
 

The Check your setup step of Facebook integration configuration incorrectly expects the Callback URL to be a secure administrative URL. A correctly-configured Callback URL (with a non-secure path to the "FB" servlet) results in an error.

Integration

Issue Description
57167

The hourly queue activity graph under Luminate Management can render very slowly when the time frame is larger than one day. Administrators should use the hourly queue activity graph with the time frame set to one day as a workaround.

57168

The daily queue activity graph under Luminate Management can report incorrect statistical information. This will be corrected in a future release. Administrators should use the hourly queue activity graph instead.

66958

TeamRaiser registrations that originate in Luminate CRM may cause an error message in Queue Problem Management.

MultiCenter

Issue Description
33712

When a center administrator adds a new constituent record in "All Centers" mode, it might not get added to any center and the administrator might not be able to view and edit the constituent record afterwards.

Open APIs

Issue Description
50874

The takeAction API cannot deliver messages to webforms that require constituents to complete an interactive challenge/response test (also known as CAPTCHA).

Because a significant amount of Federal Congressional webforms contain a CAPTCHA, as a workaround, direct constituents to the legislator's contact website to complete the webform manually.

The <url> element returned by getAdvocacyAlert contains the link to the recipient's contact website. The value of <interactive> indicates whether the URL links to a webform with a CAPTCHA, and, therefore, requires the workaround.

Payments

Issue Description
68109

In Service Center 2, changing the give amount of a sustaining gift may cause the Next Payment Date to move back one day.

Personal Fundraising

Issue Description
24583

When a partial refund for a Personal Fundraising Donation (formerly Tributes) is made, the Donation Partial Refund autoresponder is sent instead of the Personal Fundraising Partial Refund autoresponder.

40708

A Champion does not receive the Honorary Fund Creation Acknowledgment email when the first honorary fund is created.

Reports Classic

Issue Description
22340

When a custom date range is applied to an Advocacy Alert Summary Report, the column displaying the number of Tell-a-Friend messages forwarded for each alert is not limited by that date range. Instead, the column displays the total number of Tell-a-Friends sent since the creation of the alert.

Report Writer

Issue Description
37344

The standard Report Writer report model includes a "bulk offline adjustment". (The bulk offline adjustment is not included in reports run from Reports Classic.)

Surveys

Issue Description
44266

When you embed a Luminate Online survey in a Luminate CMS page, the survey may not display the same as it does in a PageBuilder page. You may need to adjust the CSS for your Luminate CMS pages in order for surveys to display the same in both PageBuilder and Luminate CMS pages.

TeamRaiser

Issue Description
LO-5893

When admins do not create stationery for participants to use in the Participant Center for their TeamRaiser event, the default Blank Stationery includes the following line of text at the top of the email:

A message from <name> <email>.

To remove this message, create at least one stationery in the TeamRaiser configuration. Even a completely blank stationery does not include that text.

 

During the card fulfillment process, pressing Enter on the keyboard triggers a click for the first button on the page, which is either Back or Cancel, instead of the Continue or Next buttons.

45739 Changing a Milestone dollar amount does not consistently reset a badge award.
50978

If you upload a CSV with undecodable control characters (such as, Greek letters or other non-English characters), and the site option ADDRBOOK_ENCODING_SENSITIVE_CSV_PARSER is set to true, you are taken to a Technical Difficulties page. The workaround is to remove the control character.

50996

Currently, the Spanish documentation for users with multi-locale set to Spanish provides incorrect headers (for importing a "Generic CSV" file in Participant Center Classic and, possibly, other areas such as Personal Fundraising). The CSV file will not be accepted with those headers. The correct headers are "Primero", "Apellido" and "Correo electr&oacute;nico" corresponding to the First Name, Last Name, and Email headers.

52534

When a Participant Center is embedded into a PageBuilder page, using the S80 tag to pull the trID value (<convio:session name="80" param="trID"></convio:session>) within the wrapper renders as null instead of rendering the TeamRaiser's ID. Contact your Account Manager for help with this problem.

68543

The primary email address will only update as a result of an explicit profile change or if the existing email address has a bad status. If neither condition is met, no change will be made to the CONSTITUENT table and the change will go to the EMAIL_HISTORY table.

WYSIWYG (Content Editor)

Issue Description
40570

The WYSIWYG text color tool does not change link colors. To set a link color not the default, create your text, apply the color to that text and then highlight the colored text and apply the link. Advanced users can create an a.style that defines the text color and apply that style to the link.

40717

Conditional comments that test for the Internet Explorer browser to determine which Cascading Style Sheet to apply are broken by the WYSIWYG in Firefox.

40718

The HTML Source Editor reformats pasted content. Some carriage returns and left brackets that precede double brackets (such as for opening a Luminate Online conditional) are removed, and some are replaced with a single space character. Leading tabs are removed from HTML elements.

40720

<code></code> tags pasted into the HTML Source Editor are transformed to <code>//]]&gt;&lt;/script&gt;</code>. This behavior can break Luminate Online conditionals.

40780

If a table is the first element on a page, you cannot navigate in front of it. If a table is the last element on a page, you cannot navigate past it. If a table is the sole element on a page, you cannot navigate around it and you cannot add content outside it.

40801

When multiple cells of a table are selected and CSS changes are made to the cells, they apply only to the left, top-most field.

40816

(Internet Explorer only) When pasting text into the WYSIWYG editor, a "Do you want to allow this webpage to access your clipboard" message pops up. To remove this, select "Internet Options" from the browser Tools menu and go to the Security tab. With the Internet zone highlighted, click the "Custom level" button and enable the "Allow Programmatic clipboard access" radio in the &ldquo;Scripting&rdquo; section.

40844

(Internet Explorer only) The TinyMCE WYSIWYG moves the selected="selected" attribute to the first option in a list.

41098

Images uploaded in the WYSIWYG do not automatically display in the Image Library. The image list must be refreshed to display uploaded images.

41045
41186

The edit CSS Style button is available even to administrators who did not have permissions to edit CSS styles. The button can be removed from the WYSIWYG editor by setting the site option SITE_WYSIWYG_RESTRICT_INLINE_FORMATTING.

41571

If you select a conditional (or the text block containing it) that contains a table or another conditional, then select "preformatted" or "heading1" from the toolbar Style dropdown menu, the Style change is not applied and the conditional breaks.

44406

When tables are inserted into an email, the WYSIWYG editor forces a tag that the spam checker marks as spam. The tag is, however, valid, and the spam point for it is only 0.1 (out of 5.0 total for spam).

44859

The WYSIWYG will insert blank lines between HTML comment tags (&lt;-- and --&gt;). The workaround is to delete the blank lines. To do so, you must work in the WYSIWYG HTML Source editor. Select and copy the comment tags and all content between them. Paste that into a different text editor (such as Notepad). Delete the blank lines and paste the comment back into your document and save.

45107

The WYSIWYG only supports a table -- not cell -- alignment field. As a result, align top is not available for table cells. Administrators who must apply top alignment to cell content will have to use the HTML source code editor to add the attribute manually.

45151

In sites where Multi-Locale is enabled, switching between the WYSIWYG editor and the HTML editor will cause your work to be lost. To avoid this, save your work before toggling between the two editors.

45165 When searching the Luminate Online Image Library, only four images show at a time.
45171 Popups must be enabled for the WYSIWYG to work.
47788 The WYSIWYG spell check does not notify you when its internal limit on misspelled words has been reached.
48671

When you open a very large document in the WYSIWYG using Microsoft Internet Explorer, you may get an alert warning you that a script on the page is causing the browser to run slowly. Subsequent changes to the document are not saved. To avoid this problem either edit with a different browser, such as FireFox, or convert the document into a multiple component page with the content divided among the components.

62601 Personalization Groups and Types are not currently translated in the WYSISWYG Editor in the Event Management Center.
62606 Conditional Groups and Types are not currently translated in the WYSISWYG Editor in the Event Management Center.
65720

On Microsoft Internet Explorer 11 and Google Chrome, after an image's placement is changed, you cannot insert a link on the image.

Use Mozilla Firefox when working with image links. Or, when using Google Chrome or Internet Explorer, insert the link on the image before moving placement of the image.