I don't want a custom template!!

Next topic

Author	Message
RW Wood	Tuesday 16 September 2003 11:02:12 am Sorry to post this again, but the only way to get rid of this error message is to put the template that ezP wants to create in the template folder for that design. That implies that the program is demanding a custom template for every site design, but I WANT the template that I've set as standard for the overall site. "Default object view. Click to create a custom template" followed by the content folder's name, description and buttons saying "preview", "remove", "add to bookmarks", and "notify me about updates" I've tried to figure if something is not right in the site.ini.append but have gotten nowhere.
Bjørn Kaarstein	Wednesday 17 September 2003 2:07:19 am A dirty solution would be to take a backup of the standard folder, and simply exchange the templates in the original standard folder... Regards Bjørn
RW Wood	Wednesday 17 September 2003 6:54:28 am Are you saying that there's a flaw in the fallback system? The whole point of the overrides, I thought, was to only change what was specific to one of many site designs. If this is the best "solution", why not throw out the fallback system altogether? I don't get it. RWW
Karsten Jennissen	Wednesday 17 September 2003 7:03:58 am Hi, you do not need to use the dirty solution. I read your other thread and it seems that the system does not recognize your design settings the right way. Are you sure you are using the right ini files? In which file did you specify the design settings? Look through all site.inis including the one in /settings/override and check where you find any design settings. Check here to see which config file does what and which file overrides which: http://ez.no/developer/ez_publish_3/documentation/installation_and_configuration/configuration/configuration_files Regards, Karsten
RW Wood	Wednesday 17 September 2003 7:44:26 am Here's what the doc says: The configuration files are read in this order: /settings/site.ini /settings/siteaccess/[directory]/site.ini.append /settings/override/site.ini.append.php This means that settings in [3] override [2] which override [1]. If you want to change configuration settings for different siteaccess setups then create new directories under /settings/siteaccess and change them there (also remember to put those new siteaccess rules in /settings/override/site.ini.append.php). I'm not sure to what the () part is referring, however, here's what I have: /settings/site.ini (not changed from default, but I removed comments) [DesignSettings] StandardDesign=standard SiteDesign=admin AdditionalSiteDesignList[]= /settings/siteaccess/ggila/site.ini.append (my "standard" design) [DesignSettings] StandardDesign=ggila SiteDesign=ggila /settings/siteaccess/argentina/site.ini.append (a typical "sub-design) [DesignSettings] StandardDesign=ggila SiteDesign=argentina /settings/override/site.ini.append [DesignSettings] StandardDesign=ggila As near as I can tell, unless I'm missing something that has to be changed other than the [DesignSettings] section of the files, that should produce the desired result, ie. fallback to use of templates within the ggila design folder if there's not one in the argentina folder. Since the ggila folder is a straight copy of the original standard folder, everything is there and there are no missing templates. As a matter of fact, if I click on the "create a custom template" link, the template that's used as the default is the one from the ggila design. Thanks for your help, but I must be missing something really obvious. RWW
RW Wood	Wednesday 17 September 2003 5:39:29 pm I finally figured out what, I guess wasn't obvious to anyone else either. "Default object view. Click to create a custom template" and all that follows is coded into the standard design full.tpl and that template has to be replaced to get rid of the "error". I was interpreting the problem as ezP telling me I needed "another" template, not to replace the existing. To be honest, I'm not sure why the developers did that for only the full.tpl when it's common knowledge that "stuff" has to be changed if one wants a different appearance. To me, it was really confusing because I understood the override system and checked everythig repeatedly looking for why a template other than the one in my "standard" design was being used, only to find out that it was and was the source of the problem. I would suggest that perhaps future releases either do away with the forced creation of the "custom" full.tpl, or at least put a clarifying message on that page such as: "Default object view. Click to create a custom template. This output is produced by the full.tpl in your /standard/templates folder. It must be replaced and a copy put in /standard/templates/node/view folders. You must either use this interface to produce those templates or develop them outside of ezPublish and place them in the indicated folders." Just a suggestion. Now on to the multilingual and specific content appearing only with specific site design problems. Thanks. RWW