Bug in template editor: overrides will always be for user siteacccess, no matter what I select

Wednesday 11 June 2003 11:04:01 am

This time the thing actually loads and does something. I stumbled across one rather stupid bug though: when defining overrides, it will always define them for the user siteaccess, no matter what siteaccess I selected it for (I even removed user from the possible siteaccesses so I guess this is somehow hardcoded in there). I'm quite convinced that it will work once this is fixed.

Visit http://triligon.org

Thursday 12 June 2003 3:16:23 am

Works if I hit set (didn't occur to me to hit that one before ;-). But it would definitely help if it worked without the hitting set, I agree.

Thanks a lot, its much more useable now.

Maybe also add a note that hitting set (or another name if that fits better) will show the overrides. Maybe call the buttong "show siteacces overrides" or something along that line.

I think it would also help if the class editor were to show what overrides there are defined for a particular class but that's just convenience feature more than anything else.

Visit http://triligon.org

Thursday 12 June 2003 4:54:42 am

There's another bug.

If override.ini.append.php exists, it will be parsed but the new file created will be override.ini.append (containing override.ini.append.php and the new class). Now the new template won't show up because only override.ini.append.php will be parsed the next time. Same goes for showing templates.

Visit http://triligon.org