CSS and JS file Include

I have to include CSS and JS files in sitepublisher sites and as expected, the path of CSS and files is relative to the current branch. But in our setup, each branch in Teamsite doesnt correspond to a webroot folder on the webserver (due to some reasons..).
So, is there a possibility to manupulate the path of CSS and JS files so that it even works on the webserver without any issues?

Thanks in advance.

TS 7.2.1

Find more posts tagged with

Comments

siddin

I have to include CSS and JS files in sitepublisher sites and as expected, the path of CSS and files is relative to the current branch. But in our setup, each branch in Teamsite doesnt correspond to a webroot folder on the webserver (due to some reasons..).
So, is there a possibility to manupulate the path of CSS and JS files so that it even works on the webserver without any issues?

Thanks in advance.

TS 7.2.1

Look at page token $URL_PREFIX in site publisher guide

interDev

Look at page token $URL_PREFIX in site publisher guide

We dont use Livesite Runtime envrionment and are generting static HTMLs from sitepublisher. So URL_PREFIX will not create the complete relative path of CSS and JS files and it will not work on webservers. Any other thoughts?

Crsb

I don't know of any official way, but you can edit the default.site with a text editor to manipulate the resources, not sure if it has any drawbacks thou.

Rick Poulin

We dont use Livesite Runtime envrionment and are generting static HTMLs from sitepublisher. So URL_PREFIX will not create the complete relative path of CSS and JS files and it will not work on webservers. Any other thoughts?

The $URL_PREFIX should be resolved to a static token for you at generation time. It's still the appropriate way to refer to your site root, which is expected to map to the root of your workarea. If that's not the case, then perhaps you could use paths that would work on the generated pages, and use iwproxy rules to make them work as expected within TeamSite.

Crsb

I might be wrong but I think this thread is more about adding references to assets that don't live in the workarea (you can't browse to them in TS), which means you can't add them to default.site since it only lets you select files that you can browse to.... for example the only way i can think of to reference http://www.google.com/....api.js is to edit the .site with a text editor and add it as resource node.

Rick Poulin

I didn't read the original post that way, but granted, the .site hack is probably the only half-decent way of including external resources. The only supported way I can think of doing that is to write a PreController to add that stuff in the PAGE_HEAD token, but that seems an awfully heavy solution.