Synchronizing Skin Layers and CSS/Javascript Resources

by George Lee — last modified Dec 30, 2008 03:05 PM

How to ensure that the proper CSS/Javascript resources are used in different skins.

Switching skins changes what skin layers in portal_skins are used, but it does not switch what CSS and javscript resources to load. This could be disastrous if you have CSS that applies only to the page templates in one skin, but not to the page templates in another skin.

The solution is simple: in the portal_css or portal_javascripts tools, just add a condition on certain resources similar to

python:portal.getCurrentSkinName() == 'My Public View'

Previous: Use Case Two: Skin By Type of User Next: Additional Documentation on Switching Skins Right arrow

About

You are reading:

from Switching Skins.

This Tutorial describes how Plone chooses a skin when you open a web page, and then describes the multiple ways that you can intervene to switch the skin. The Tutorial also discusses two common use cases, switching skins based on URL and the type of user (e.g., Anonymous or Authenticated).

All content on a single page

Use with: Plone 2.5.x, Plone 2.1.x
Relevant for: Integrators, Customizers

This document was contributed by George Lee, and last modified 445 days ago.

Visit our chat rooms or support forums if you have more specific questions.

You can also learn how to design, build, and deploy a website in Plone through one of the numerous Plone training sessions around the world.