Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Backward Compatibility
If you were using macros prior to Nexaweb's 4.2 release and those macros contained any of the MessageFormat special characters, you may wish to disable the MessageFormat functionality to ensure that your macros continue to function as before. This can be done by changing the following value to true in your nexaweb-client.xml file:

 

Code Block
    <!-- This parameter is supplied so that the macro code can know NOT -->
	<!-- to use MessageFormat for the macro strings. in 4.2 we added parameters -->
	<!-- which use MessageFormat, thus single tick escaping is required in 4.2 -->
	<!-- plus. We want existing macros to work if the customer so desires. -->
	<ensure-pre-4-dot-2-macro-compatibility>false</ensure-pre-4-dot-2-macro-compatibility> 

 

...