SunBlogNuke - DotNetNuke Blog Module

Issue Detail

Lot of logs in Event Viewer related with "Scheduler Exception -Sequence contains more than one matching element". This occurs when there is a duplicate entry in the WebServers table.

Solution

To verify if this is the issue, go to Host > SQL and run the following SQL query:

SELECT ServerName FROM {databaseOwner}[{objectQualifier}WebServers]

If you see the same entry more than once, you need to run the following SQL query:

DELETE FROM {databaseOwner}[{objectQualifier}WebServers]

Once that has been completed, hover over Tools->Recycle Application Domain to make it work with re-indexing.

Referrence

Scheduler Issues in DNN 7.3.x

Scheduler exception after Upgrade to 7.3.0

DNN 7.3.1 SCHEDULER EXCEPTION

Well, let us get started to fight DNN Bugs again. This is the forth post we discussed about DNN bugs and share workarounds with you. The last posts as follows below:

1. Fighting DNN Bugs: All Handlers Not Work
2. Fighting DNN Bugs Ⅱ: Why Can't Remove Google Analytics
3. Fighting DNN Bugs Ⅲ: Why Non-Administration Users Logged Out

which you also are interested in reading.

Today we would like to share the bug is about spammer, mainly about spammer registrations/login attempts. When looking/monitoring Admin -> Event Viewer, there are a ton of event log recorded off type "Login failure" or "New user", then your website should have been hit by an old robot-script written specifically to target DNN website.

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

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

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".

As you know, currently DNN is growing bigger than what you expected and the latest version is 7.2 building with lots of awesome features. However, in my opinion, we encountered more and more problems in the same time – tons of versions with tons of existing bugs to be fixed. More frustrating things are that some bugs exists cross DNN4-DNN7 and still not fixed now even though they are created into issue tracker.  Well, if they are ignored with the official guys, let us check them out and address some workaround to fix them forever or temporarily. Today we get started to build a series of posts and share how we fighting DNN bugs these years :(

Today we are glad to announce that SunBlogNuke v6.1 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 more and more websites built by SunBlogNuke, our clients not only focused on the efficiency and better usability but also asked more requests about the performance of this publishing tool. Indeed it is time to speed up another performance action. We reviewed the performance of all the store procedures with SQL Server Profiler and invested where it was running slow and why. In the process, we built accurate iteration to fix them with running lots of testing. Even through we may missed something else,  there had been no sacrifice of quality and stability in the SunBlogNuke product and we assured you that the SunBlogNuke v6.1 will be speeded up in your DotNetNuke website.

Why not have a try? Get started now.

Major Highlights in v6.1:
Min DotNetNuke version required: v6.0.0

• ENH - SQL optimizations with better performance, mainly for default blog view and Content Slider Widget.
• ENH - supported new tokens "DigNum" and "BuryNum" for post entity.
• FIX - upgrade issue from "4.8.0" to "6.0" caused by SQL script.
• FIX - approved/rejected links always show when posting new comment.
• FIX - date time not referring to the preferred timezone of every current user any more.
• FIX - email notification not delivered when new comment posted.
• FIX - threw exception when aggregate feed based on portal level.

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+.

NOTE: from v6.0 the SunBlogNuke will begin to not support DotNetNuke 5.x any more because it will utilize core APIs introduced from DNN6+, such as daylight savings time. If you are still using the dnn5, you don’t have to be worry about it because we will also maintain independent branch of the older version 5.8.x, which will always be compatible with dnn5 and may be updated with fixes without new features any more.

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

Actually everyone was looking forwards to DotNetNuke7, which should be equal to the so-called milestone, however, more expectations more disappointed. Let us take a look at the votes in codeplex – until today only average 2.8 rating with lots of lowest 1 star. In my opinion, that may be the lowest rating of all the releases before. Let’s make a discussion why it occurred and how we feel.

The SunBlogNuke team is excited to announce the final release of 5.6.2 today. This release mainly focused on fixes introduced by last version and also some enhancements. More exciting is that we completed some compatible testing on #DNN7 and it runs well. If you are still using older versions, we recommended that you should upgrade this stable package. Now let’s go through all the awesome highlights included in this buildings :)