|
Tuesday 06 April 2010 3:33:02 am
What's the purpose of this new setting? Is there any documentation beyond the article for 4.3's backward compatibility? It is enabled by default, and seems to cause some really weird behavior... Szenario: A new v4.3 installation with Plain site package using hostname siteaccess for backend and frontend. plain_site_user is the frontend siteaccess, using plain_site and base as SiteDesign respectivly AdditionalSiteDesignList. plain_site_admin is the backend siteaccess using admin2 and admin as SiteDesign respectivly AdditionalSiteDesignList. Some extensions with design extensions enabled (e.g. ezGmapLocationDatatype). Issues: Every time after clearing the entire cache (using the sidebar), the backend uses plain_site_user's pagelayout.tpl. After clearing the cache a 2nd time (via setup tab, the sidebar has vanished), without doing any changes, backend uses the correct pagelayout again. In the backend's template view ( e.g. /visual/templateview/node/view/full.tpl ) the standard-template-resource is shown as "design/admin2/templates" for both, plain_site_user and plain_site_admin. Why...? On the same page in the override listing for plain_site_user all overrides are listed, but according to the listing, no file matches the override. However, when viewing the frontend in the browser, the frontend override templates are correctly used. Solution: Manually disabling DesignLocationCache in site.ini resolves all issues.
|
