Umbraco not correctly displaying a Macro in a Members Area
Hi,
We are using Umbraco 4.5.2 and have created a simple Macro which works fine on all the pages but the Members area pages. In the Members area, the Macro renders it's content just fine in the Rich Text Editor, however when Umbraco renders the page - instead of rendering the content for the Macro cleanly like it does in the Text Editor it does nothing. Inspecting the HTML shows that instead of rendering the content all it's done is:
<?UMBRACO_MACRO macroAlias="ThoughtOfTheDay"
settingsid="1861" />
Which looks to me as if Umbraco is ignoring the Macro for some reason. Why would this happen and is there a way around it?
Macro's are meant for content/pages only, since a Member is not content this is working as excpected, maybe you can create a custom datatype to display the data that you want?
Perhaps I was not clear - it is on the Content Pages where this is happening, not in the in the backend. The "Members Page" I am referring too is simply a content page on which we have used Role Based Protection. (i.e. we set the Public Access to a specific role on the content page via the interface).
Umbraco not correctly displaying a Macro in a Members Area
Hi,
We are using Umbraco 4.5.2 and have created a simple Macro which works fine on all the pages but the Members area pages. In the Members area, the Macro renders it's content just fine in the Rich Text Editor, however when Umbraco renders the page - instead of rendering the content for the Macro cleanly like it does in the Text Editor it does nothing. Inspecting the HTML shows that instead of rendering the content all it's done is:
Which looks to me as if Umbraco is ignoring the Macro for some reason. Why would this happen and is there a way around it?
Thanks in advance for any help people can offer.
Hi,
Macro's are meant for content/pages only, since a Member is not content this is working as excpected, maybe you can create a custom datatype to display the data that you want?
Cheers,
Richard
Hi,
Perhaps I was not clear - it is on the Content Pages where this is happening, not in the in the backend. The "Members Page" I am referring too is simply a content page on which we have used Role Based Protection. (i.e. we set the Public Access to a specific role on the content page via the interface).
is working on a reply...