Hi! I have a problem with previewing macros in RTE. If I create a new page and add a macro in the RTE the preview works fine. But as soon as I save the page (i.e. not publishing) the preview disappears and it will look like in the image below.
The markup for the macro will then look like this:
I would also like to know the specific conditions in which the partial view macro's cshtml files are displayed correctly in all circumstances (edit screen, in rte, in front-end..)
I've seen this too. There is a hacky fix. In that XSLT macros are unaffected. Therefore, depending on the complexity of your code it may be easier to use XSLT (If RTE preview support is vital).
You can always offload the heavy lifting to C# and use an XSLT extension if it's complex. Thereby just using XSLT as a view (You end up with a nice MVC pattern doing this!). This also means that if they ever fix this issue it's easier to migrate it back to a partial.
Issue when previewing macro in RTE
Hi! I have a problem with previewing macros in RTE. If I create a new page and add a macro in the RTE the preview works fine. But as soon as I save the page (i.e. not publishing) the preview disappears and it will look like in the image below.
The markup for the macro will then look like this:
When I finally publish the page the problem disappears and the macro is previewing as expected again. After that, saving works fine again.
Does anyone have any idea why the previewing disappears when I only save the page?
Thanks in advance!
Anyone? :)
I would also like to know the specific conditions in which the partial view macro's cshtml files are displayed correctly in all circumstances (edit screen, in rte, in front-end..)
I'm still having issues with this, does anyone have any idea what might be wrong?
Thanks in advance!
Hi,
This appears to be a reported issue: http://issues.umbraco.org/issue/U4-9075
I've seen this too. There is a hacky fix. In that XSLT macros are unaffected. Therefore, depending on the complexity of your code it may be easier to use XSLT (If RTE preview support is vital).
You can always offload the heavy lifting to C# and use an XSLT extension if it's complex. Thereby just using XSLT as a view (You end up with a nice MVC pattern doing this!). This also means that if they ever fix this issue it's easier to migrate it back to a partial.
is working on a reply...