WordPresss 2.5

This is the only web site that references the new custom_fields feature. Is there documentation available somewhere for the API side, should the custom_fields be an array of structs with each struct having a key and value with an optional id?

Thanks,
Angelo

I joined the mailing list.

I did a test and it appears my assumption was right, the custom_fields is an array of structs. Each struct should contain a key and value. A struct should also include the custom field ‘id’ if the struct is updating an existing custom field. Otherwise the struct should only include the key and value to insert a new custom field.

WordPress is awesome!

@Wdiget Guy –

The getIso error was recently brought up in a ticket:

http://trac.wordpress.org/ticket/6612

I haven’t asked for that patch to be committed yet, I’m waiting for feedback from some of the current blog clients before we mess with date/time settings, which have proved to be very sensitive in the past.

To answer your question about date_created_gmt, just the standard YYYYMMDDTHH:MM:SSZ format.

Hi Joseph — thanks for all of the great info.

I have a follow up question on date/time. I’m writing a Java app using the redstone xmlrpc library.

Whenever I set the postCreated field, WP interprets/modifies the timezone to GMT. For the time being, I’ve kludged the date (adding the difference between the local TZ and GMT) so that WP gets the post date right.

I’m using the java.util.Date class for the postCreated parameter.

Any thoughts on whats going on here? btw, I’ve had zero luck in getting date_created_gmt to work properly.

thanks

tom

Thanks Joesph

I just signed up for the email list and posted the following there:

I’m writing a Java app using the redstone xmlrpc library and having a problem with both postCreated and date_created_gmt

Whenever I set the postCreated field, WP interprets/modifies the timezone to GMT. For the time being, I’ve kludged the date (adding the difference between the local TZ and GMT) so that WP gets the post date right. This is ugly and I’d rather not do this . . .

It’s been suggested that I use the date_created_gmt field, but I’ve had zero luck getting this to work. It seems that WP doesn’t recognize the passed in java.util.Date as a valid date and subsequently defaults to the current date.

Any thoughts on whats going on here? Anyone care to share some working code?

Here’s a snipet of what I’m doing . . .

HashMap content = new HashMap();

java.util.Date postDate;

Calendar c = Calendar.getInstance();
c.add(Calendar.Days, 7);

postDate = c.getTime();

// System.out.println(postDate); yeilds

// snip . . .
// title, keywords, category, description, etc. are all populated . . .

content.put(“title”,title);
content.put(“mt_keywords”,keywords);
content.put(“categories”, new String[]{category});
content.put(“post_status”, “publish”);
content.put(“description”, articlebody);
//content.put(“date_created_gmt”, postDate); // date doesn’t get interpretted correctly and defaults to the current date
content.put(“dateCreated”, postDate); // date is offset by local TZ – GMT

Object[] params = new Object[]{new String(“n/a”), user, pass, content, new Boolean(“true”)};
Object token;
try {
token = client.invoke(“metaWeblog.newPost”, params);
} catch (XmlRpcException ex) {
Logger.getLogger(WPDripFeederView.class.getName()).log(Level.SEVERE, null, ex);
} catch (XmlRpcFault ex) {
Logger.getLogger(WPDripFeederView.class.getName()).log(Level.SEVERE, null, ex);
}