Which is supposed to be the the 2.2 install however when the package installs I get this message:
Which suggests this is the 2.1 version of the package and isn't compatible. When I check the dll versions then are stamped as 6.1.1.0 and they contain another dll called FergusonMoriyama.Umbraco4.Workflow.dll.
So my first question is, is this expected? Is this just a versioning issue on the dll but actually the code is right?
If the answer to that is yes the code is correct then my second question is - should this version actually be compatible with 6.2.X, is anyone using it? On a vanilla install of 6.2.4 of Umbraco the workflows tab on the content is blank and the "My Recent Content" throws this error:
Could not load control: '/usercontrols/fmworkflow/RecentContent.ascx'.
Error message: System.NullReferenceException: Object reference not set to an instance of an object. at umbraco.cms.businesslogic.web.Document.get_Text() at ASP.usercontrols_fmworkflow_recentcontent_ascx.__DataBind__control8(Object sender, EventArgs e) at System.Web.UI.Control.OnDataBinding(EventArgs e) at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBind() at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBind() at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBind() at System.Web.UI.WebControls.GridView.CreateRow(Int32 rowIndex, Int32 dataSourceIndex, DataControlRowType rowType, DataControlRowState rowState, Boolean dataBind, Object dataItem, DataControlField[] fields, TableRowCollection rows, PagedDataSource pagedDataSource) at System.Web.UI.WebControls.GridView.CreateChildControls(IEnumerable dataSource, Boolean dataBinding) at System.Web.UI.WebControls.CompositeDataBoundControl.PerformDataBinding(IEnumerable data) at System.Web.UI.WebControls.GridView.PerformDataBinding(IEnumerable data) at System.Web.UI.WebControls.DataBoundControl.OnDataSourceViewSelectCallback(IEnumerable data) at System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) at System.Web.UI.WebControls.DataBoundControl.PerformSelect() at System.Web.UI.WebControls.BaseDataBoundControl.DataBind() at System.Web.UI.WebControls.GridView.DataBind() at FergusonMoriyam.Workflow.Umbraco.Web.Ui.RecentContent.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at Spring.Web.Support.ControlAccessor.AddedControl(Control control, Int32 index) at Spring.Web.Support.SupportsWebDependencyInjectionOwnerProxy.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at umbraco.cms.presentation.dashboard.OnInit(EventArgs e)
On our clients site it just throws a Spring.NET error saying it can't find a certain contrete type (I can provide a stack trace if needed)
Finally does this work on Umbraco 7.X? I don't want to suddenlt be stung on an upgrade to 7 and any workflow they've set up suddenly stops working.
Phew okay, a lot of questions, I hope someone can help!
First the easy answers. There isn't a workflow for Umbraco 7 and as much as we'd love to do it and it isn't too much work, we'd need a commercial sponsor. The other route would be to do it for yourself.
Secondly: I wouldn't worry about the installer message - it displays the last tested version and we know it will work with 6.2.4.
The execption on the dashboard is a little more complex. That should just read the Umbraco audit trail from the database and I can't decipher the stack trace.
That's lovely, thanks for the quick response. I'll dig into this a bit more, the bigger issue was a spring.net error finding a concrete type but I've got to free up a bit of time to figure that out, I suspect it's something to do with our application.
If we do end up using it we'll contribute anything back to the project for sure, including if we upgrade to 7!
Wrong 2.2 package for Umbraco 6.2.X?
I've grabbed the 2.2 installer from here:
http://our.umbraco.org/FileDownload?id=9522
Which is supposed to be the the 2.2 install however when the package installs I get this message:
Which suggests this is the 2.1 version of the package and isn't compatible. When I check the dll versions then are stamped as 6.1.1.0 and they contain another dll called FergusonMoriyama.Umbraco4.Workflow.dll.
So my first question is, is this expected? Is this just a versioning issue on the dll but actually the code is right?
If the answer to that is yes the code is correct then my second question is - should this version actually be compatible with 6.2.X, is anyone using it? On a vanilla install of 6.2.4 of Umbraco the workflows tab on the content is blank and the "My Recent Content" throws this error:
Could not load control: '/usercontrols/fmworkflow/RecentContent.ascx'.
On our clients site it just throws a Spring.NET error saying it can't find a certain contrete type (I can provide a stack trace if needed)
Finally does this work on Umbraco 7.X? I don't want to suddenlt be stung on an upgrade to 7 and any workflow they've set up suddenly stops working.
Phew okay, a lot of questions, I hope someone can help!
Hi Steven,
First the easy answers. There isn't a workflow for Umbraco 7 and as much as we'd love to do it and it isn't too much work, we'd need a commercial sponsor. The other route would be to do it for yourself.
Secondly: I wouldn't worry about the installer message - it displays the last tested version and we know it will work with 6.2.4.
The execption on the dashboard is a little more complex. That should just read the Umbraco audit trail from the database and I can't decipher the stack trace.
Do the other workflow dashboards give you issues?
Happy to try and work through this with you.
Best,
Hi Darren,
That's lovely, thanks for the quick response. I'll dig into this a bit more, the bigger issue was a spring.net error finding a concrete type but I've got to free up a bit of time to figure that out, I suspect it's something to do with our application.
If we do end up using it we'll contribute anything back to the project for sure, including if we upgrade to 7!
Thanks a lot,
Steve
is working on a reply...