Leo Charre > WordPress-API > WordPress::Base::Object

Download:
WordPress-API-1.10.tar.gz

Dependencies

Annotate this POD

View/Report Bugs
Source  

NAME ^

WordPress::Base::Object

DESCRIPTION ^

base for WordPress::API objects

METHODS ^

new()

abs_path()

abs_path_resolve()

optional argument is abs path if not, expects abs_path() to have been set. attempts to resolve to disk returns abs path resolved subsequent calls to abs_path() will also return this value.

save_file()

dumps data structure to abs_path(), as YAML conf file

url() not implemented

attempts to save unless we have an id the method link() will return only if it was loaded, the method url() will save to the wordpress blog if no url is present, and then return

load()

save()

delete()

id()

aliased to post_id or page_id, etc depending on object_type()

make_xmlrpc_alieases()

arg is class (your object class) and optionally one of 'Post', 'Page' we try to resolve what kind of object you have from the name, if your object package class ends in Post or Page, don't worry.

This creates aliases to WordPress::XMLRPC::getPage or WordPress::XMLRPC::getPost, etc.

xmlrpc_get() xmlrpc_new() xmlrpc_delete() xmlrpc_edit()

These are called internally. If your object is a Post object, then xmlrpc_get returns same as getPost would, arg is id. Used internally.

object_type()

returns Page, Post, or MediaObject

NOTES ^

This module is meant to be inherited by WordPress::API::Page WordPress::API::Post WordPress::API::MediaObject, etc

syntax highlighting: