Realized certain video files were not showing up even after going to File Management and Synching the folders. The dnn site you to set the acceptable file types.
When publishing site to live, trying to go to site gives a Server Error – Runtime Error. Looking in the Application logs on the server gave " The directory App_WebReferences/ is not allowed because the application is precompiled." This was causing a bit of stress to a programmer in a our company since he tried to publish a change during business ours. Solution http://stackoverflow.com/questions/9892646/how-publish-my-web-site When publishing the options that work are to have “Delete all existing files prior to publish”, and “Precompile during publishing” checked. And “Exclude files from the App_Data” unchecked.
The popup shows up, but after it pops up the whole page becomes unusable. So not only was it not displaying right, the whole page is frozen. I found a StackOverflow post, below describing how the popup may have that behavior when it is nested inside elements that have positioning elements, which fits with previous experiences I have had. One of the answers described how appending the modal popup to the body of the page "$('#mytModal').appendTo('body');" would be a way of getting it out of any positioning elements. Previously on a different page I had moved it out of some divs and it worked right. However in this particular site the modal is in a ASP.Net site as a user control where the "offending" positioning element is in the master page and it contains the user control. I stuck the script in the user control, but the behavior was the same. When I used Firebug I saw that I was getting a "$ is not defined" message. With Jquery we ne...
http://www.dnnsoftware.com/forums/forumid/198/threadid/527555/scope/posts/threadpage/2 Found out our app pool is recycling every minute or so due to unrealistically low virtual memory settings, and that was causing problems. That Site Crawler seems to be used for when you use the site search functionality. However I have disabled that Site Crawler in HOST->Scheduler which we do not use, and that got rid of the error.
Comments
Post a Comment