Here's a scenario:
I create a new template. In it, I am displaying some additional fields within /templates/mytemplate/html/com_content/form/edit.php so my administrators who log in to the front end of the site can control additional parameters for articles ("created" and "created_by", for example). Simply adding them to the override file displays them, but because /components/com_content/models/forms/article.xml has filter="unset" for each of these and lacks proper label, description and other attributes, the adaptability seems to stop there.
In a 1.5 template, because this security procedure wasn't in place, it was easy to simply add in missing fields and the logic to support them. But 1.6 seems to present a new challenge.
Given that example...
- Can you specify an override XML file for forms so the core doesn't have to be hacked? Or does this defeat the purpose?
- Where would this need to be placed within the template package if it is an option?
- What would be a good alternative if this isn't an option?