the problem appears when the function is called in the AfterPublish event (even if the page ID is for a different page than the one being published).

It works fine otherwise.

Hi Paul,

I am having the same problem, after reading this post, and its causing a lot of problems as this functionality is crucial to a project I'm working on right now. Have you found anything to help sort this? I have tried putting <pages validateRequest="false"> in the web.config but that doesn't help.

I have found a plugin from Darren Ferguson which performs the html rendering correctly but it operates on the whole site. I need it to be limited to certain doctypes.

Does anyone on the Umbraco forum know of a work around for the RenderTemplate issue me and Paul have found? If not is there another means of outputting a node (of a certain doctype) to html on the server?

Thanks, Nick

Hi Nick,

No, I never found a solution. I changed the funcitonality of my site slightly so I could avoid the AfterPublish event - not ideal but fortunate it didn't bother my client too much.

Cheers

Paul

You can get around that error by adding this in the template:

<umbraco:DisableRequestValidation runat="server"/>

Or you could use this code in your user control:

        protected void Page_Init(object sender, EventArgs e)
        {
            ((umbraco.UmbracoDefault)Page).ValidateRequest = false;

        }

Actually, I'm trying to use this now and running into another problem. I need to render the page being published, but the first time it is published I still get the dangerous request error. After it is published once, it works fine. Any ideas why disabling request validation only works after the page has been published once? Any workarounds?

Thanks, Jeff

I think rendertemplate works with the nodefactory, and hence only with published content.

Maybe this helps http://www.asp.net/learn/whitepapers/request-validation

Mikael is right, it works with nodefactory, so can only run after umbraco.config has been written out. This hasn't happened yet when the after publish event is running. I wound up moving the code (back) to a usercontrol datatype where I can check that the document has been published once before allowing a button click to do the rendering I needed.

is working on a reply...