Hi Caius, Do you mean for the ID or for the name?
I see no reason for the name. However, I think the name shouldn't actually be human-readable at all. It should be an encoded string (isn't it usually already?), so we are always sure the data is coming directly from the specific FormUI field. For the ID, I don't think "[" is supported. ~arthus On Aug 16, 2009, at 8:12 AM, Caius Durling wrote: > > Hi guys, > > I've just changed the comment form to add "comment_" to the ids of > each element in the form, and noticed the names are just mirroring the > id. Which leads to field names like "comment_name", which exists as > $_POST["comment_name"] in the submitted data. > > Now I realise this is my personal taste, but I prefer to use $_POST as > a named array for post data, so you'd access the name field like > $_POST > ["comment"]["name"]. I prefer separating the data out in this way, > because it makes it easy to ignore all post data except for the form > you want (because $_POST["comment"] contains only the data from the > comment form.) > > So I'm wondering if there's a good reason for us to stick with > comment_name, or if we could move to comment[name]? > > C > --- > Caius Durling > [email protected] > +44 (0) 7960 268 100 > http://caius.name/ > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
