In additions to the techniques suggested for Action code debugging, consider:
- Using ^action^ to record template-only calculations back into user attributes for later inspection - useful with complex exports.
- Using HTML view's export button to export a note/file. The latter button will always overwrite existing exported files whereas full export may not. This is because the full export looks at whether source attributes have changed. Thus changes in templates code aren't 'seen' and the process can become obfuscated in complex include exports.
- The effects of $HTMLDontExport and $HTMLExportChildren on the use of ^include^. The later can't return data from a note set to not export.
- For $Text export using ^text^ remember the effects of $HTMLMarkupText and $HTMLQuoteHTML.
- The slightly different effects of ^title^ vs. ^value($Name)^ and ^text^ vs. ^value($Text)^.
- ^text(plain)^ exports ASCII and ^value($Text)^ exports UTF-8. Non low-ASCII characters in ^text(plain)^ will export as UTF-8 codes rather than the intended character. This is not normally the intention in a plain text context.
