In a freshly created DNN v7.3.1 website, I have run into a problem using code from "Creating a Responsive Twitter Bootstrap Skin for DotNetNuke 7 Part 2 - Skin Objects". I get the following error:



I have consulted Google and has been suggested that I set:



That doesn't seem quite right. Any suggestions?

(The code that I used is taken directly from zzze_Bootstrap_Skinning_Part2_7719.zip)

Can you describe how you are using the code from the tutorial? Are you using it in a custom skin?

Exactly when and where does the error occur?

In my test DNN installation, I created the following folders:

\Portals\_default\Skins\Bootstrap
\Portals\_default\Containers\Bootstrap

Then from the zip file

zzze_Bootstrap_Skinning_Part2_7719.zip

I copied the contents of the Skins folder from the "Bootstrap Skin Resources\Complete\Skin\Bootstrap" to the folder \Portals\_default\Skins\Bootstrap. Similarly, I copied "Bootstrap Skin Resources\Complete\Containers\Bootstrap" to the folder \Portals\_default\Containers\Bootstrap.

Everything looked fine and matched the video until I click on Login and then I get the error message:

[HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (.]
System.Web.HttpRequest.ValidateInputIfRequiredByConfig() +12703455
System.Web.PipelineStepManager.ValidateHelper(HttpContext context) +166

I am running:

DNN v7.3.1
.NET 4.0.30319.18444
Microsoft-IIS/7.5
Microsoft Windows NT 6.1.7601 Service Pack 1

Were you able to resolve Steve? I followed along with the tutorial and ran into the same problem. I also tried copying the completed files but they are throwing the same error.

Some things to check:

First: "can you please check your web.config file and ensure that requestValidationMode="2.0" is set on the httpRuntime node - this exception most commonly comes up if that is missing or set to 4.0 (DNN only supports 2.0 = we add this during install but if a sites permissions are wrong and we cannot update web.config this exception can appear)"

Second"

"The problem is when you have a Dnn page with a name that includes non-ascii characters (such as icelandic, or japanese), and using a module container which includes the ability to show the 'commands' for a module (usually 'edit content' and 'settings') - the code that generates the Urls for the popup window links for those module-specific commands double-encodes the Urls, which ASP.NET throws an exception on.

It's not specifically related to the Url Master module and affects the core code as well.

There are a couple of workarounds:
- use the DNN 6 'manage' or the DNN7 floating module menu to access the module commands. It will help to use a module container that doesn't show the other values - the dnn6 & dnn7 standard containers do not show the module commands, as they rely on the in-built module menu.
- switch off popups for the site."

Both of these comments seem to imply that special characters in page names may be related to the problem.