Hey Joe,

So the too many form elements issue pops up with the html content versions panel. I have a client who has over 120 previous versions on one feature instance. I think if we had a button to delete versions older than X days or if we had a config setting to auto-delete versions older than X days. The auto-delete action could fire when a new version is created.

Thanks,
Joe D.

It's set to 10 but the problem is there. We get the error below when we try to update the HTML content or click on one of the version history page links.

2012-04-16 15:36:05,399 ERROR (null) - (null) - (null) - mojoPortal.Web.mojoBasePage - 65.31.211.163-en-US - /HtmlEdit.aspx?mid=327&pageid=97
System.Web.HttpException (0x80004005): The URL-encoded form data is not valid. ---> System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at System.Web.HttpValueCollection.FillFromEncodedBytes(Byte[] bytes, Encoding encoding)
   at System.Web.HttpRequest.FillInFormCollection()
   at System.Web.HttpRequest.FillInFormCollection()
   at System.Web.HttpRequest.get_Form()
   at System.Web.HttpRequest.get_HasForm()
   at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull)
   at System.Web.UI.Page.DeterminePostBackMode()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

The only way around it at this point is to use the aspnet:MaxHttpCollectionKeys setting.

Thanks,
Joe D.

I've only got 19 viewstate items on this page when viewing it. When I edit the content with the 120+ versions, HtmlEdit.aspx has 7000+ viewstate items. There are 5 modules on the page and a search box. The 5 modules are HTML content (3), Site Statistics (1) and Google Translate (1). One of the html modules and the Google Translate are in ModuleWrappers. The module we're having the trouble with is not in a ModuleWrapper.

Removing the ModuleWrappers from the page doesn't stop the error from occuring.

Editing any of the other html content modules on the page does not produce an error.

It seems that the version paging is adding viewstate for all of the elements on all of the pages, not just the currently selected page.

Thanks,
Joe D.

Awesome! I'm glad you found that. I was starting to think I had a weird install or something.

Thanks!,
Joe D.