DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Upgrading Blog Module

 6 Replies
 3 Subscribed to this topic
 30 Subscribed to this forum
Sort:
Author
Messages
Veteran Member
Posts: 1246
Veteran Member
MVP
MVP
You're an MVP!

I have an site that is using Blog 3.5.1 on DNN 8.0.4 (upgraded from an equally old DNN version)

So ... how to I upgrade

  1. to a modern version of the Blog Module
  2. and to a version that runs on DNN 9.3.2

Somewhere in there, I think, the blog module changed considerably ...

Any suggestions, tips, etc. would be appreciated greatly.

Veteran Member
Posts: 1246
Veteran Member
MVP
MVP
You're an MVP!
I upgraded 3.5.1 to 4.0.0

When I try to upgrade to 4.0.1 I get this error:

Start Sql execution: 04.01.00.SqlDataProvider file
Warning SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException (0x80131904): The object 'DF_Blog_Blogs_EnableTwitterIntegration' is dependent on column 'EnableTwitterIntegration'. ALTER TABLE DROP COLUMN EnableTwitterIntegration failed because one or more objects access this column. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteScriptInternal(String connectionString, String script) ClientConnectionId:116ca303-237a-491d-bba1-717c663609e0 Error Number:5074,State:1,Class:16 ALTER TABLE dbo.Blog_Blogs DROP COLUMN [EnableTwitterIntegration]
Info End Sql execution: 04.01.00.SqlDataProvider file

Any suggestions?
Veteran Member
Posts: 1246
Veteran Member
MVP
MVP
You're an MVP!
Hmmm...

I was able to execute that sql file using SSMS and the Blog seems to be working.
Veteran Member
Posts: 1246
Veteran Member
MVP
MVP
You're an MVP!
So, after getting to 4.1.1 and the Blog Module seemingly working ... I tried a quick jump to 6.4.1. This resulted in another error:


Error: NPI Web Library is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Unknown server tag 'dnnweb:DnnCodeBlock'. ---> System.Web.HttpParseException: Unknown server tag 'dnnweb:DnnCodeBlock'. ---> System.Web.HttpParseException: Unknown server tag 'dnnweb:DnnCodeBlock'. ---> System.Web.HttpException: Unknown server tag 'dnnweb:DnnCodeBlock'. at System.Web.UI.TagPrefixTagNameToTypeMapper.System.Web.UI.ITagNameToTypeMapper.GetControlType(String tagName, IDictionary attribs) at System.Web.UI.MainTagNameToTypeMapper.GetControlType2(String tagName, IDictionary attribs, Boolean fAllowHtmlTags) at System.Web.UI.MainTagNameToTypeMapper.GetControlType(String tagName, IDictionary attribs, Boolean fAllowHtmlTags) at System.Web.UI.RootBuilder.GetChildControlType(String tagName, IDictionary attribs) at System.Web.UI.ControlBuilder.CreateChildBuilder(String filter, String tagName, IDictionary attribs, TemplateParser parser, ControlBuilder parentBuilder, String id, Int32 line, VirtualPath virtualPath, Type& childType, Boolean defaultProperty) at System.Web.UI.TemplateParser.ProcessBeginTag(Match match, String inputText) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.WebFormsModuleControlFactory.CreateModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleControlFactory.LoadModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

-------------
Now, some google reveals that this is related to Telerik.

Suggestions about this one are welcome.

It's DNN 8.0.4 ...
Veteran Member
Posts: 1246
Veteran Member
MVP
MVP
You're an MVP!

The Telerik dlls in /bin are

Telerik.Web.Ui.dll no version in properties, but it is 18.5 mb in size
Telerik.Web.UI.Skins.dll Product version: 2013.2.717.40

DotNetNuke.Html.Editor.TelerikEditorProvider.dll    Product version:5.6.3.

----------------

I poked around a bit more and this starts happening after going from Blog 4.1.1 to Blog 5.0.0

Veteran Member
Posts: 349
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
As far as I can remember the blog module latest release 6.4.1 is compatible from Dnn 8.0 up to the latest Dnn version. Have you tried upgrading the blog module directly to 6.4.1 while staying in Dnn 8 ? Also is the server using SQL Server 2008 at least ?
Senior Member
Posts: 1607
Senior Member
MVP
MVP
You're an MVP!
New Poster
New Poster
Congrats on posting!

FYI - I just ran the blog module through EVS and came up with the following compatibility table.  :) 

(By the way, this is the route I'd suggest trying to upgrade as well... but it's sometimes different from site to site)

Blog Module Version Minimum Compatible DNN Version Installs w/ Out Errors Azure Compatible
04.00.00 04.06.02 No No
04.01.01 04.06.02 No No
05.00.00 06.02.00 Yes Yes
06.00.00 07.00.04 Yes Yes
06.00.11 07.00.04 Yes Yes
06.01.00 07.00.04 Yes Yes
06.02.00 07.02.00 No Yes
06.03.00 08.00.00 Yes Yes
06.04.01 08.00.00 Yes Yes

This, of course, doesn't take into account custom configurations and conflicts with other extensions.  I hope this helps (everyone).  :)

These Forums are for the discussion of the open source CMS DNN platform and ecosystem.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
  2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
  3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  5. No Flaming or Trolling.
  6. No Profanity, Racism, or Prejudice.
  7. Site Moderators have the final word on approving / removing a thread or post or comment.
  8. English language posting only, please.

Would you like to help us?

Awesome! Simply post in the forums using the link below and we'll get you started.

Get Involved