SunBlogNuke Team Blog

Share you with any news or development process about our dnn modules, such as status or release notes.

First time here? You may want to check out the blog archives, subscribe to the RSS feed, sign up for free email updates, or follow me on Twitter. Thanks for visiting!

Posts Tagged 'troubleshooting'

We are pleased to present below all posts tagged with 'troubleshooting'. If you still can't find what you are looking for, try using the search box.

Scheduler Issues with DNN 7.3.x

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

DNN Tips: GetTab Method without DNN Context

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.

Fixed reCAPTCHA issue with SunBlogNuke

PS: now you can simply upgrade SunBlogNuke with the latest package to exclude this bug.

Currently  some clients raised some problems with error information "That assembly does not allow partially trusted callers" when visiting the post detail page of our dnn blog module - #SunBlogNuke. After looking into the issue, it looks that the Google reCAPTCHA control dose not work with partially trusted callers. To fix it, please try out the following ways:

1) Please open your web.config file and find out the <trust> element. If it is open please modify the level attribute as 'High' or simply remove the <trust> element with commenting it:

Original may like that:

<trust level="Medium" originUrl=".*" />

Modified it like that:

<trust level="High" originUrl=".*" />

or comment it like that:

<!-- <trust level="High" originUrl=".*" /> -->

     If you are in a shared hosting environment, you may need to talk to your hosting provider, some providers may not allow you to run in Full Trust mode.

2) Another solution may require a upgraded assembly for Google reCAPTCHA control. Please refer to this post in details http://code.google.com/p/recaptcha/issues/detail?id=100. Just download the fixed assembly and replace the original one in the bin folder of your website.

Hope it helps if you encounter the same issue. If you have any question please leave your comments or raise it in our forum. :)

Similar resource links:

http://www.dotnetnuke.com/Resources/Forums/forumid/136/postid/143336/scope/posts.aspx

Important Fixed Version 4.7.2 for SunBlogNuke

Today we would like to release the important fixed version 4.7.2 for Ultimate DNN Blog Module – SunBlogNuke, which included urgent  fixes , such as exception "attempted to divide by zero" threw  when adding module into page and it raised in the community forum here - Divide by Zero Error. Also we enhanced Content Slider Widget with ability to support customized property value of the dnn core profile for Author entity in the CSW, like [AUTHOR:Website]. Importantly we supplied a new solution to avoid multiple jQuery conflict issue when other modules also included jQuery framework and fixed threaded comments broken in the "_default" theme.  As usual, the complete details for all of the changes can be found in the Release Notes.

More exciting is that the next generation of SunBlogNuke v5+ have been on road, which will be done with DNN6 release available. It will take advantage of all the benefits of the latest dnn core framework. So here we announced that the upcoming v5.0 will not support dnn4 any more because it will utilize lots of core APIs introduced from DNN5+, such as Taxonomy. You don’t have to be worry if you are still using the dnn4. Meanwhile we will also maintain the older version 4.x compatible with dnn4.  Please stay tune :)

Major Highlights in v4.7.2:

  • ENH - Supported customized property value of the dnn core profile for Author entity in the CSW, like [AUTHOR:Website].
  • ENH - Added auto-ping service for trackback requests.
  • ENH - Excluded handlers from web.config, which introduced lots of problems with complex dnn environment.
  • FIX - Multiple jQuery conflict issue when other modules also included jQuery framework.
  • FIX - Threw exception (attempted to divide by zero) when adding module into page.
  • FIX - Threaded comments broken in the "_default' theme.
  • FIX - Datetime token tags, such as 'PublishedDate', not resolved correctly in the CSW.
  • FIX - 'Alternate Feed Url' meta tag not show.
  • Lots of fixes & customizations.

NOTE: As with any release, we recommend you perform a complete file and database backup before performing any upgrade on a production website and that you first conduct a trial upgrade on a staging version of the site. Following these guidelines will ensure that you are able to recover should any unforeseen problems arise during the upgrade process.

Note that some issues may occur if your original version of SunBlogNuke is lower version, like 3.x, and you've developed your customized theme. Please refer to the tutorial - Must-Read Note for SunBlogNuke v4.x and follow the instructions. Hope it makes sense.

You can get it here. Blog your way and enjoy life. :)

The SunBlogNuke Team

A Quick Note for Enhanced and Fixed Version - SunBlogNuke 3.7.x

As you know, we recently released Ultimate DNN Blog Module – SunBlogNuke v3.7.x with some enhancements and small fixes, including code refactoring. When you would like to upgrade this version, please note that if you had developed any customized theme ever you MUST modify all view files lightly, including BasicView.ascx, DetailView.ascx, CommentView.ascx, TagsView.ascx, SearchView.ascx, and PrintView.ascx. Just follow the two steps below:

  1. Find out your customized theme folder which should be placed in the $YourRoot/DesktopModules/SunBlog/Themes/YourCustimizedTheme/.
  2. Open up the BasicView.ascx, find the first line declaration and modify it like that:

    Original:

    <%@ Control Language="vb" AutoEventWireup="false" EnableViewState="false" Inherits="DnnSun.SunBlogNuke.Framework.PostViewBase" %>

    Modified:(yes, it is so easy and just modify "Framework" into "UI".)

    <%@ Control Language="vb" AutoEventWireup="false" EnableViewState="false" Inherits="DnnSun.SunBlogNuke.UI.PostViewBase" %>
  3. Like the step 2), check out whether there is declaration about Toolkit. If exists, modify it like that:

    Original:

    <%@ Register TagPrefix="toolkit" Namespace="DnnSun.WebControls.Toolkit" Assembly="DnnSun.Modules.SunBlogNuke" %>

    Modified:(You should notice that just modify "DnnSun.Modules.SunBlogNuke" into "SunBlogNuke.Core".)

    <%@ Register TagPrefix="toolkit" Namespace="DnnSun.WebControls.Toolkit" Assembly="SunBlogNuke.Core" %>

The same process for the other view files.

In the end, make sure you MUST follow the tutorial if you had developed any customized theme ever, otherwise you will encounter the error like "Could not load type 'DnnSun.SunBlogNuke.Framework.PostViewBase'.". When you visit your good main blog page in your dnn website. If not just skip it :) Hope it makes sense for you.

Troubleshooting SunBlogNuke Installation

During Ultimate dnn blog module – SunBlogNuke installation, different problems may arise which pop-up frequently on the SunBlogNuke Support Forums and it may stop an installation dead in its tracks. Today I am attempting to cover solution for these issues and hope it makes sense while you are facing the same problems.
Copyright © 2009-2020 Ultimate DNN Blog Module - SunBlogNuke Powered by SunBlogNuke Corp