-
-
Welcome to another installment of the DotNetNuke Tips to help simplify your life. This is a simple one, but can save you a TON of headache and troubleshooting.
I was helping a coworker out today, trying to track down a gremlin for a new development install on Windows XP SP2. The coworker, we'll call Whistle, was having troubles getting his new environment up and running. The site wouldn't run thus it wouldn't create the proper database tables, stored procs and related data.
After a few minutes of beating his head on the desk I sat down to assist. He had completed the usual setup process, created a database, extracted the ZIP file, modified the web.config file for the newly created database, and of course, he set the proper permissions on the folders.
But for some reason the site wouldn't load in IE, repeating errors that DNN was unable to modify the web.config file. After his 10 minutes, and myself spending another 5 minutes trying to get it running we ran across the most simplest of issues, that I'm sure many of you have also faced, as have I a few times as well.
When you setup the permissions on your folders, if you're on a domain, and setting up an IIS5 machine (Win2k or XP) be sure to change the "LOCATION" of the user to be the local machine and not the domain ASPNET user!
Such a simple thing, yet very easy to miss and hard to track down. Stay tuned for more DotNetNuke tips, brought to you by Chris Hammond from Engage Software.
-
-
It's been an interesting ride the past two years. At Engage Software DotNetNuke has gone from a small portion of our business to being a VERY large part of the business. So much so that we need to hire more developers!
We're looking for some college students who have recently graduated or will graduate in the next year or two who are looking to get some great ASP.Net experience and also get to learn the ins and outs of DotNetNuke. If you're interested send your resume to chammond @ engagesoftware.net
-
-
Has anyone else had a HUGE influx of comment spam on your CS sites lately? (I'm assuming quite a few folks are seeing this)
Over on ChrisHammond.com (upgraded to 2.1 a few days ago) I've been getting close to 100 spam messages a day. While it's nice to have the CS 2.1 spam filtering running over there, I'm curious if anyone has looked into where it's all coming from???
-
-
Incase anyone missed the emails from Admin earlier, the deluge of spam notifications that went out earlier was due to a backlog of emails from 3-4 days. Here's a copy of the email
"All,
The email job did not successfully run for approximately 3-4 days so you may have just received a large amount of comment notifications, etc. (of which undoubtedly some will be for SPAM comments). This IS NOT an increase in SPAM. In fact, we put new rules in place as a result of the recent SPAM and now auto-delete approximately 99% of the incoming SPAM.
Before deleting SPAM, please forward an example (assuming you get multiple) to
Regards,
ASP.NET Weblogs Team "
-
-
Perhaps you need to run a webservice inside an instance of DotNetNuke. If you've tried by just copying the webservice directory out there you've probably been frustrated with the result.
The fix is pretty darn simple. First thing, create a virtual directory in IIS for your web service folder.
Second, copy the BIN files from the DotNetNuke/bin folder to the webservice/bin folder.
In the webservice web.config file add the following to System.web
<httpModules> <clear />
</httpModules>
That will clear out the httpModules that DNN loads, thus allowing your webservice to run on it's own.
<clear />
</httpModules>
That will clear out the httpModules that DNN loads, thus allowing your webservice to run on it's own.
12/4/2010 An update to this blog post
I found another useful resource for IIS7 and getting a virtual directory to run Under DotNetNuke, follow the instructions on this blog post.
-
-
If you're looking for a Pontiac in St. Louis you've come to the wrong place!
If you're looking to buy a Nissan 350Z then you're in the right place! I'm selling a 2003 Nissan 350Z. Stay tuned for more information!
-
-
Perhaps you're running a professional website and don't want your content authors entering smileys into their content? The latest version of DNN with the FreeTextBox provider by default allows anyone with FTB access to put smileys in their content.
To remove the smiley toolbar button you'll need to recompile the Provider.Ftb3HtmlEditorProvider project.
In the Ftb3HtmlEditorProvider.vb file go to Line #318 and comment that line out.
Recompile the project and deploy the newly updated DotNetNuke.Ftb3HtmlEditorProvider.dll.
-
-
Here's a blog entry from Shaun Walker discussing DNN having any sort of chance at the Packt Open Source Content Management System award.
Hopefully we can drum up enough nominations to show that DNN is a force to be reconned with, even in the open source world where "MS IS BAD"!
If you want to nominate DNN be sure to visit the Nominations page!
http://www.packtpub.com/nominations
-
-
Since I've yet to have time daily to post a new DotNetNuke tip I'm renaming my feature to just be DotNetNuke tips! I'll continue to post them when I have the time to do so.
While I was off meeting with a client DotNetNuke dropped a new release! Go out and get it!
If you're running any of the recent releases 3.3.* or 4.3.* it's highly recommended you upgrade to 4.3.4, there were some security issues found and resolved with those releases.
More DotNetNuke Tips next week.
-
-
If you're looking to pimp your myspace profile click here.
Just another blog post to help out another project