2009/5/29 Laurent Alquier <lalqu...@gmail.com>:
> Hi
> I used the Create Class form for the first time today and while it did
> create the classes I wanted, it also threw a couple of errors in the
> process.
> 1- I got the following PHP error for each field processed by the form:
> Notice: Undefined property: SFTemplateField::$input_type in <PATH TO
> EXTENSIONS>\extensions\SemanticForms\includes\SF_FormField.inc on line 222
>
> 2- The form ignored by choice for Field name (it used the property name by
> default).

Is there any reason the 'class' shouldn't enforce that convention?
i.e. just have two choices, property name and display name, and use
the property name as the field name.

Seems like a logical convention to have, but it may cause problems for
reasons I haven't considered.

> Other than that, it's a great time saver.
> - Laurent Alquier
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Semantic Forms" group.
To post to this group, send email to semantic-forms@googlegroups.com
To unsubscribe from this group, send email to 
semantic-forms+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/semantic-forms?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to