Bug Found. Doesn't work with GaiaWare.net controls.

[John Welborn]

I found out yesterday after way too much trial and error that if you
have a gaia control on the webform it won't render anything. I don't
get any errors, but absolutely nothing is rendered. Not even a blank
html document. There is literally _nothing_ in the view source. But
if you remove the gaia control everything works.

I don't really know how to do any further testing as there are no
errors. Running in debug mode doesn't catch anything. You can step
through the .aspx page and see where it executes the bundle commands
but after you go though the page it's just blank.

I'll post over at the gaiaware site as well. FYI, Gaia is an AJAX
framework for webforms. We're now moving to MVC and jquery, but many
of our older pages are still using the Gaia controls.

Let me know if you have any suggestions.
John

[John Welborn]

Maybe another way to look at it, or another question to ask, is there
a way to disable Cassette on our webforms pages? It's lovely for MVC,
but it's just causing problems on the webforms pages. I'd prefer to
just leave those alone.

[John Welborn]

Sweet. I just found that if I turn set rewriteHtml="false" everything
goes back to working. Yay!!

[Andrew Davey]

Nice work tracking down a work-around. I'm not sure why the output rewriting is breaking the page. Perhaps the Gaia control is also installing a response filter that conflicts with Cassette's. Let me know if you see it happening with other controls as well.

Another useful trick to know is that the following will disable rewriting just for the current request:

HttpContext.Current.Items.Add("Cassette.IsHtmlRewritingEnabled", false);

Make sure it's added before the PostRequestHandlerExecute asp.net pipeline step is executed e.g. on page load.

Of course if you don't need rewriting at all, then leave it completely switched off in web.config.

[John Welborn]

Ah that's a nice tip. I might be able to add that to the master pages
for my old .aspx files and then I could leave it enabled for the MVC
pages.

I'm guessing that's exactly what is happening conflict wise. Gaia is
an asp.net ajax library and I'm guessing they grab the response so
they can add in all of their client side Javascript.

On Jan 3, 8:13 am, Andrew Davey <and...@equin.co.uk> wrote:
> Nice work tracking down a work-around. I'm not sure why the output
> rewriting is breaking the page. Perhaps the Gaia control is also installing
> a response filter that conflicts with Cassette's. Let me know if you see it
> happening with other controls as well.
>
> Another useful trick to know is that the following will disable rewriting
> just for the current request:
> HttpContext.Current.Items.Add("Cassette.IsHtmlRewritingEnabled", false);
> Make sure it's added before the PostRequestHandlerExecute asp.net pipeline
> step is executed e.g. on page load.
>
> Of course if you don't need rewriting at all, then leave it completely
> switched off in web.config.
>

[John Welborn]

FYI, this worked perfectly. I was able to turn it back on in the
web.config and then in the Page_Load of all of my Master Pages I
added
HttpContext.Current.Items.Add("Cassette.IsHtmlRewritingEnabled",
false);

So I was able to disable Cassette in .aspx pages (which is fine) and
it works like a champ with the MVC pages.