The debug mode has been completely redesigned to enable input error context information as well as extended context information for Java Script errors. See Setting the engine preferences for information on how to enable debug mode.
Critical errors caused by exceptions in the output library now display the template element that caused the error in addition to the error message.
This preference setting warns the template designer of potential issues. The feature shows a warning if any query or iteration is processed consecutively for more than N repetitions, where the N threshold is defined in the preferences. You can set the loop threshold in the engine preferences:
CRRPE1064I Processing document template 1 of 1.
CRRPE3604W The template element 4 (iteration) has been processed for 150 times which exceeds the defined threshold. This is normal for templates processing large data sets but can indicate a problem with the execution of the template otherwise.
CRRPE3604W The template element 4 (iteration) has been processed for 300 times which exceeds the defined threshold. This is normal for templates processing large data sets but can indicate a problem with the execution of the template otherwise.
CRRPE1064I 1500 publishing commands are processed. 1208 publishing commands remain to be processed.
CRRPE1064I 2709 publishing commands are processed. 0 publishing commands remain to be processed.
As many of the error reports now include the ID of the element causing the error, the element ID is now a visible property and is shown in the properties page as well as in the tooltip. You can also search for a particular element ID via the Search menu.