Not quite sure about the error message. But I'm wondering what your goal is? what do you want to achieve and won't you be able to do this using the altTemplate option?
Murray's answer worked for me. It might be possible to use one of the other Server methods (see http://forums.iis.net/p/1146511/1857360.aspx#1857360 for example) instead of Response.Redirect() to transfer control, but for now I'm using his since it does what I want, even if it does feel like a bit of a hack:
Usercontrol & Server.transfer
In my usercontrol I got a Server.transfer.
I get an error thrown by
Am I missing a setting to disable this check from happening, or does umbraco and transfer just don't love eachother?
Would RenderTemplate be an option?
I believe that Server.Transfer is looking for a "real/physical" page. You could try
That will work indeed, but I need values from the refering page, so I need a transfer to be able to access the context items
The transfer is probably done after rewriting. Try using default.aspx?id=1234 or something like that.
Sorry, the id is not nessesary ofcource.
Not quite sure about the error message. But I'm wondering what your goal is? what do you want to achieve and won't you be able to do this using the altTemplate option?
Removed all context items and set them to Session variables.
Redirecting now, no longer transfering.
To do a "Server.Transfer" equivalent in code behind, you can do something like this:
I had an issue transfering to default.aspx?id=1234 because it caused an infinite loop
Murray's answer worked for me. It might be possible to use one of the other Server methods (see http://forums.iis.net/p/1146511/1857360.aspx#1857360 for example) instead of Response.Redirect() to transfer control, but for now I'm using his since it does what I want, even if it does feel like a bit of a hack:
Thanks!
is working on a reply...