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...image path issue - relative setting helpimage path issue - relative setting help
Previous
 
Next
New Post
7/2/2012 8:20 PM
 

Hi guys - I seen to have a relative path issue with my new 6.2 upgrade.  After a few little isssues and some excellent help from this forum the site is mostly going however.  To summarize the physical path is C:\inetpub\wwwroot\Intranet - i have created it as an application under the default website.  Yet when I browse to http://localhost/intranet/Home.aspx the images are broken and the path to docs not correct.

The properties of broken images are http://localhost/Portals/0/FTNetwork.png but of course their physical location is C:\inetpub\wwwroot\Intranet\Portals\0\FTNetwork.png.

So I start looking for some setting under the Host menu to try to fix but cant find any.  So I start comparing Host menu settings between the current production intranet (5.1.4 DNN) and this new 6.2 upgrade.  One difference is that the relative path is'/' in production but the new upgrade this setting is '/intranet' - But under this 'Host Settings' > 'Basic Setting' its read only.  Should I be able to chnage this, is this my issue???

In summry the path inside the broken image tags within the upgrade is 'src="/Portals/0/FTWordDoc-Internal.png' - Since this is coming out of the database there muct be some DNN admin level setting where I can fix this........help

Thank you in advance

 
New Post
7/3/2012 3:29 AM
 
Hi Matthew,

It looks like you are in the development environment where you configured your website as an application under the "Default Website" root.

Sometimes, it create issues like this, when the module is not accessing the path taking care of "Application". If you host the same website in production like "www.mywebsite.com" it would work fine. But when as an application inside a website, it won't work pretty fine.

Now given that you are on development environment, you can add a new website, outside Default Website in IIS and assign port 82 or any other. After this, you can access your site like :

localhost:82

If you are not on dev. environment, in that case, you have to modify something inside the module which is fetching the path from database, in a way that it takes care of application-relative paths.

Hope this makes sense to your problem.


- Ravi
 
New Post
7/3/2012 3:39 AM
 
Also, I feel this issue does not belong to upgrading problem. It is occurring due to the IIS settings. You can experience the same issue with existing site as well (check before upgrade).

- Ravi
 
New Post
7/3/2012 4:10 AM
 
Matthew, if your test website is localhost/intranet, proper path is "/intranet". however it looks like the HTML editor is not taken this into account properly. You may switch using CKEditor provider (dnnckeditor.codeplex.com) for proper relative paths, but be aware, that paths may always fail when moving the same website from production, where it is installed in the domain root to a subdirectory of localhost. If you want to keep proper paths, you should provide an alias for your website, e.g. "myWeb". You'll need to edit system32/drivers/etc/hosts file using a text editor, uncomment line 127.0.0.1 localhost and add tab and "myweb" at the end of the line. Save the file. Now bind your website to "myWeb" and make sure, DNN portal alias table has an entry for your website and "myweb".

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/3/2012 6:31 PM
 
A quick reply to see if I can catch you online - What do you mean by 'Now bind your website t' ??

Also in reference to:

;;;however it looks like the HTML editor is not taken this into account properly

we ahve not added any more content,nor used any editor in the new upgrade. This path issue is for exiting content that was present pre-upgrade.

Is making an application inside IIS on 2008 server (IIS7.0+) the same as right clicking > create in 2003 server (11S 6.0 I think) ??

Thanking you
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...image path issue - relative setting helpimage path issue - relative setting help


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