[wp-xmlrpc] Protected metadata impact on 3rd party plugins and API

[Andrew Nacin]

On Jun 19, 2011 3:36 PM, "Daniel Jalkut" <jalkut at red-sweater.com> wrote:
>
> This change altered the behavior of WordPress so that custom fields with a
leading _ underscore cannot be edited by clients of the API.

This doesn't seem like expected behavior. Affecting XML-RPC was not one of
our goals.

> 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?

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.

I brought it up with one of the other core developers. I'll post here
probably tomorrow with an update.

Nacin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-xmlrpc/attachments/20110619/c1fc3c41/attachment.htm>