Forum OpenACS Development: acs-templating enhancements

Collapse
Posted by Malte Sussdorff on
Just for the record. ACS templating allows you to store your list and form templates in a custom package now, it does not have to reside in /acs-templating/resources/lists anymore. This is in HEAD and should solve Dave's problem with the ajax listtemplate (just put it in ajax-helper).
Collapse
Posted by Malte Sussdorff on
with template::head and the new site-master make sure your lrn-master from theme-zen points to /www/site-compat and not to blank-master.

In the long run the code in site-master which determines if we are in .LRN should go directly to lrn-master.

Collapse
Posted by Emmanuelle Raffenne on
Hi Malte,

I'm a bit confused.
lrn-master points to blank-compat since it (lrn-master) includes part of the site-master code and I don't see any changes regarding this in the repository.

Am I missing something?

Collapse
Posted by Malte Sussdorff on
Hi Emanuelle, then try to run it with developer support bar using theme-zen and acs-templating / www from HEAD. This fails because the developer support bar is initialized using template::header (or something like it) in site-master. As is the .LRN toolbar by the way.

When you now run developer support, the toolbar is not initialized => the CSS is not loaded. But the special developer support div tags for the showing and hiding of the ADP files are still there, because this is something inherent to the ADP code.

This all leads to a page which is not viewable. If you change this in HEAD, then we should be fine, but for the time being it looks like (from experience) that the latest commit to HEAD puts the initialization of developer support and .LRN support into site-master. And until this is reflected in lrn-master you need to change it to site-compat instead of blank-compat. Hope this clarifies the situation.

Collapse
Posted by Don Baccus on
You're right that this needs to be fixed, and will be for 2.4 as we complete migration to the new scheme.