Incorrect behavior after authentication

[davegardner]

The background is that I have a site with several very slow queries and I am using aggressive caching to improve perceived performance. This is fine for unauthenticated users, but unfortunately many of the users hitting the site will want to authenticate. I was hoping that donut caching of the Main Menu Widget would alleviate the problem, but it seems not quite yet.

After following the instructions in the wiki to add the Output Cache Part to the Menu Widget, enabling Ajax on the Menu Widget and setting the Output cache for the Menu Widget to 0 I can see that it's definitely ajaxified (Loading.. flashes). However, as soon as I authenticate it seems to return to the incorrect URL, http://dev.cbca.org.au/AjaxifyContent/11?__r=8d362ba1ed76c19.

Where did that 'AjaxifyContent' come from?

[DaRosenberg]

Hi @davegardner ,

Sorry that nobody replied to this until now. Are you still having issues?

I'm not sure what you mean by "return the incorrect URL", can you elaborate a bit? The AjaxifyContent controller is the one used by the Ajaxify client script to download the content of the widget asynchronously, so you should expect that to be the URL of the request used to load the widget.

I should also clarify that it's probably overkill to use both OutputCachePart and AjaxifyPart on the same menu widget, since all requests made to AjaxifyContent will be output cached separately by the built in output caching of Orchard. And since that happens on a different route, you can control the cache duration for this one separately in the output cache settings.

Finally, based on what you are saying, you may want to look at IDeliverable.Donuts which is a newer module that is a lot more robust for these kinds of scenarios.