Bug #935
AdvancedCustomFields not accessible from XMLRPC
| Status: | Closed | Start date: | 03/30/2013 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assignee: | KevinH | % Done: | 100% | |
| Category: | - | |||
| Target version: | Dev Sprint 5 | |||
| Component: |
Description
AdvancedCustomFIelds are NOT the same as custom_fields
this means I cannot set them via the XML-RPC API. ugh.
See this thread: http://support.advancedcustomfields.com/discussion/3964/xml-rpc-integration/p1
Can we just use standard custom fields instead?
History
#1 Updated by KevinH almost 5 years ago
- Status changed from New to In Progress
I have changed all fields from select to text which should resolve the xml-rpc issue. If you are still having any difficult please let me know and we will make further changes to custom field handling.
#2 Updated by KevinH almost 5 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Tested via json and it works fine (see draft "Story Title").
#3 Updated by n8fr8 almost 5 years ago
Can you show me the JSON call you made exactly? Just curious about how you are representing the keys and values (as arrays, in arrays)? The Wordpress XML-RPC docs on this front are a little confusing.
#4 Updated by n8fr8 almost 5 years ago
- Status changed from Feedback to Resolved
Yay, it is all working now... even setting the media_value and media_guid.
Thanks for the help, Kevin!
http://storymaker.cc/plants-keyboard-coffee/
At some point, we can experiment with turning the fields back to Select, but for now, let's leave it as is.
#5 Updated by n8fr8 almost 5 years ago
- Status changed from Resolved to Closed