A blank page with the error 'The entity name must immediately follow the '&' in the entity reference' is displayed when selecting "Proceed to Checkout" for a two-step shopping cart when:
a) a catalog item has a name that has an ampersand.
b) a catalog item has a variable question that has an ampersand.

Steps to Reproduce

1.Ensure that the following system properties (sys_properties) are set to true:
2. Create a catalog item that has a name with an ampersand (for example, Test M & M).
3. Create a question of Single Line Text type with an ampersand in the name (for example, Do you like M & Ms).
4. Click Try It and Add item to the shopping cart.
5. Click Proceed to Checkout.

Instead of the two-step summary page of the shopping cart item, a blank page loads with the error: The entity name must immediately follow the '&' in the entity reference.


The following field in the respective UI Macro needs to be changed: 

1. In the UI Macro, sc_cart_view_column_expandable_desc, change: 




Line 23 should then look like this:

<g:inline template="help_text.xml" question_show_help="true" question_help_tag="${HTML:jvar_questionHelpTag}" question_name="${jvar_cart_item.getID()}" help_class="${jvar_line_color}">

Note: This is the fix for catalog item with a name and short description that contains ampersand.

2. In the UI Macro cart_variable_summary_v2,

a) change:

Line 15 should look like this:
<td style="color:grey;">${HTML:questionLabel}$[SP]</td>

Note: This is the fix for variable with question that contains an ampersand.

b) change:

Line 19 should look like this:

Note: This is the fix for variable with question display that contains an ampersand.



Three alternate workarounds include:

1. Change system property glide.ui.escape_text to true
Note: Some customers are reluctant to change this where they had previous issues with setting this property to true.

2. Change system property glide.sc.use_cart_layouts to false (not ideal).

3. Change the individual UI Macros sc_cart_view_column_expandable_desc and cart_variable_summary_v2 to escape the particular field.
(like the previously suggested solution.)


Please refer to KB0562895 for recent update regarding this

Related Problem: PRB636980

Seen In

Eureka Patch 4 Hot Fix 1
Fuji Patch 2 Hot Fix 1
Fuji Patch 3
Fuji Patch 5
Fuji Patch 6
Fuji Patch 7 Hot Fix 5
Fuji Patch 8
Geneva Patch 3 Hot Fix 2
Geneva Patch 4
Geneva Patch 6 Hot Fix 2
Geneva Patch 7
Helsinki Patch 4

Fixed In

Fuji Patch 7

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-10-15 08:07:33