Contour form added to richtext snippet in media gallery not publishing
Ok, hopefully I can explain what I'm doing to see if there is a solution to what I'm encountering [or lack thereof]. I have a media type, named "Snippet", that contains only a richtext box, alias "snippetText", allowing users to create snippets of reusable content (think a newsletter signup column tout). Now, I have a media picker in my doc type to select one of these snippets that will be shared in the current page and potentially any children. Here's the magic portion of XSLT in my RightShared macro:
All works beautifully except the Contour form doesn't render. I verified the form is valid by adding it as regular content to test it. Is this even possible to achieve using Contour 1.0.7 on Umbraco 4.0.3?
I tried a different approach and received some different results - unusual results might I add. Instead of selecting and rendering a snippet, I opted for a Form picker on the homepage and the macro is called on all pages. Here's the macro magic: (it's not limited to just this portion of xslt, the rest is irrelevant)
$rightContactForm is the correct guid for the Contour form I'm attempting to render; however, when I execute the macro I do not receive the correct rendering of the form; rather a next and previous button are present. Here's the source of the rendering:
Since this contact form resides on many pages (right column), I want to select the form or snippet containing the form on the home page and every child that wants to display the form can do so with a flag. I'm afraid I may have to resort to hard coding the form as a separate template for pages that want to use the contact form just to satisfy the requirement.
I showed the output to another developer and he immediately stated that's the default output of a dotnet wizard control. Odd. Anyway, I believe you are correct and I've decided on a different strategy to achieve similar goal.
Contour form added to richtext snippet in media gallery not publishing
Ok, hopefully I can explain what I'm doing to see if there is a solution to what I'm encountering [or lack thereof]. I have a media type, named "Snippet", that contains only a richtext box, alias "snippetText", allowing users to create snippets of reusable content (think a newsletter signup column tout). Now, I have a media picker in my doc type to select one of these snippets that will be shared in the current page and potentially any children. Here's the magic portion of XSLT in my RightShared macro:
Here's an example of a node grabbed from the macro:
All works beautifully except the Contour form doesn't render. I verified the form is valid by adding it as regular content to test it. Is this even possible to achieve using Contour 1.0.7 on Umbraco 4.0.3?
I tried a different approach and received some different results - unusual results might I add. Instead of selecting and rendering a snippet, I opted for a Form picker on the homepage and the macro is called on all pages. Here's the macro magic: (it's not limited to just this portion of xslt, the rest is irrelevant)
$rightContactForm is the correct guid for the Contour form I'm attempting to render; however, when I execute the macro I do not receive the correct rendering of the form; rather a next and previous button are present. Here's the source of the rendering:
Since this contact form resides on many pages (right column), I want to select the form or snippet containing the form on the home page and every child that wants to display the form can do so with a flag. I'm afraid I may have to resort to hard coding the form as a separate template for pages that want to use the contact form just to satisfy the requirement.
Comment author was deleted
Hi Jon,
A Contour form requires to be inside a form with runat="server" attribute.
Got it, day 1, I double checked just to make sure tho.
Comment author was deleted
Hey Jon, I think the main problem is is that you are trying to output the Contour form (a .net usercontrol) from an xslt macro. This will not work.
I showed the output to another developer and he immediately stated that's the default output of a dotnet wizard control. Odd. Anyway, I believe you are correct and I've decided on a different strategy to achieve similar goal.
is working on a reply...