Recently we would like to make some big things based on #DNN8 - a better platform for DNN. Still our website only hosted by DNN7.1 upgraded in the last year. Now we chosen more security upgrade dnn7.1 -> dnn7.4 -> dnn8+. Now we firstly upgrade our official website sunblognuke.com with #DNN7.4.

Some new areas introduced in 7.4.0.

• Workflow & Versioning API
• Multi-language settings
• Improved HTML5 support

Issues & Workaround

Fighting DNN Bugs Ⅱ: Why Can't Remove Google Analytics

Some resources related with DNN7.4:

Introducing DNN Platform 7.4

DNN-7-4-DEVELOPER-QUICK-START

What is Highlight.js?

Highlight.js is a syntax highlighter written in JavaScript. It works in the browser as well as on the server. It works with pretty much any markup, doesn’t depend on any framework and has automatic language detection.

Project on Github

Next we would like to show you how to integrate DNN Blog with Javascript syntax highlighter - Highlight.js with some simple steps. Enjoying it soon :)

If you are developing a slightly complex DNN module, how to pack it in the installation package with DNN module manifest should be one important task. It will make your module looks elegant and better flexibility - reasonable folder structure, clean installation points, easy maintenance. We recommend that you should follow up the top 5 tips Bruce Chapman mentioned in this article below:

Top 5 DotNetNuke Manifest file Module Packaging Tips

1. Use Html in the File for better layout in the install pages
2. Use a resources.zip file for all your files
3. Use a html file for your Licence Agreement
4. Make your module DNN 4.x and DNN5.x compatible by using two separate manifest files.
5. Use the ‘sourceFileName’ attribute for your assembly files.

And refer to official wiki and guideline of DNN manifest schema:

Types of Manifests

The DNN Manifest Schema

Right now we found out that the node of releasenotes only can be used like that：

<releaseNotes src="Installation\ReleaseNotes\Release.07.03.00.txt"></releaseNotes>

Wrong usage： (Who know why?)

<releaseNotes> 
   <releaseNote src="Installation\ReleaseNotes\Release.07.03.00.txt"/> 
</releaseNotes>

Just update GalleryPlus module with #DNN built-in search, which was introduced from DNN7.1+. The latest package of GalleryPlus is v3.1 version.

And some useful links with DNN core search architectures and capability:

Search Done Right in DNN

Integrating with Search – Introducing ModuleSearchBase

Today I just got a very annoying error with one DNN7 fresh installation in Windows 7 x64 machine. Which is;

Compiler Error Message: CS0016: Could not write to output file 'c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\DNN7\62d43c41\27d749ca\xx_xxx.dll' – 'Access denied.'

Here is solution which I have found. What you have to do is just assign the following folders with IIS_IUSRS and NETWORK SERVICE users with the full control permission:

1) C:\Windows\temp

2) c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files

Once you applied those setting, restart your IIS and try to run your application again. The error should be gone by now.

Hope that this post will help you to fix the problem as I did and if you have found any other fix's please leave feedback and I will post them up.

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

Resources links:

Local IIS 7.0 - CS0016: Could not write to output file / Microsoft.Net > Framework > v4.0.30319 > Temporary ASP.NET Files

“CS0016: Could not write to output file” error when starting an app in IIS 7

Today we are glad to announce that SunBlogNuke v7.0.5 is available to free upgrade. It looks a long time without any updates from our team, however, don’t worry about this project and we are still paying lots of attentions on developing better software/products for you and it will be never dead :)

As for any new website based DNN framework, the building DNN7 should be recommended, no doubt. So this building focus on more attentions on integrating with DNN7 framework, for example, the separate url provider based "Advanced Url" component of DNN core. More exciting things are lots of handy featured implemented in this package. Seamlessly integration with 3rd party commercial module also taken into account, for example, MyTokens now supported well. Hope win business together :)

Why not have a try? Get started now.

SunBlogNuke Version 7.0.5
Min DotNetNuke version required: v7.1.0

• ENH - supported email templates for subscription feature and now you can configure different email templates for specific blog instance.
• ENH - supported to access more properties of DNN core profile in the theme level, such as FirstName or LastName of blog author like "<%=Entry.AuthorProfile.FirstName%>".
• ENH - supported category image to show in the list of dashboard if exist.
• ENH - supported 'bulk delete' action for entries list of dashboard.
• ENH - meta title/description & header for archives view configurable for better SEO purpose.
• ENH - resolved ugly slug with friendly text/characters, for example, it will automatically transform "some $ugly ###url wit[]h spaces" into "some-ugly-url-with-spaces".
• ENH - integrated with MyTokens module(http://my-tokens.dnnsharp.com/) of DNNSharp corp, including dnn core tokens.
• ENH - totally compatible with DNN7
• ENH - integrated with lots of DNN7 core features, such as friendly url extesnion.
• ENH - supported new search API of DNN7 with implementing "ModuleSearchBase".
• ENH - replaced code editor in theme customization panel with dnn core one - CodeMirror plugin.
• ENH - disabled keywords auto retrieved from tags when empty due to irrelevant keywords - http://sixestate.com/meta-keyword-tags-still-useful/.
• ENH - updated obsolete methods & profile widget.
• ENH - support option to limit page links of pagination control.
• ------------------------------------------------
• FIX - post thumbnail removed after editing post and threw exception when uploading the same thumbnail.
• FIX - blog export url not found 404 when portal built by sub folder format like "http://www.domainname.com/subportal_xx".
• FIX - enclosure url not resolved with absolute path in the RSS feed.
• FIX - Google recaptcha not built by https with DNN secure enable.
• FIX - shortcut ctrl-enter feature of search box not work with DNN7.
• FIX - social icons not pop up properly on hover status with DNN7 style.

As usual, the complete details for all of the changes can be found in the Release Notes.

If you are still using older versions, we recommended that you should upgrade this stable package.

If you are applying upgrade process, please BACK UP YOUR CHANGES BEFORE PROCEEDING and follow up the suggested upgrade path: v2.1->v5.2->v6.0+.

You can get it here. We hope that with this generation dnn blog module you can enjoy the blog writing and it will make your life better; plus if you have any good advice about our products, please feel free to leave a comment or contact us.

The SunBlogNuke Team

As we promised ever, we always maintain the independent branch of SunBlogNuke compatible well with older version of DNN  CMS, such as the DNN4-building.

Today we would like to announce that we have built another compatible package of SunBlogNuke for DNN5.2+.

Even through you are still using the DotNetNuke 5, you don’t have to be worry about it and just feel free to let it there without any update as you like. Surely, the development status is still active; we will include updates with fixes if necessary.

You can get it here. We hope that with this generation dnn blog module  you can enjoy the blog writing and it will make your life better; plus if you have any good advice about our products, please feel free to leave a comment or contact us.

Note:

1) If your dnn website is DNN5.2 above, you should ignore this package and get more latest package.

2) We may charge $25/hour for premium support of these compatible buildings or some additional feature requests.

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

BTW,  if you would like to upgrade it with latest package in your DNN5/DNN6/DNN7+ website, the recommended upgrade path will be changed as follows:

v2.x/v3.x/v4.x –> v5.2 –> v6.2 or the latest package

And if you are troubleshooting with upgrade, please take a look at these tutorials below:

Common problems with SunBlogNuke

Known issues related with upgrade

As you know, the simple method GetTab(int tabid) was obsolete and has been replaced by GetTab(ByVal TabId As Integer, ByVal PortalId As Integer, ByVal ignoreCache As Boolean). If you want to call the new method, we have to pass the additional parameter “PortalId”.

In common,  the object PortalSettings can be easy to get with DNN context, such as special dnn module & page; however, it may be inaccessible in some sceneries, such as separate aspx page or handler. Then is there any way to get the correct tab info with this new method? Now there is a simple trick to do it with passing into Null.NullInteger as the parameter PortalId. So the coding looks like that:

var tabController = new TabController();
var blogPage = tabController.GetTab(tabID, Null.NullInteger, false);

Deeping into the source code, you will find out that it always tries to get the correct PortalId for this tab/page object:

//if we do not know the PortalId then try to find it in the Portals Dictionary using the TabId
portalId = GetPortalId(tabId, portalId);

//if we have the PortalId then try to get the TabInfo object
tab = GetTabsByPortal(portalId).WithTabId(tabId) ??
        GetTabsByPortal(GetPortalId(tabId, Null.NullInteger)).WithTabId(tabId);

Hope this trick & tip helps if someone has the same issue.

Recently we are building a totally new branch of #DNN #Blog #Module – SunBlogNuke based on DNN 7.1 core framework. As you know, DNN7 indeed introduced lots of awesome features, including advanced url rewrite solution. There are more topic about DNN7, however, we just share some interesting things about new class "ModuleSearchBase".