Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade to 8.00.00 Critical IssuesUpgrade to 8.00.00 Critical Issues
Previous
 
Next
New Post
6/7/2016 5:23 PM
 

Hello, I agree with Richard Howells that his default.css should be the correct one.  However there is something odd with DNN 8.0.  With the recent current critical vulnerabilities allowing site takeover we need to upgrade.  But we cannot release when the Login button is not even visible.  

The issue stems with the periods in the path, specifically the "7.0.0" folder.  The 8.0.0 is not accessible either.  If I move the css file to a folder without the periods then it will work.  This forced path is something in NUKE not in any other module or anything.  There is evidence of this in UpgradeWizard, and the Install.htm files where you can see the reference in the image below.  The authors of our skin say they cannot find how to change the path. 

 I have looked in through DNN in the database and through the files for several hours today but I cannot see where to change the path.  I have tried a couple other workarounds but none of them work.  The j0ys of nuke. So I am asking you guys, how do I force it to change the path?  


 
New Post
6/7/2016 5:49 PM
 
ISTM that this is not a DNN issue. The file (I presume) actually exists on your server, but your IIS will not serve it to the browser. I think you need to find out why and correct it.

I'm not running DNN 8 so I cannot test your configuration.

I suggest you begin by copying some arbitrary image to a name with 8.0.0 in it and see if you can request that directly from the browser. If you can't then you have confirmed that this is not a DNN issue and you can get started on correcting the underlying problem.

On my system (Windows Server 2012) it happily serves up a jpg file with 8.0.0 in the name. Does yours?


Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
6/16/2016 6:34 AM
 
Hi,

I too was having this issue. It was because we recently started using Microsoft's IIS tool URLScan.

Here was my fix:

Go to: "C:\Windows\System32\inetsrv\urlscan\UrlScan.ini"
Change “AllowDotInPath=” to 1
This should then allow the dots/periods in the URL paths (our problem was the "7.0.0" and "8.0.0" paths

Regards,
James
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade to 8.00.00 Critical IssuesUpgrade to 8.00.00 Critical Issues


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out