Forums

We expect that Publish 5.3.1 will work with DNN 5.0.1 and some of the breaking changes have been corrected in that next release of DNN5. We will test this out. If 5.3.1 still doesn't work we will be sure that Publish 5.4 is DNN5 compatible. No hard ETA on 5.4, but likely within the next month.

There was a blog post earlier today from Joe Brinkman saying the current date for 5.0.1 is Monday the 23rd of February. We will be sure to test it the working code for 5.0.1 next week, prior to the public 5.0.1 release

Good news! Our testing of Publish 5.3.1 against DNN 5.0.1 has been successful, the breaking changes that were in 5.0.0 have been corrected in the 5.0.1 release.

DNN 5.0.1 should be available later today from DotNetNuke.com

Chris

I have upgraded my portal to 5.0.1 successfully and installed Engage: Publish 5.3.1.  My portal is running under the 3.5 framework and as you had suggested before I compiled the Engage: Publish solution against the 3.5 framework and copied the EngagePublish.dll into the bin directory.  I am now receiving this error when I attempt to click on Manage Content.

A critical error has occurred.
The control with ID 'clpAdminEdit' requires a ScriptManager on the page. The ScriptManager must appear before any controls that need it.

AssemblyVersion: 5.0.1
PortalID: 0
PortalName:
UserID: 1
UserName:
ActiveTabID: 92
ActiveTabName:
RawURL: /Publications/tabid/92/ctl/AdminContainer/mid/430/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 1b60d743-5216-4358-a2a0-3c9f6e03eed2
InnerException: The control with ID 'clpAdminEdit' requires a ScriptManager on the page. The ScriptManager must appear before any controls that need it.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.ExtenderControl.get_ScriptManager
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: The control with ID 'clpAdminEdit' requires a ScriptManager on the page. The ScriptManager must appear before any controls that need it. ---> System.InvalidOperationException: The control with ID 'clpAdminEdit' requires a ScriptManager on the page. The ScriptManager must appear before any controls that need it. at System.Web.UI.ExtenderControl.get_ScriptManager() at System.Web.UI.ExtenderControl.RegisterWithScriptManager() at System.Web.UI.ExtenderControl.OnPreRender(EventArgs e) at AjaxControlToolkit.ExtenderControlBase.OnPreRender(EventArgs e) at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Any help is appreciated.

Thanks again.

Derek

Chris,

Thanks for all the help.  I had forgotten to swap the AjaxControlToolkit.dll file with the 3.5 version before I built the solution, everything appears to be working as expected so far.

Thanks again for your help.

Derek