The URL of images for portals includes the PortalID in the URL?

Directly referencing in the browser address bar bypasses the server side generation of URLS and requires adding the PoartsDIR/PortalsID to the url in order to locate the resource.

How can a Portal be referenced from internet browers directly as well as from inside of skins when referencing absolute resources as only the root + resource (image, html, aspx etc....) location without requiring the need to have the Portal ID placed the url ?

example   http://mydomain.com  and not  http://mydomain.com/portaldir/portalID

How we we eliminate the Server side generation of URLS that include PoartalDIR/PortalID ?

Example1...

Create a portal subdirectory under the root called support and copy the image to that directory

   http://mydomain.com/support/image.png

Example2....

Create a page in the root of the portal ....

http://mydomain.com/support/Product-I...

Example3.... Absolutely reference an image or resource from the Skin....

>a src="http://mydomain.com/support/Product-I..."< This is a absolute Link >/a<

When making a standard website using IIS... this is never a problem.... But I can not see how to have a website portal behave as a root website ????

Any help is appreciated...

Thanks,  Bill

Hi Sebastion,

Can the URL Friendly settings accomplish this or Infinity... where links that have PortalDIR/Portal/ID in the url are then made friendly... effectively accomplishing the same need ?

Thanks,  Bill

Of course that makes sense that there is a static dependency in the code if there is no solution to this...

I dont think that support@dotnetnuke.com  is the appropriate place to make suggestions to improvements, maybe you can direct me to the appropriate place to suggest product improvmenrts.

It would be to the advantage the DNN abstracted the technical structure of links and resources from the graphic designers, html editors and UI system so that all portals appeared to be starting at the root and containing only structures that are directly underneath its hierarchy in the filestructure and make available virtually mapped references to resources outside of those hierarchies!

But hey,  I am sure they have thought about it already RIGHT ?

/Bill