Hi,
I am having an issue on a site that I am developing. I have setup the site with a temp url and in the portal alias put both the correct live url and the temp url. I have added links to a text module which when friendly urls are selected hold the main url and don’t use the temp url. This means that when my client views the site, when they select that link it goes to their original site. If i turn off friendly urls it fixes the problem. I want to use friendly urls and also I have done a lot of work so far and don’t want to have to go back through each of the links I have created so far and change them all. I am sure this is either me doing something wrong or a bug in dnn 514. Any one go any suggestions on how I can use friendly urls in a development site and them change once the site goes live.

Thanks

Roger

Hi Joe,
I agree, I need to use relative links. The problem is that dnn is generating absolute ones.
Example:
I have a text/html module with the text "read more..." I create a link using the create link > browse > page > select page to link to > ok.

the html generated with friendly urls turned on is different to that when these are turned off.

Code when on:

http://stmon.digitaltradingco.co.uk...sTest.aspx">test link 2

code when friendly urls is off:

read more

This is my problem. I hope this makes more sense!#

Thanks

This is the code generated when I do the same.

http://stmon.digitaltradingco.co.uk...sTest.aspx">test link 2

I can't see it realy being related to the 514. I'm on 5.2 and experience te same problems.

We build our DNN portals on a local testing server using domains like http://test.domain.com to have our customers pre create their sites content.

After that I made a database backup and restored that with our live server and copied over the complete DNN installation, something we could nicely do as it were the first portals.

On the production server the test domains be came normal http://www.domain.com domains and the old aliasses were dropped. I then discovered that all links within the HTML modules still use the old test domains.

I don't really understand this behavior as it apparently does not allow me to let a customer build there new site on domain x and then switch it over to domain y.

Maybe I'm doing something wrong but both our testing server as well as our production server don't create relative links using the editor.

Makes sense... Here are a couple of screens illustrating the issue.

As you can see the initial link is set to http://test.carmenautomotive.nl while the new link is set towards http://www.carmenautomotive.nl. Of course one could change these links, but that would be by hand and you can't expect end users to do that.

Another problem with this is that when your portal has multiple aliasses, like carmenautomotive and carmen-automoive in this case, the links are still set to the domain on which they are created. So a user entering your site through carmen-automotive will switch to carmenautomotive whenever he or she clicks a link. Not a problem unil it's set to a blank target and popup filters kick in.

Hopefully I am mistaking and need to change a setting for my DNN installations, as I see this behavior as a big issue.

Thanks for the help again! Hope to hear from you guys.

Running on the community edition here by the way.

Regards,
Maurits

Heey Joseph,

Now I'm confused... Your answer implies that I should use the "Page on my site" or "File on my site" option right? But as you can see in my screens this is what I already do.

To clearify, The first screen is the link as is is when I open the existing HTML module and click the editors link icon. The second is when I then click the "browse server" button. There I chose the "Page on my site" option and select the appropriate page. The third screen is the result of this.

You refer to specifying pages without the leading domain, which i understand, but is doing so by hand the only way? That would unfortunately make the system very unfriedly to normal content editors.

That's not a problem, but I see why it confused me now as the description you give does not seem te apply here.

I have tested this and found that links do get hardcoded within our portals. This is why I got confused by your answer.

Apparently there is some bug here or do I need to adjust some settings in order for this to work?

This is what I got after creating the links according to your explaination.

I've added a screen of the host for reference as well.

I understand and it is getting clear to me that DNN lacks a little here, as I expected it to create relative links fully automatically. But as I read the posts it apparently does not.

Thank you very much for your input Joseph! I'll take this up with the content editors and make sure they have the proper instructions.

Now we're talking! The solution, or work around, you gave indeed creates the links relative as I illustrated with te screens below.
If you'd ask me this behavior should be standard for each link created with the 'Page on my site' option, but at least this way it will become a bit easier for the content editors instead of having to change the URL's themselves.

Thank you for the message Joseph.