Difference between revisions of "Developing a MVC Component/Adding verifications"
From Joomla! Documentation
m (moved Talk:Developing a Model-View-Controller (MVC) Component for Joomla!1.7 - Part 11 to Talk:Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Part 11)
m (moved Talk:Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Part 11 to Talk:Developing a Model-View-Controller Component/2.5/Adding verifications: Improve structure with subpages and version disambiguation.)
Revision as of 13:35, 6 August 2012
Why is the protected function _populateState() in the /admin/models/helloworld.php file? It doesn't appear in the original helloworld.php model file, and there isn't any indication as to the purpose of this function aside from the annotations within the function, which I don't fully understand.
Section about admin/views/helloworld/tmpl/edit.php is not the same as in file present in archive.
verification seems to operate even when required="false" is coded
I have expanded the helloworld component to have several other fields now, and set some of them to required="false" in the /models/forms/app.xml file. I still get "invalid field" when I leave the input box empty. Any ideas?
(later) I think I figured it out: the client-side script operates on every field it's assigned to, whereas the server-side may operate only on a field that's required and not empty. Not sure about that last, but I am sure that the client-side script operates, so you may want to code the regex differently in admin/models/forms/<com-name>.js (the client side) vs admin/models/rules/<field>.php .
"In theory, there's no difference between theory and practice; in practice, there is" --Yogi Berra 10:51, 30 September 2011 (CDT)