[wp-trac] [WordPress Trac] #43559: wp_ajax_add_meta() does not allow empty values
WordPress Trac
noreply at wordpress.org
Sat Mar 17 18:46:28 UTC 2018
#43559: wp_ajax_add_meta() does not allow empty values
--------------------------------------+------------------------------
Reporter: charlestonsw | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Options, Meta APIs | Version: trunk
Severity: normal | Resolution:
Keywords: has-unit-tests has-patch | Focuses: rest-api
--------------------------------------+------------------------------
Comment (by charlestonsw):
I will try the patches -- I"m sure they'll be fine as I've modified WP
Core myself on my VVV box to test the theory behind the original request.
The question is will these patches make into core someday? My app is
working fine , I wrote my own workaround so my users can work with the
current limitations of WordPress as per the full use case here:
The full use case --
1a) Site admin logs into the main services site.
1b ) Open a custom post type from the WP Admin page.
1c) Add a custom field "box_title".
1d) Save the custom field (leaving value as blank) -- PROCESS FAILS per WP
Core restriction.
2a) An end user consumes the meta from a remote app via the REST API.
2b) The app does not set the text inside a HTML element per the Vue app to
blank because the post has not matching key (see 1b above).
Could I build a new app that uses the REST API to force meta onto the
original post and set it to blank, sure can. But why would I go about
writing a web app to replicate the base WordPress app with a new admin UX
just so they can set a custom field value to blank? I could write an
entire app to replace WordPress admin and front end UX -- possibly even
using the REST API much like Calpyso. But why?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43559#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list