We have moved to GitHub Issues
You are viewing the read-only archive of Umbraco's issue tracker. To create new issues, please head over to GitHub Issues.
Make sure to read the blog posts announcing the move for more information.
Created by Andrew Rees 09 Mar 2017, 10:44:25 Updated by Warren Buckley 03 May 2017, 07:25:06
Duplicates: CON-1339
Using Umbraco 7.5.2 and Umbraco Forms 4.4.2 we've noticed an issue where exceptions are being raised when an Umbraco Form posts back to server with Javascript disabled.
The site is based on an Azure App Service using flexibile load balancing, and Redis as the session state provider. It looks like Forms is trying to push objects into session that are not marked as Serializable.
Type 'Umbraco.Forms.Core.Providers.FieldTypes.Textfield' in Assembly 'Umbraco.Forms.Core.Providers, Version=4.4.2.0, Culture=neutral, PublicKeyToken=null' is not marked as serializable.
This happens with SQLServer session mode as well, even on non-Azure sites. The core issue is this:
Unable to serialize the session state. In 'StateServer' and 'SQLServer' mode, ASP.NET will serialize the session state objects, and as a result non-serializable objects or MarshalByRef objects are not permitted. The same restriction applies if similar serialization is done by the custom session state store in 'Custom' mode.
It looks like all the FieldTypes classes need the [Serializable] attribute.
@andrewrees there is an official bug for this here: http://issues.umbraco.org/issue/CON-1339 Please vote that up.
Priority: Major
Type: Bug
State: Duplicate
Assignee:
Difficulty:
Category:
Backwards Compatible: True
Fix Submitted:
Affected versions: 4.4.2
Due in version:
Sprint:
Story Points:
Cycle: