Itamar Tzadok

I'm not sure about the templates for I've just started working with 1.9, but if the new view you need is an alternative list view you can try incorporating it into the list template with a button which allows the user to switch between that view and the standard list.

... or simply include a js file that writes the code into the document. This way there's nothing for the htmlarea to muck up and the code may be easily modified by editing the js file and without turning the editor on and off.

When you copy the code into the HTML editor in a label or block you need to change first to text mode by blicking on in the tool bar. Here is how it should look like:

If these groups are fixed throughout the course then 'visible groups' mode can do the trick. But even if they change from topic to topic you can still handle that by manipulating groups which might be easier than duplicating forums.

Unfortunately if you edit the template a filter in Moodle will validate the code and muck it up but if you keep the code in a external document you can just paste it back in and all will be well.

Does anyone know how or where to turn this off.

One way to avoid this unfortunate but sometimes necessary behavior is to write the table with javascript. In the header you define a string variable to which you then add the relevant table parts from each section of the template and finally document.write it in the template footer. Something like:

Header script:

var strHtml="";
strHtml+='..'; // open table and header row

Body script:

strHtml+='..'; // data row; the template generator do the loop on this script command and you get all rows.

Footer script:

strHtml+='..'; // close table
document.write(strHtml);