I receive the following error when trying to save the datatype in 6.1.5:
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during
the execution of the current web request. Please review the stack trace
for more information about the error and where it originated in the
code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Spreadsheet_Uploader.SpreadsheetPrevalueEditor.Save() +317
umbraco.cms.presentation.developer.editDatatype.save_click(Object sender, ImageClickEventArgs e) +38
System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e) +186
System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument) +164
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3706
hmmm... looks like I get the same error if I create a new datatype and do not fill in the CSS style textbox. Oops! I'll have to modify my code to check to see if that box is empty. To fix, you must put at least one css class in the CSS Style List for Dropdown textbox.
FYI: When you install Spreadsheet Uploader, it comes with an example datatype. This datatype has these two classes (comma separated) in the CSS style textbox: 'order-information,specs-information' They will then show up as a drop down on the datatype in the content section. Stylesheets with these classes are in the umbraco/plugins/Spreadsheet Uploader/css/ folder. I built Spreadsheet Uploader with the idea that you may want to specify your own classes for tables that would mirror your frontend. Obviously, the advantage would be that your end user will see their tables styled the same way on the backend as the frontend site. On the other hand, you can just create a style that you want to use for all tables in the backend. 'order-information' is the closest thing to a normal generic table style if you want to just use that.
Let me know if that answers your question and I'll try and get to that bug fixed soon...
Error when saving datatype in Umbraco 6.1.5
I receive the following error when trying to save the datatype in 6.1.5:
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Stack Trace:
Any help to fix the error is greatly appreciated.
hmmm... looks like I get the same error if I create a new datatype and do not fill in the CSS style textbox. Oops! I'll have to modify my code to check to see if that box is empty. To fix, you must put at least one css class in the CSS Style List for Dropdown textbox.
FYI: When you install Spreadsheet Uploader, it comes with an example datatype. This datatype has these two classes (comma separated) in the CSS style textbox: 'order-information,specs-information' They will then show up as a drop down on the datatype in the content section. Stylesheets with these classes are in the umbraco/plugins/Spreadsheet Uploader/css/ folder. I built Spreadsheet Uploader with the idea that you may want to specify your own classes for tables that would mirror your frontend. Obviously, the advantage would be that your end user will see their tables styled the same way on the backend as the frontend site. On the other hand, you can just create a style that you want to use for all tables in the backend. 'order-information' is the closest thing to a normal generic table style if you want to just use that.
Let me know if that answers your question and I'll try and get to that bug fixed soon...
Tyler
is working on a reply...