This is exactly the issue that 1.6 was trying to resolve when it completely broke macro execution, instead outputting HTML code. Unfortunately it is unresolveable, and I'm quite tempted to call it a bug in the {include} macro. That macro needs to render the content of the page using a custom RenderMode instead of the one it is handed.
In any case, there is a workaround. If you have the Reporting plugin installed you can do this instead:
{report-info:content:body|render=wiki|source=Page to include}
Caveat: the current version of reporting (2.0.1) will display an error message when displaying images. This is a bug in reporting and will be resolved in Reporting 2.0.2).
David Peterson added a comment - 22/Mar/08 02:30 PM This is exactly the issue that 1.6 was trying to resolve when it completely broke macro execution, instead outputting HTML code. Unfortunately it is unresolveable, and I'm quite tempted to call it a bug in the {include} macro. That macro needs to render the content of the page using a custom RenderMode instead of the one it is handed.
In any case, there is a workaround. If you have the Reporting plugin installed you can do this instead:
{report-info:content:body|render=wiki|source=Page to include}
Caveat: the current version of reporting (2.0.1) will display an error message when displaying images. This is a bug in reporting and will be resolved in Reporting 2.0.2).
In any case, there is a workaround. If you have the Reporting plugin installed you can do this instead:
{report-info:content:body|render=wiki|source=Page to include}Caveat: the current version of reporting (2.0.1) will display an error message when displaying images. This is a bug in reporting and will be resolved in Reporting 2.0.2).