I get the message "Filtering is not allowed." in both the preview of the form and on my site. The site is running Umbraco 6.0.4 Can you specify why this error might occour?
I've located the problem. It's caused by an ActionFilter that we use for all our sites to modify the page output. I'm not sure why this is causing problems with Contour. We never had issues before.
I've seen that post but it's not helping. I think I know why this happens. It seems that you override the HttpContext.
When checking for filterContext.IsChildAction in my attribute it returns False when it should return True. Could that have something to do with you overiding some things?
Filtering is not allowed.
I get the message "Filtering is not allowed." in both the preview of the form and on my site.
The site is running Umbraco 6.0.4
Can you specify why this error might occour?
Thanks an advance!
Comment author was deleted
Hey Ron,
That's strange, did you make any changes to the form views so far?
Comment author was deleted
Will try a test install with that some version to see if I can reproduce
Hey Tim,
I've located the problem. It's caused by an ActionFilter that we use for all our sites to modify the page output. I'm not sure why this is causing problems with Contour. We never had issues before.
Any idea?
Comment author was deleted
Just tried with a fresh 6.0.4 installing latest Contour 3.0.13 and that works fine...
@Ron are you also running latest Contour or an older version?
Comment author was deleted
Ah ok glad you found it, possible solution here: http://forums.asp.net/t/1634304.aspx/1
I've seen that post but it's not helping. I think I know why this happens. It seems that you override the HttpContext.
When checking for filterContext.IsChildAction in my attribute it returns False when it should return True. Could that have something to do with you overiding some things?
Comment author was deleted
Well it is using mvc bridge http://our.umbraco.org/projects/developer-tools/mvcbridge (to support older Umbraco versions) so I suppose that in that code it might be overriding the HttpContext
is working on a reply...