The Salty Economist

Things I Should Have Learned in High School
posts - 56, comments - 0, trackbacks - 0

Subtext Install


Well, I finally got this puppy to work. Took some effort, but we succeeded.


(1) Subtext does not appear to be available on the MS Web Platform Installer. Not sure that is. Perhaps, Subtext has gone by the wayside?

(2) First thing was I had to hack the web.config file to remove the whole section: sectionGroup name="system.web.extensions". Don't know why?

(3) I used SQL Express (2012), but the quick way of creating the database from the .mdf file failed all over the place. So, I just created my own blank database and manually edited the web.config file as: connectionString="Server=AMAZONA-94B9DC6;Initial Catalog=BOBS_BLOG;User ID=mySQLUser; Password=myUserPW"

(4) I had to change the folder security settings on the blog subdirectory: C:\inetpub\wwwroot\BobsBlog go give the IIS User write permissions (I actually gave the user Full Control, but I only think write is needed.

Then I browsed to it and it worked.

Well mostly. I tried adding some HTML to my text a got this big ugly:

A potentially dangerous Request.Form value was detected from the client (ctl00$ctl00$MainContent$pageContent$postsContent$Editor$richTextEditor$richTextEditor

Description: ASP.NET has detected data in the request that is potentially dangerous because it might include HTML markup or script. The data might represent an attempt to compromise the security of your application, such as a cross-site scripting attack. If this type of input is appropriate in your application, you can include code in a web page to explicitly allow it. For more information, see

Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (ctl00$ctl00$MainContent$pageContent$postsContent$Editor$richTextEditor$richTextEditor

So again, I had to hack the web.config file. After a bit of Googling, I discovered something that worked. In the tag System.Web I made the following change:


httpRuntime executionTimeout="90" maxRequestLength="819200" useFullyQualifiedRedirectUrl="false"


httpruntime executiontimeout="90" maxrequestlength="819200" usefullyqualifiedredirecturl="false" requestvalidationmode="2.0"

Print | posted on Tuesday, April 15, 2014 12:33 PM |

Powered by:
Powered By Subtext Powered By ASP.NET