images not displaying after localhost install
Last Post 08/11/2008 3:39 AM by Lee Sykes. 8 Replies.
Author Messages
Ken Maudsley
Nuke Active Member
Nuke Active Member
Posts:24


--
07/30/2008 5:12 PM  
I brought my live site to my localhost production machine following the tutorial in Issue 22. The images in Text/HTML modules use relative URLs (/Portals/0/images/image.gif) and do not display. When I add an image in the production environment, the URL is scr="(portalalias)/Portals/0/images/image.gif".
I want to see the images on my localhost and I also need them to show properly when I take the site back live.
What do I do?
The tutorial shows that the URLs are absolute and therefore pulling from the webserver. Is this what I have to do?
Joseph Craig
DNN MVP
Posts:11667


--
07/31/2008 9:10 PM  
Which version of DotNetNuke are you using? On my 4.8.2 test site, I put this into a Text/HTML module using the image tool:

< img height="160" width="250" src="https://www.dnncreative.com/Portals/5/SamplePicture04.jpg" alt="" / >

It displays perfectly.

Joe Craig, Patapsco Research Group
Complete DNN Support
Ken Maudsley
Nuke Active Member
Nuke Active Member
Posts:24


--
08/01/2008 2:37 PM  
I have a 4.8.4 site and a 4.5.5 site that both have this problem.
My img tag looks exactly like your. If I put the name of the alias into it

<... src="https://www.dnncreative.com/alias/Portals...>

then it displays. In SQL SMS Express, I add virtual directories and think this is the problem. If I specified the Default web site as my test site then I think it would work, but I am new to SQL. I did it like the tutorial and since the tutorial points out the URLs are absolute, I'm not sure what to do as mine are relative.

Thanks for the input.
Joseph Craig
DNN MVP
Posts:11667


--
08/02/2008 8:49 AM  
This shouldn't be an issue with the version of the SQL server that you are using.

Joe Craig, Patapsco Research Group
Complete DNN Support
Ken Maudsley
Nuke Active Member
Nuke Active Member
Posts:24


--
08/04/2008 9:23 AM  
Then I should assume that I have done something wrong. I have repeated the process and watched the videos several times. Before I go back again though, it would be helpful for me to understand why Lee's video shows the absolute URL for images. Was this a function of the DNN version he installed in the tutorial and that has changed since. Thank you.
Joseph Craig
DNN MVP
Posts:11667


--
08/04/2008 9:55 PM  
I'm not sure if that was because of an earlier version of DotNetNuke, but I do know that I can use relative links, provided that the images are in or below the Portal or site root.

Joe Craig, Patapsco Research Group
Complete DNN Support
Lee Sykes
DNN Creative Staff
Nuke Master VI
Nuke Master VI
Posts:4945


--
08/05/2008 6:06 AM  
The absolute URLs have been used due to my FCK Editor settings. - when I create RSS feeds and they use images, they need to have absolute URLs otherwise the images will not display correctly, so a lot of the site uses absolute URLs.
Lee Sykes
Site Administrator
Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

Twitter: www.twitter.com/DNNCreative

Lee Sykes's Facebook Profile
Ken Maudsley
Nuke Active Member
Nuke Active Member
Posts:24


--
08/05/2008 10:20 AM  
Is there a likely cause of this problem (i.e., relative URL images are not displaying in text/html modules)?
Sorry I didn't knock out all my questions in one posting.
Lee Sykes
DNN Creative Staff
Nuke Master VI
Nuke Master VI
Posts:4945


--
08/11/2008 3:39 AM  
 I have looked into this a bit more for you, when your live site uses relative URLs, and you restore it to a localhost installation you get the following URLs on the images:

In the FCK editor:
/Portals/0/pics/issues/34/issue34_180.jpg

Will become:
http://localhost/Portals/0/pics/issues/34/issue34_180.jpg

But, the actual URL you need is:

http://localhost/dnncreative/Portals/0/pics/issues/34/issue34_180.jpg

The workaround I have found is to copy the files from your Portals folder into your localhost folder, ie:

C:\Inetpub\wwwroot\Portals\0\

I would be interested to hear how Joe has set this up.

When I'm testing, I actually leave the images as not displaying because this reminds me I am working on a localhost installation. - if I click on a link on a localhost installation and it opens the live webpage and I then accidentally start editing the live webpage this could cause problems - so I'll leave my localhost installation images not displaying so if I do click on a live website link I see the images are displaying and are reminded that this is the live site.

Of course, you want to display the images, so I think this workaround will help.


Lee Sykes
Site Administrator
Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

Twitter: www.twitter.com/DNNCreative

Lee Sykes's Facebook Profile


---