Hi Joe,

The thing to understand is that relative urls are always relative to the root of the web site, so even though we use relative urls there is a difference between /home.aspx and /mojo/home.aspx even though they are both relative urls.

So if you create the content with site running as a virtual directory in the mojo folder for example, the friendly urls have /mojo/pagename.aspx for the friendly part and /mojo/Default.aspx?pageid=x for the real url. So the cleanup would invlove removing the extra segments from the urls if the site were moved to a root level.

The FCKeditor image browser also uses relative urls as does the link browser which allows browsing and linking to pages within a site, so there may be urls in the content that need fixing as well. Of course the normal link dialog ues fully qualified urls as it can link to external pages, but if you use it to link to local pages those urls may also need fixing. 

So, its much better to populate the site using the same url structure that it will have in production use to avoid the need for cleaup as much as possible.

Hope it helps,

Joe

Unless there's just a huge amount of pages I would just edit directly in the table rather than take a chance on a query. You will need to edit mp_FriendlyUrls, mp_Pages, mp_BlogPosts to correct the urls.

Hope it helps,

Joe

Hi,

You raise an interesting scenario. I admit I have never tried the installation on a machine where ssl was required for every request right from the start and using an alternate port for ssl. I will make a note to come up with an easier way to handle this situation.

In the mean time here are steps that  I think should solve the problem.

1. Put this in your user.config file:

<add key="SSLIsAvailable" value="true" />
<add key="AlternateSSLPort" value="444" /> 

2. Here is the ugly part, go into the database manually and in the mp_Sites table there should be an existing row, set the bit field UseSSLOnAllPages to 1 or true.

3. Touch the Web.config file to make it reload settings. ie type a space in it and save it.

4. Visit your site at https://yourrooturl:444/Default.aspx

Hope it helps,

Joe