[eluser]JulianM[/eluser]
Yes, set_value works nice for me, too.
You can pass the default value if you want to avoid to receive an error if the passed variable do not exist, or you can call it using @set_value, however I prefer the first option.
Good luck
Julian
[quote author="benajnim" date="1241211692"]What I've done to solve this problem is use a method called getRecord() in my models. It will always return a "record" array and in the case of a new record, will simply populate empty field values. No complaints when the views are rendered.
The set_value() method of the form helper also appears to gracefully handle the problem of attempting to read/print unpopulated variables on your form. You just need to pass a default value to use if the variable you're attempting to access is not defined. It seems to work a lot like the sql function coalesce().[/quote]
