Home → General →

cross-site linking outputting incorrect URL

• Edit

Rory Reiff

09 Nov, 2011 04:28 PM

I have an XHTML block with the following code:

<link type="text/css" rel="stylesheet" href="/assets/css/jquery.fancybox-1.3.4.css" />

and I am including that block into a template on another site. However, the output in the html looks like:

<link href="//assets/css/jquery.fancybox-1.3.4.css" rel="stylesheet" type="text/css" />

I have tried wrapping my link in [system-asset] as well as [system-asset]site://SITENAME/ but nothing gets both Cascade to recognize the file in my site, as well as the output correct. What am I doing wrong? Thanks.

1. 1 Posted by Rory Reiff on 09 Nov, 2011 04:37 PM

   

   I just discovered the same thing is happening within a stylesheet I have on Site B, that is referencing an image located in Site A (the image is actually rendering in cascade, but the URL gets output with an additional preceeding slash once published).

   div.video div.controls {
       background: url('[system-asset]site://_chapman_common/assets/images/site/play_small.png[/system-asset]') 0 0; 
       }
   

   • Edit

2. 2 Posted by Lee Roberson (F... on 09 Nov, 2011 04:42 PM

   

   Just an idea -- do both of these sites have a proper Site URL set in the Site Management screen? Especially the one that actually houses the assets?

   • Edit

3. 3 Posted by Rory Reiff on 09 Nov, 2011 04:45 PM

   

   The URL I have set for both is '/' - should that be something else? I was setting up each site with that URL, then structuring the folders in each site to match up as if I was publishing everything from the root down (i.e. if I have a site for /dayone, the URL I set is '/' then in that site I have a 'dayone' folder that contains all my folders and pages.

   • Edit

4. 4 Posted by Lee Roberson (F... on 09 Nov, 2011 04:49 PM

   

   Ah, try just putting your domain in there then.

   Also, it's not enforced by the user interface, but you need to make sure for various reasons that the URL entered in that field doesn't end with slash because that can cause some issues (in your case, it just put an extra slash at the beginning of the rewritten path).

   Plug your primary domain into there, e.g. http://www.school.edu and then the rewriter will write the link as http://www.school.edu/assets/css/jquery...

   In cases where you have multiple staging servers you can get the correct paths to output by setting a URL on the each Destination, too (this is available in a recent release of Cascade Server). This helps your pages that go to your test destination only publish with the paths to the dest destination CSS and Javascript, etc.

   • Edit

5. 5 Posted by Rory Reiff on 09 Nov, 2011 04:52 PM

   

   Ah - okay. That would make sense. Thanks so much Lee!

   • Edit

6. 6 Posted by Rory Reiff on 09 Nov, 2011 04:57 PM

   

   One quick thing - would that be entered into the 'Web URL' field of each Destination? Because I did enter 'http://cuv-corws01.chapman.edu' into my destination in that field, and it still published the page with http://chapman.edu for the URLs

   • Edit

7. 7 Posted by Lee Roberson (F... on 09 Nov, 2011 05:12 PM

   

   You might have to ask support about that -- cross-site linking to assets might only use the Site URL field and not the Destination URLs.

   • Edit

8. 8 Posted by Ryan Griffith on 14 Jun, 2012 08:47 PM

   

   Apologies for the late response.

   You are correct Lee, cross-site linking uses the Site URL field.

   Cascade 6.10 introduced the Web URL field for Destinations which allows you to perform link rewriting using Destination URLs. When specified, this field overrides the Site's URL (see previous link for more information).

   If you have additional questions please let us know.

   • Edit

9. Ryan Griffith closed this discussion on 14 Jun, 2012 08:47 PM.