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 ...?
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?
--
chirsch{AT}gmail{d.t}com
You must be logged in to post messages in this topic!
