Forums / Setup & design / Icon for folder objects?
Jan Bengia
Wednesday 08 June 2005 12:41:07 pm
Hi, how do I assign icons to classes/objects in the admin->content view?I copied the folder-class and modified it. Now it's assigned to some general "sheet"-icon. I want it to be assigned to the folder-icon. Is there an easy way to do this?
BTW: Where are the class-overrides located (path)? I haven't found this information in the documentation ...?
thanks a lotJan
Craig Hirsch
Wednesday 08 June 2005 1:49:07 pm
Yes, this is very easy.
FYI, icons in the default admin theme are stored in:
/share/icons/crystal-admin
and icon settings are in the icon.ini settings file.
To set up your new content class to appear with the folder icon, override icon.ini for your admin siteaccess as follows:
[ClassIcons] ClassMap[YOUR_NEW_CLASS_IDENTIFIER]=filesystems/folder.png
Clear your caches and that should do it.
-- chirsch{AT}gmail{d.t}com
Wednesday 08 June 2005 1:50:52 pm
To address your second question -- what do you mean by "class overrides?" Can you explain further what you're looking for and/or looking to do?
Wednesday 08 June 2005 3:29:37 pm
Hi, thanks for your help! I'll try that icon-stuff.
Regarding my second question: Uhm, what I mean is: I work in an multisite-environment. When I create new templates, I place them in the specific folder for the siteaccess (htdocs/design/[site]/templates/).But when I create new Classes (like "member" with "name"-attribute and so on) via the admin frontend: In wich folder (of the file-system) are they placed? And how does the Admin-FE know which classes belong to which siteacceses?
And with "overrides" I mean: When I modify existing classes, the changes are only aviable in the specific siteaccess. So somewhere exists the original class and somewhere the "overwrite" class ...?
Hmm, I hope I got my point across :) greetsJan
Wednesday 08 June 2005 8:52:44 pm
Yep, I understand what you're asking now. Content classes, including new ones that you create, aren't stored in the filesystem at all. They're entirely database-derived constructs. Each class, and each attribute of each class, is stored in the database.
Quite honestly, I'm not certain that new classes are specific to a particular siteaccess. I've personally never worked in an environment with a lot of sites served from one eZ instance. Can anybody else comment as to how this works?