Multiple destinations and cross-site linking

Garth's Avatar

Garth

27 Mar, 2015 09:19 PM

Hello,

I can't tell whether I'm just not applying the right configuration, or if I've approached this in the wrong way, or maybe it can't be done at all.

We have two sites (Site A, B) that reference each other as well as a "Static" site which contains common stylesheets and images used by both Site A and B.

All three of these sites have two Destinations each: Testing and Production.

Each Destination reflects a different base URL for the site. For example:

Site A has: test.site-a.com, www.site-a.com
Site B has: test.site-b.com, www.site-b.com
Static has: test.static.com, www.static.com

When I publish Site A to its Test Destination, cross-site links from A to B should be resolved (somehow) to the corresponding Test Destination used by Site B. The same is true with cross-site links from Site A to stylesheets managed by the Static site.

I've noticed that cross site links from Site AorB to the Static Site reflect the "Site URL" property for the Static Site rather than magically knowing which base URL to use given the available (and selected) Destinations between the two sites.

This means that when I publish test.site-a.com, it will create references to www.static.com instead of test.static.com.

The only way for me to have test.site-a.com properly rewrite URLs to test.static.com is to change the Static Site's Site URL property to match the Test Destination's base URL. And then, when I want to publish the site(s) into production, I have to change the Site URL property to reflect the Production Destination base URL.

Is that correct? If I'm not doing anything wrong, it sure would be handy to be able to create a "Destination Set" between multiple Sites. This would help facilitate being able to easily publish staging/dev/test versions of multiple interrelated sites.

Thanks for any insight anyone may have!

  1. 1 Posted by Penny on 06 Apr, 2015 03:06 PM

    Penny's Avatar

    Hi Garth,

    I believe the described behavior is correct and expected. I would definitely recommend filing your suggestion on our Idea Exchange. The only work around that I have seen for the described behavior is to just enter the sub-folders in the Site URL rather than the fully qualified URL. This will only work if you are publishing within the same domains for each of your servers: dev, test, and prod. So rather than saying http://mydomain.edu/admissions, you would just put /admissions in the Site URL.

    I hope this information helps!

  2. Ryan Griffith closed this discussion on 20 Apr, 2015 02:27 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac