[Zope-CMF] Problem when updating CMF 1.1 to CMF 1.2

Dieter Maurer dieter@handshake.de
Sun, 21 Apr 2002 20:58:07 +0200

josef_meile writes:
 > ... File Directory views empty after upgrade ...
 > Everything was going good! except by the default folders in the
 > "portal_skin" tool, the ones that have a lock, such as Images, 
 > content, control, generic, and so on.
They remember the path to the directories in the file system.
When you access them, they compare their paths against the
set registered during start up.

I observed some magic changes of paths registered:

   in some constellation, it used "Products/CMFDefault/skins/..."
   while in another one, it was "lib/python/Products/CMFDefault/skins/..."

Maybe, its something similar for you.

   If it is, updating the "path" in the "Properties" tab of the
   skins to the correct value will fix the problem.

 > So, I just move my custom skins to another place and delete 
 > the "portal_skins" tab and create it again. At this time the
 > default skins weren't displayed. Does anybody know how to
 > retreive them?
You add a "File Directory View" for each of them to "portal_skins".

 > Why just don't the developers include them when 
 > creating the portal_skin tool?
Because they do not know which one to create, where to find them, etc.

  Note that CMF is a framework and CMFDefault is just an example
  usage. Adding a "CMFCore: Skin Tool" is part of the framework
  and does not know anything about CMFDefault.

  The Skins tool is initialized correctly, when you add
  a new CMFDefault Site instance. You may copy its "portal_skins"
  to your portal, when you want a CMFDefault "portal_skins" tool