Hi Matt,

The adapter for mojoTreeView has been highly modifed to meet our needs for site navigation and styling. It is possible that those changes have broken some postback stuff but I know also that the first version of the CSSFriendly adapter also had some postback problems with treeview that were supposedly solved in a newer version.

Using postback with menu or treeview is not something I recommend in general. Postback should not be used for navigation, postback is intended for processing form submissions and the classic pattern is to redirect out of postback after processing a form submission to avoind the problem of the browser refresh button causing a duplicate or second postback. Not getting out of postback can also cause problems for other features on a cms page that have logic based on if(!IsPostBack). 

One common solution for keeping a cms feature postback from affecting other features on a page has been to wrap it in an updatepanel. Unfortunately neither treeview nor menu work inside updatepanel. 

So my advice in general is avoid using the postback features of menu and treeview and we don't use them in mojoPortal.

One option if you really need to go that direction is that as of .NET 4 the Menu control has a new RenderingModeProperty to make it render as nested ul/li elements instead of tables, so potentially you could use <asp:Menu and use postback and style it like a treeview. Unfortunately they did not give the treeview the same treatment and it does not have that new property so CSS Adapter would still be needed.

If Menu doesn't work for you let me know and perhaps I can implement another TreeView control that uses the unmodified CSS Adapter.

Best,

Joe