Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...Using Modules a...Using Modules a...DNN6.2.2 Filemanger HTTP 404 errorDNN6.2.2 Filemanger HTTP 404 error
Previous
 
Next
New Post
8/28/2012 9:26 AM
 
Bill Hart


Joined: 5/1/2012
Posts: 44

Im baffled.

I uploaded 2 files (png images) to the portal in a directory that I made via on my server (using Microsft RDP) and have attempted to use the browser to view the files.... I get a an HTTP 404 error... I can use one of my other domains that are not DNN... simply IIS domains and there is no problem....

I tried using DNN file manager to set the rights on the directory and the file to open files in fold and browse files in folder but that has no effect...  I do not understand what can be keeping the browser from seeing the files.  If I click the files in the file manager... they can open...

 

What is wrong with my understand of files on a DNN server ?  Why are they not accessible ?

Thanks for your help!

Bill 
 
New Post
8/28/2012 10:16 AM
 
Bill Hart


Joined: 5/1/2012
Posts: 44
After investigating I for some hours, I can see that there is a need to add into the url portals/portalID after the root when accessing resources directly... and that these are as well added by the portal when generating the HTML on the server side.

So now I am even more confused... When referncing directly resources on the site in the url of the browser why is it nessesary to add portal/portalID

Example... I place a file called test.aspx in the root of the portal.... then I want to test the file and type into the browser http://mydomain.com/test.aspx and that gives a 404 error. but If i instead by adding portals/PortalID to the url then I can see the resource...

Have I set something up wrong on the DNN installation that requires I add portals/portalID to the url ... this lengthens my urls and is weird... ????

Thanks, Bill
 
New Post
8/28/2012 12:22 PM
 
Bill Campbell


www.pogabacoor.org
Joined: 4/28/2006
Posts: 169
Bill,

It sounds as though you have not quite 'got' DNN.

It's a content management system, so once you have installed DNN, all future site content upload and presentation is managed 'inside' DNN.

Use DNN Filemanager to add directories for your resoures. Use DNN File Manager to upload the resources. Add a page within DNN for viewing the resources, and add Modules to the new page to actually do the viewing.

If you have a local DNN User Group, I would recommend you attend a couple of meetings and perhaps find a one-on-one mentor in your local area to get you over the hump.

Bill
 
New Post
8/28/2012 12:31 PM
 
Bill Hart


Joined: 5/1/2012
Posts: 44

Hey Bill... thats actually not quite accurate... site uploads and management can occur via FTP, via RDP and by simple having physical access to the server where you log on and free move, rename delete resources.

So, Sorry, but that isnt the problem... the problem is that DNN does not treat Portals as a root website... parts of the CMS system do and parts of the Skin / css referencing can... but its strange that portals can not be referenced by their root designation on all resources...

The partial available of root references vs. non root references is what is confusing....  I figured there was a setting somewhere such that I have missed that makes all references absolute from the root and thereby negating the need to place PortalDIR/PortalID into the string.... this isnt very SEO friendly either and it as well devulges part of the file structure. 

 

Would be much more secure if it was a virtual reference to the root... that doesnt revel the true structure....

But thanks for your comment :-)

Bill
 
New Post
8/28/2012 1:56 PM
 
Bill Campbell


www.pogabacoor.org
Joined: 4/28/2006
Posts: 169

Bill,

I get what you are saying, but let me put it to you this way.

On a standard install Home page - nothing in the URL about portal etc BUT right click any of the images in the main page and check properties. There is the Portal/PortalId/file path that you are objecting to. View Source for the page, and yes, some of the resource content paths start from a site root perspective BUT those images are coming from the site root images folder. Anything within the module uses the portal/portalId/ because it is not coming from the root images folder, but from inside the portal/portalId/Installed Module/images folder.

In the viewed source there is an awful lot to reveal this is a DNN site, long before you get to the resource path.

An ordinary user, uploading resources through file manager and viewing them through an installed module would see nothing of the portal/portalId/ file path.

So I'm sorry too - but I do not see an error, I see WAD.

Bill
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...DNN6.2.2 Filemanger HTTP 404 errorDNN6.2.2 Filemanger HTTP 404 error


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