7.1 error page for 404 is not showing up - http-status-code-404

I have a dnn 7.1.1 installation I am testing for production. I thought that this version supported a 404 error page. But no matter what type of erroneous url I pass to the DNN site I don't get this page appearing and I don't see it under admin/page management. DO I have to turn this feature on some where? This is a brand new install and the following page says it should be turned on by default: DNN 404 wiki
I could not find any setting in the root web.config. The advanced url provider is enabled.
Can someone help me figure out how to timplement this 404 error page
Thanks in advance
EDIT 1:
Can someone confirm that 7.1.1 is the minimum version for this feature, or is it only with the professional version, I am using DNN platform.
EDIT 2:
See HERE for link to DNN issue tracker. I have tried this both with a new installation and an upgrade from 7.0.6 and the problem continues. If you ask for an non-existent resource with an extension you get a generic asp server error:
Server Error in '/' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its
dependencies) could have been removed, had its name changed, or is
temporarily unavailable. Please review the following URL and make
sure that it is spelled correctly.
Requested URL: /blob.aspx
if you request a page wihtout an extension like /blob you get one of two errors:
404 Not Found
The requested Url does not return any valid content.
Administrators
Change this message by configuring a specific 404 Error Page or Url for this website.
OR
The resource you are looking for has been removed, had its name
changed, or is temporarily unavailable.
There is no 404error page in the admin/page management section of the site in either the upgrade or brand new instal. The new instal was deployed uwing Azure website Gallery for DNN 7.1.1.
I manually upgraded a 7.0.6 instance to 7.1.1 to get the other testing environment.
EDIT 3:
Okay, so I know how to reproduce this. If you create a new portal/site with the blank template then there is no 404 error page under admin/page management. If you create a site with the default English template then the 404 error page is listed in page management and the 404 page shows up when you request a deadpage.
WHat I tried:
I copied the 404 error page from the default template site into the blank template site hoping that this would fix the problem. It did not. So now I think that there is a setting that needs to be enabled somewhere, but I know it is not in the web.config file because both these portals are in the same dnn instance and one works and the other does not, so there is another place I have to find this.
EDIT 4:
I don't have a work around other than creating new site with default template and recreating a site. It appears that this error is planned to be fixed by 7.2.1 as documented HERE
EDIT 5:
I dug through the databse to see if I could find a setting that would make this work. The only setting I could find was in portal settings (called 'AUM_ErrorPage404'), so I duplicated it with the following script but changed the portal and tabID to match the portal that was created with the blank template .
This added a setting to portal settings that assigned a error page to the portal. I found this setting for the default template and not the blank template. SO I added it hoping it would solve my problem. It did not.
INSERT INTO [dbo].[PortalSettings](
[PortalID]
,[SettingName]
,[SettingValue]
,[CreatedByUserID]
,[CreatedOnDate]
,[LastModifiedByUserID]
,[LastModifiedOnDate]
,[CultureCode])
VALUES (
[PortalID]
,'AUM_ErrorPage404'
,[TabID of 404 Page I Created]
,[CreatedByUserID]
,getdate()
,[CreatedByUserID]
,getdate()
,'en-us')
I found no settings for the 404error page/tab in the [TabSettings] for the page created in the default template, in fact, there were no records in tabSettings for the error page created in the default template portal..
A brand new site created with the default template in 7.1 only has the following portal settings (with values):
AUM_ErrorPage404 371
DefaultAdminContainer [G]Containers/Gravity/Title_h2.ascx
DefaultAdminSkin [G]Skins/Gravity/2-Col.ascx
DefaultPortalAlias test404
DefaultPortalContainer [G]Containers/Gravity/Title_h2.ascx
DefaultPortalSkin [G]Skins/Gravity/2-Col.ascx
EnableSkinWidgets True
GettingStartedPageShown True
GettingStartedTabId 346
MaximumVersionHistory 5
PortalAliasMapping CANONICALURL
SearchAdminInitialization true
TimeZone Pacific Standard Time
I am not sure where else to look in the DB for a setting to chnage

After some research and hours of frustration. I found that a new setting is required in version 7.2.2:
The table: PortalLocalization now contain two fields: Custom404TabId and Custom500TabId, those fields need to be updated with the same value of the PortalSetting AUM_ErrorPage404, AUM_ErrorPage500 so if you upgrade from a version below to 7.1 probably you have to update those fields by yourself.
Hope this save time.
Israel Garcia

Okay, I got it to work!
The script above did the trick:
INSERT INTO [dbo].[PortalSettings](
[PortalID]
,[SettingName]
,[SettingValue]
,[CreatedByUserID]
,[CreatedOnDate]
,[LastModifiedByUserID]
,[LastModifiedOnDate]
,[CultureCode])
VALUES (
[PortalID]
,'AUM_ErrorPage404'
,[TabID of 404 Page I Created]
,-1
,getdate()
,-1
,getdate()
,'en-us')
The missed step:
After adding the setting for AUM_ErrorPage404 I had to clear the cache and restart the application. Now it works.

Related

Salesforce: Visualforce pages not working anymore because of certificate error

I have a dev box running with a namespace and just added a demo visualforce page named "test" and just clicked on "Preview". It is ending up with a certificate error on my browser.
The URL salesforce tries to open is https://myinstance-dev-dev--mynamespace.visualforce.com/apex/test
The certificate being provided by this domain is for "viv1.force.com". That is why my browser is blocking it.
Any idea why this is happening? My visualforce pages were working on the dev box, but now suddenly end up with this error.
Strange solution. Had to check "Critical updates" on setup, and DEACTIVATED the setting "Stabilize URLs for Visualforce, Experience Builder, Site.com Studio, and Content Files". Now it is working again.
I assume for some reason this stabilization missed to change the used certificate behind visualforce pages. Deactivating above option fixed it.

Error 500 - Angularjs with DNN - Christoc.Module ng-include

I have an application that I build using VB.NET and angularJS in DNN with the Christoc.Module module. There seems to be 2 issues. When I build my project and refresh the page on my site, I will receive an error 500. The same result happens on the site unexpectedly after being idle for about 30 minutes. I have tried to change settings on the website web.config to see if it was a session expiry timeout, but that doesn't seem to be the case since all pages that where access before the error are fine, and can access server functions.
I was wondering if anyone has ever seen something similar.
I use ng-include to show the current "active page". I have tried using the AngularJS $route and the same behaviour occured.
<div class="animate-repeat" ng-repeat="path in PathLinks| filter:{'path_name':variable}:true" ng-include="'/DesktopModules/module/path/' + path.path_name + '.aspx></div>
CLick here for image of the issue
I ended up simply recreating the whole module with a newer version of the visual Studio DotNetNuke Compiled Module. The original module was created using an older version of that extension. This seemed to have completely fixed the issue for me.

Unable to add a new page in DNN9 (dotnetnuke version 9)

I installed dnn version 9. When I want to add a new page I go to the contents-> Pages-> Add page. an empty white page appears without any options to add a new page or event to cancel.
This is caused by a problem with your templates folder, either missing, or bad permissions. I'm guessing when you installed you chose the blank template?
I've got a blog post on things to try to resolve
http://www.chrishammond.com/Blog/itemId/2692/Canrsquot-add-ldquopagesrdquo-in-DNN9
"If you are having problems adding Pages in DNN 9, read this blog post.
I recently upgraded all of my sites to DNN 9, the most recent one being upgraded last night. This morning I wake up to an email from a client of mine reporting a problem with adding pages in one of their sites that they also upgraded to DNN recently. I read through their email, and decide that I’ll look into their issue a bit later, have an itch to scratch on one of my own websites, so I’ll get to them later (sorry client).
Working on this site that I upgrade last night, I decided I wanted to add another page to the site, low and behold, I was unable to do so.
To add a page in DNN9 you click on the “Content” option in the persona bar, and then the Pages option. There you will be presented with a view similar to this:
image
When I clicked on Add Page there, the screen went blank, like so:
image
That’s not very useful, actually that is as far from useful as possible. Once that happens, you can’t actually “do” anything from an Admin perspective. You have to “leave” this page, go somewhere else (click on manage/users for example, then you might need to click BACK in your browser a bunch of times) then you can click on Content/Pages again to get back into the Page listing for a site.
So why is the persona bar page blank? This error is the cause:
GET https://SOMEPORTALALIASHERE/API/PersonaBar/Pages/GetDefaultSettings? 500 (Internal Server Error)
If you dig into the DNN Error Log (Admin Logs) a bit you might find a more detailed error, something along the lines of
Message:Value cannot be null. Parameter name: source
StackTrace:
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable1 source, Func2 predicate) at Dnn.PersonaBar.Pages.Components.TemplateController.GetDefaultTemplateId(IEnumerable`1 templates) at Dnn.PersonaBar.Pages.Components.PagesControllerImpl.GetDefaultSettings() at Dnn.PersonaBar.Pages.Services.PagesController.GetDefaultSettings() at lambda_method(Closure , Object , Object[] ) at
So what does that message tell you? Well something is happening with your DNN Install trying to get a list of “page templates”. In digging further, on my site, I found the issue to be the File Permissions on the Templates folder in the portals/0/ directory. For some reason on the site that I upgraded last night, my permissions were set to ALL USERS DENY on the “Browse Files in Folder” and “Open Files in Folder” check boxes.
image
Unchecking those, clicking SAVE resolved my “pages” persona bar issues. How did those permissions get set? Who knows, this DNN site has been around since 2008 or earlier, and that never caused a problem.
There are definitely some “kinks” to be worked out of DNN9, but so far I am digging the new experience.
Regarding my “client”’s site, they had a similar, but different issue. In their case, the TEMPLATES folder didn’t exist in the Portal that they were trying to use. Simply creating a new Templates folder in their File Manager fixed that problem for their site."
I tried out many solutions but finally I figure it out by reinstalling and add Object Qualifier. because it is optional field I leave it without any value in my first installation
This error was fixed in DNN 9.0.1

DTM connectivity to SiteCatalyst

I am trying to setup DTM to report to Adobe analytics. I have pasted the header/footer code on my page and I see in fiddler that the "page load" and field level tracking is triggering DTM scripts. But I am unable to see anything in my report suite on Site catalyst.
As per DTM documentation, I have altered the AppMeasurement.js to have the report suite ID
var s = new AppMeasurement();
s.account = "myreportsuiteidonsitecatalyst";
/*
============== DO NOT ALTER ANYTHING BELOW THIS LINE ! ===============
Am I missing anything? Please help.
There's most likely an error in your DTM code. You can use the Chrome extension here to troubleshoot your DTM configuration: http://help-forums.adobe.com/content/adobeforums/en/marketing-cloud-forum/adobe-marketing-cloud.topic.html/forum__lkzf-_dtm_switchdt.html.
In addition, there are fantastic videos here which walk you through the setup of DTM and the configuration of the Analytics tool within DTM: https://outv.omniture.com/ (under Dynamic Tag Management)
You also have to have the tracking server information set either in the code editor window or the UI.
This is the problem even I was facing too.
I have analyzed this problem and get something which is very helpful but not able how to rectify this problem.
As you know sitecatalyst set s_vi cookie in our browser which is persistent, with help of this cookie we came to know that reports are reflecting in sitecatalyst reports. But while using DTM s_vi is not getting set in browser and hences no reflection of reprts in sitecatalyst.
I run my pages in Chrome and found that no cookie is being set in that browser but while using IE s_fid is being created subsitute of s_vi when s_vi not able to create.
So something wrong is with this.
you can check your cookie like _satellite.readcookie('s_vi') or _satellite.readcookie('s_fid')

DNN 7 Can No Longer Edit Page

One of my DNN 7 sites has lost its ability to edit any of the pages. It now alway displays the Modules, Edit and Pages menu regardless if admin is logged in or not. When I try to edit a page, a window appears and then quickly goes away. There is nothing of use in the event log and I have tried different skins with no luck. I have another DNN website on the same computer and it works fine.
I have found that I am losing permissions to ToggleUserMode after I recompile a custom module that I'm developing has been installed on a test page and then recompiled in debug mode.
I'm wondering if this can be related to the fact that when I install DNN I blank out the default installation option of creating a dotnetnuke application. I leave that option blank and create the installation in the root of my website.
P.S I tried the amended module tag suggested on SO without any luck.
I finally figured this out. I had originally bound www.example.com to my default website but later created a new site for www.example.com. Apparently most of the requests were going to my new site, but the request for authorization for page editing was going to my old site which resulted in the 401 error. I rebooted my computer and disabled my default website and all is well.

Resources