CDN vs non-CDN issues

When importing template via Actions > Add template…

I had CDN set as <script src="//"></script> and <script src="//"></script>

(but the rest of JS files that is non-CDN I don’t mind…)

Instead, Percussion automatically imported anything CDN-related <script src="/web_resources/themes/FoundationTest/import/"></script>

<script type="text/javascript" src="/Rhythmyx/web_resources/cm/jslib/jquery.js"></script>

even overriding the latest jQuery I included, they’re using few versions behind.

This is the issue b/c some plugins required the latest jQuery…

Hi Aaron,

The import process while crawling each link it finds, will automatically create the file based on the link path referencing the file and recreate the folder structure. As for the jQuery references, Percussion ships with and relies on both jQuery and jQuery UI and references those files automatically. For stability and supportablilty, we recommend not referencing any other jQuery or jQuery UI libraries to avoid unexpected behavior with the user interface.

We do periodically update our libraries of both jQuery and jQuery with new releases of the product. Out of curiousity, which plugins were you planning on using?


I think his issue relates to the fact both src attributes do not have an "http:"or “https:” in front of the “//”. Percussion must be reading the “//” and thinking it’s a local resource, not an external one. To me this is a bug as it’s perfectly valid to leave these off.

excerpt below via…

" All the browser does is infer the protocol from the current location.

UPDATE: The primary reason for this is so that all elements on an HTTP page remain HTTP thus avoiding the overhead of HTTPS calls. Similarly, we want all elements on an HTTPS page to be secure in order to avoid that nasty security dialog that could pop up to inform people that the page is only “somewhat” secure."

Percussion should probably fix this so it does not attempt to translate such links…

I agreed what Paul said. Thank you for the explanation!

We actually did this intentionally. The rationale for this decision was that we couldn’t be certain whether people knew what resources were needed as part of their website. In the case of pointing to modernizer, it makes sense, but what if they were pointing to a location that they were planning on taking down as a result of moving to Percussion? Since we couldn’t be certain, and because we didn’t want people’s sites to break as a result of the import, we decided to be safe and copy everything.  After import, you can choose to change those references to go back to being external calls.  


It sounds like CM1 is only testing for a leading “/” and then immediately converting it to a local path. it should instead first test to see if there’s a double slash “//” and if so, leave it alone…

And if it’s a local resource, say on a shared location/network, that someone is trying to use, well the slashes for referencing it go the other direction “”…

Good point Paul about / vs //