I really don’t think html validation is important. Only the ability to create your own callbacks and regex yourself.
After all trying to support all the possible ways to validate would be a waste of your collective time and brain power.
The usa uses zipcode, we use postal, phones validate differently internationally, etc. Only the basics are needed.
Email, url, Text, Numeric, Alphanumeric, these are standard the world over.
The rest should be left up to the community as maybe a plugin or addon we can create and upload to a central location for the communities use.

I’ve even had to create validation that checks for Chinese characters and reminds the user to enter in english only, as its legally binding. 🙂
Wouldn’t want to see you guys have to create stuff like that. Your plugins are a much better use of time. 🙂

Marcus

And this is why I love it when Steve or Kevin post. LOL

Marcus

I haven’t used ADD-MORE’s within a grouped field structure yet. (what I mean by that, is I create simple groups, where the group has no field name, and all the fields within are then just arrays)

So how I do it is let’s say I have the following:

piklist('field', array(
	'type' => 'group'
	,'add_more' => true
	,'label' => 'Week Bookings'
	,'description' => 'Here you can book each week individually, including days off'
	,'fields' => array (
		array (
			'type' => 'select'
			,'field' => 'mae_sched_choose_week'
			,'label' => 'Week'
			,'columns' => 6
			, 'choices' => piklist(
				$wpdb->get_results("SELECT 
				w.ID AS weekID, CONCAT('Week ',w.menu_order, ' (',REPLACE(wc1.meta_value,', ".$weekyear."',''),' - ',wc2.meta_value,')') AS weekTitle 
				FROM {$wpdb->prefix}posts w
				LEFT JOIN {$wpdb->prefix}posts wp ON wp.post_title='".$weekyear."' AND wp.post_type=w.post_type
				LEFT JOIN {$wpdb->prefix}postmeta wc1 ON w.ID = wc1.post_id AND wc1.meta_key='mae_wks_start_week'
				LEFT JOIN {$wpdb->prefix}postmeta wc2 ON w.ID = wc2.post_id AND wc2.meta_key='mae_wks_end_week'
				WHERE w.post_parent = wp.ID AND w.post_type='weeks'
				ORDER BY w.menu_order"), array("weekID","weekTitle")
			)
			,'on_post_status' => array(
			  'value' => 'publish'
			)
		)
		,array (
			'type' => 'text'
			,'field' => 'mae_sched_days_on'
			,'label' => 'Days of Camp'
			,'columns' => 6
			,'value' => 'mon,tue,wed,thu,fri'
			,'on_post_status' => array(
			  'value' => 'publish'
			)
		)
	)
));

Notice there is no field name on the group level.
But there is on the child levels.

So I can retrieve the information quite simply by:

get_post_meta($postid, 'mae_sched_choose_week', false);
get_post_meta($postid, 'mae_sched_days_on', false);

This returns an array of the first and second fields within my add more.

You should be able to do the same with yours, provided its in post meta.
You would grab the parent group field, which would contain all the arrays for the add_mores below it in just one get.
get_post_meta($postid, 'pricing_tier_group', false);

Would get all the arrays associated with that group.

Hope this helps.

Marcus

It makes me wonder about your folder structure…

Mine is:
themename/piklist/parts/etc…

Is that the same structure?

Also, I’m not using a child theme.

Marcus

You are far too kind and you get a massive reprieve for being a javascript god yourself, because your a dad. <grin>

Hope you get to spend some time with jquery, you’ll love the api.

Trust me, when I say, that Kevin is the guru of JS, I’m more like an old fart who likes to know a few things.

Marcus