Skip to main content

I need to prepare the org before Spring release. The step I need to do is;

 

1. After you enable this update for testing, verify that the custom text from your label attributes renders correctly on your Visualforce pages.

 

2.Locate and make a list of double-escaped labels.

If label attribute text doesn’t render as expected on a Visualforce page, the attribute may be double-escaped.

Review your code to see if you escaped the label attribute before enabling this release update. If needed, see Visualforce Developer Guide: Unescaped Output and Formulas in Visualforce Pages for a list of functions that are commonly used for escaping strings.

Do not remove any manual escaping yet. For now, only create a list of all the Visualforce pages that incorrectly render text from double-escaped label attributes.

 

I am stuck at step#2. Has anyone worked this update recently? #Salesforce Developer  I'd like to ask how I can locate the  double-escaped label attributes.

1 answer
0/9000