Book Image

Plone 3.3 Site Administration

Book Image

Plone 3.3 Site Administration

Overview of this book

In the past few years, we have seen some dramatic changes in the way Plone sites are being developed, deployed, and maintained. As a result, developing and deploying sites, changing their default settings, and performing day to day maintenance tasks can be a challenge. This book covers site administration tasks, from setting up a development instance, to optimizing a deployed production site, and more. It demonstrates how-to perform these tasks in a comprehensive way, and walks the user through the necessary steps to achieve results.We have divided the subject of Plone site administration into three categories: development, deployment, and maintenance. We begin by explaining how a Plone site is built, and how to start using it through the web. Next, we add features by installing add-on products, focusing on themes, blogging, and other common enhancements. After the basics of developing and deploying a Plone site are covered, the book covers the basics of maintaining it.Further, throughout the book we preview some new technologies related to Plone site administration, available now as add-ons to the current Plone release. Finally, we will cover a variety of techniques to help you optimize your site's performance.
Table of Contents (15 chapters)
Plone 3.3 Site Administration
Credits
Foreword
About the Author
About the Reviewer
Preface
Index

Examining themes in the Zope Management Interface


Now that we have seen in part how themes work, let us take a closer look at their representation in Zope Object Database (ZODB).

Browse to http://localhost:8080/Plone. Click on Site Setup | Zope Management Interface and you should see:

This is a Through the Web (TTW) representation of all the objects in the database at the Plone site level (the application root is one level above).

The most frequently used theme-related objects here are:

  • portal_css

  • portal_javascripts

  • portal_skins

  • portal_view_customizations

Of these, portal_css and portal_javascripts are most often used to enable their respective debug modes, wherein the CSS and JavaScript files are not compiled into a single file (not to be confused with Zope 2's debug mode which detects filesystem changes in real time when enabled).

Take a look at your site with Firebug, in particular the style tab.

You should see:

Now enable debug mode in portal_javascripts and look again. You should...