In addition to being able to alter many of the basic settings on a site via portal_actions
, users can also modify certain page templates, images, stylesheets, JavaScripts, and so on through the ZMI. How Plone interprets these changes depends on the order of what are called "skin layers".
Prior to Plone 3, most customizations performed in the ZMI relied on the concept of a single, global namespace such that resources for a given product could not easily be shared between products. The global namespace was also a problem because it resulted in name conflicts in products. Authors were forced to use convoluted names in their products, such as pfg_base_edit
, which was very "un-Pythonic". This was a fairly limiting idea but made modifying items fast and easy through the web.
Before Plone 3, Plone used Zope's concept of acquisition (and still does, but not always). This means that when looking up an identifier, Plone finds the closest object, property...