This was with a stock theme, applies to front end forms. I actually found the fix on stack overflow via someone else with the same issue. I’ll check with plugins disabled but I thought I did that.
I found it – exactly that. Didn’t know it wouldn’t work in the form itself (requires an action in the functions.php)
Thanks!
I wrote this hack (in javascript) to “fix” the issue;
$('form label > input').each(function() {
$(this).insertBefore($(this).parent());
});
$('form.acf-form label').each(function() {
$(this).attr('for', $(this).prev('input').prop('id'));
});
also in other cases (a nested options list) the <label> element actually “wraps” the input — which is even worse because there’s no easy way to do a “parent” selector in pure CSS.
ie; if I wanted to style the label of a checked input, it would not be possible to do in CSS when it was wrapping the input.
labels should always come after an input in code, and move them around and style them with CSS
any update on this? I was confused as the documentation shows that you can choose from Archives pages, but my Page Link does not ever show me archives… am I doing it wrong? (ACF Pro)
http://www.advancedcustomfields.com/resources/page-link/
I came here to mention something similar, but I feel this is the same “bug” — it isn’t a bug so much as a non-standard way to make a plugin.
you should always use a vendor prefix in your functions. register_form should be acf_register_form. get_field should be acf_get_field.
this needs to be done ASAP and encourage users to transition their code to prevent more mishaps like this from happening. for now you could always use php to make both functions happy until a few versions down the line.
part of the blame goes to Woo as well for allowing such a huge product to have the same problem.
