Portal Rule fails

We have recently made changes to our company website that has PageBlaster 02.02.04 installed.

We had a friendly URL pointing to a page that has now turned into a forwarding link to one of the new pages on the site (Set under page settings Advanced Settings - Other Settings - Link URL).

However the friendly URL has stopped working and redirects to the home page ever since the website change so we have tried the following:

• Deleted and re-added the portal rule in PageBlaster
• Created a new tempoary page and assigned the old friendly URL to that page but again it redirects to the home page
• Looked through various config files under the DotNetNuke folder and identified only one entry for this rule

We've tried all different combinations of settings in page blaster but which ever page on the site we add the friendly URL to the page then instantly stops working and can't be accessed.

The only other custom modules we have installed on the website is ODS form but this problem did not exist until I made changes to the website.

We have a feeling that there is a duplicate somewhere in the PageBlaster configuration which is causing a conflict but are unsure what files to check to see if this is the problem.

I hope someone can give me advice on what I could check to identify where the problem is.

Thanks for any help on this matter

Hi John, I opened up my web.config file found under the dotnetnuke folder and changed the order of where PageBlaster comes. It is now the next line under UrlRewrite. 

Having then saved the file, our company website started to randomly break and pages got the following errors:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

or:

2) Add the following section to the configuration file of your application:







Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Services.Localization.Localization.GetEnabledLocales() +43
DotNetNuke.Framework.PageBase.get_PageCulture() +33
DotNetNuke.Framework.PageBase.OnInit(EventArgs e) +40
System.Web.UI.Control.InitRecursive(Control namingContainer) +321
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +834

[PageLoadException: Object reference not set to an instance of an object.]
DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +377
DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +485
System.Web.UI.TemplateControl.OnError(EventArgs e) +2085460
System.Web.UI.Page.HandleError(Exception e) +71
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +7341
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +213
System.Web.UI.Page.ProcessRequest() +86
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
System.Web.UI.Page.ProcessRequest(HttpContext context) +49
ASP.default_aspx.ProcessRequest(HttpContext context) +4
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +358
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64




--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

What did I do wrong?

I should add that I am a basic DNN user and have little experience using this system.

We originally had a page appear under a product section of our website which had a friendly URL that was published on a number of literature and websites and it also appears on google searches. We added a new page under another section of the website and wanted the friendly URL to come to this new page. As we also wanted the new page to have a new friendly URL we could publish in the future I thought I could keep the old friendly URL pointing to the old page and change the old page to redirect to the new page. However when I implemented all the changes the old friendly URL when entered into a browser would just bounce back to the home page.

I thought it might be a problem with having a friendly URL pointing to a bounce page so attempted to add the old URL to another new page I had created (deleting any previous settings from the old page first) but which ever page I add the old friendly URL to then breaks and whenever I navigate to it either through the website or by using the friendly URL it bounces back to the home page. Since this problem started I have been able to create new friendly URL's fine for other new pages but it is only this old friendly URL that seems to have an error.

I hope that makes it clearer but if it doesn't I might have to make a drawing!

Any ideas what I can try next?

Thanks John after cleaning up that file and re-adding page blaster to the pages seemed to solve the problem. However PageBlaster didn't like having a URL pointing to a page on our site that is set to forward to another page as DNN threw up an error. Instead I've put the old friendly URL to one of the new pages.

Thanks for all your help.