<p>On Jun 19, 2011 3:36 PM, "Daniel Jalkut" <<a href="mailto:jalkut@red-sweater.com">jalkut@red-sweater.com</a>> wrote:<br>
><br>
> This change altered the behavior of WordPress so that custom fields with a leading _ underscore cannot be edited by clients of the API.</p>
<p>This doesn't seem like expected behavior. Affecting XML-RPC was not one of our goals.</p>
<p>> Does anybody know if the WordPress team stance on this is that 3rd party plugins should only use "non-protected" naming conventions for their custom field keys?</p>
<p>They should use underscores. Plugins do that not just to keep it out of the custom fields UI, but to indicate to WP that they will be handling the saving of that key.</p>
<p>I brought it up with one of the other core developers. I'll post here probably tomorrow with an update.</p>
<p>Nacin</p>