Wednesday 19 August 2009 3:40:42 am
Hello Hakim, I have provided similar features per unique customer requests in the past. Most of the time depending on what your trying to do this gets complicated. Most will tell you it's not possible. That is not always the case. Often I have had great success with custom validation within copies of ezpublish datatypes to provide for more user friendly validation / storage / etc . I find that for the most part, the best results are found in focusing your changes to the datateypes themselves (making variations with modifications) - I have added ezimage datatype to ignore validation errors and always store the uploaded image regardless of other attribute validation errors. This helps editors greatly for example. - I have manipulated other various datatypes to ignore default php code and content class definition attribute / datatype defaults (such as validation settings stored within the class definitions in the admin). This let a customer work with an existing configuration / content in a unique way which avoided default validation and instead provided extended clientside (javascript) and serverside validation which functioned in a more user friendly way. This code was published as a number of projects, http://projects.ez.no/bcicfv I hope this helps.
Cheers Heath
Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org
|