Hi @Steve! First off, congrats to the team for the excellent work! I’m one of the “outsiders” who never used ACF, Types and the like just because I don’t want to be restricted by ‘their way of doing things’. So coding was the only option to maintain the WP way.

Now, what I said wasn’t about updating a hidden field. But not being able to monitor a field twice.

Let me replicate a code example using the same parameters as above:

piklist('field', array(
    'type' => 'group'
    ,'label' => 'Address:'
    ,'fields' => array(

    		array(
    		'type' => 'text'
	        ,'field' => 'address'
	        ,'label' => 'Street Address:'
	        ,'columns' => 12
	      )

    		,array(
	        'type' => 'select'
	        ,'field' => 'state'
	        ,'label' => 'State:'
	        ,'columns' => 4
	        ,'choices' => array(
	        	'CA' => 'California'
	        	,'NY' => 'New York'
	        	,'DC' => 'District of Columbia'
	        	,'TX' => 'Texas'
	        	,'Non-US' => 'Not from USA'
	        	)
	        /** The part that won't work IF we also have
	        * the other condition on the next field
	        */
	        // Start: -->
	        ,'conditions' => array(
	        	array(
	        		'type' => 'update' 
	        		,'value' => 'Non-US'
	        		,'compare' => '!='
	        		,'field' => 'country'
	        		,'update' => 'USA'
	        	)
        	)
        	// <-- End
      	)

         	,array(
       		'type' => 'text'
       		,'field' => 'state_other'
	        ,'label' => 'State/Province/Region:'
	        ,'columns' => 4
	        ,'conditions' => array(
	         	array(
	        	      'field' => 'state'
	        	      'value' => 'Non-Us'
	        	)
	          )
        	)

        	,array(
      		'type' => 'text'
      		,'field' => 'country'
      		,'label' => 'Country:'
      		,'columns' => '4'
      	        )
    )
));

In this quick example we have a field (state_other) hidden and only shown when the “Non-US” option is selected from the state field. That’s the first time we monitor the latter. So far so good.

Now, if we wanted to monitor the state field [with our other condition in place] to update the last field (country) [i.e. monitor the same field twice], we can’t.

Makes sense now?

I figured that you’re intentionally not allowing “double monitoring” to prevent other issues (?), but since I found a case that it’d be useful, I thought I should mention it.

PS – Irrelevant: On another note, are all HTML form attributes supported? Could we use autocomplete' => 'on' for instance?

I noticed that you can’t have a field “monitored” twice. I.e. (i) to show/hide a field AND (ii) to update another field.

Quick example: We have a “US States” select field with one option being “I’m not from US”. If that option is selected, a textbox is shown for manual input of state/province. That condition works.
We have another textbox called “Country”.
If we wanted to monitor the “US States” field (again) to auto-update the “Country” field to ‘USA’ unless the “I’m not from US” is selected, we can’t.

Don’t know if it’s a bug but I thought I had to mention it. 🙂