If you like the design, take a few minutes and read the documentation (I know, you already said you're unhappy with it).
The CSS files are stored in var because you can create sitestyle packages that allow you to override the site design, using site-colors.css, classes-colors.css, and any images you'd like. The other wonderful advantage of the ezwebin is the site editing, so users can edit without using the admin console.
You can change the templates in the extension directory (try <b>overrides/templates</b> first, then use <b>templates</b> if necessary).
If ezwebin is really frustrating you, you could install eZ 3.8+, then do an upgrade. This will prevent the setup wizard from installing ezwebin and you can take advantage of the new features.
Yet, the templates are not being used. When I debug to show "templates used" then I see many of these templates are being drawn from the extension.
Such as extension/ezwebin/design/ezwebin/templates/pagelayout.tpl
Which I full expected to be design/myfancystuff/templates/pagelayout.tpl
All I'm trying to do is modify the "homepage" after a default installation! It's very frustrating when I think I've set the design only to find it's using files in an extension instead. And I don't find any documentation about why this happens, so if it exists I would ask you to be precise in telling me where to look.
Same situation for me, this new behaviour seems a bit strange at first sight. Have you succeeded in having your own templates used in priority of the new web interface ?
I've found an ugly solution consiting of copying the design of the ezwebin extension folder to the traditional design folder :
cd /var/www/ez/extension/ezwebin/design cp -a ezwebin /var/www/ez/design/ezwebincopy
Finlayy, I have this in site.ini.append.php :
[DesignSettings]
SiteDesign=mydesign
AdditionalSiteDesignList[]=ezwebincopy AdditionalSiteDesignList[]=base
This way, when creating a copy of pagelayout.tpl in "mydesign/templates", my adaptations are taken into account.
move mydesign into a extension of it's own, but if that works for you. Can you please write a bug repport on you original issue, if true this is a bug.
