Skip to end of metadata
Go to start of metadata

<ac:macro ac:name="info"><ac:parameter ac:name="title">New Proposal Template</ac:parameter><ac:rich-text-body>
<p>This page has been created from a template that uses "zones." To proceed:</p>
<li>Edit the page</li>
<li>Replace sample content within each zone-data tag with your own content</li>
<li>Remove this notice</li>
<li>Save the page</li>
<li>When you are ready for community review, move this page to the <ac:link><ri:page ri:content-title="Ready for Review" /></ac:link> section on the edit page.
<ac:macro ac:name="note"><ac:parameter ac:name="title">No placeholders allowed!</ac:parameter><ac:rich-text-body>
<p>Please do not create placeholders. Wait until you have sufficient content to replace all sample data in the proposal template before creating your proposal document.</p></ac:rich-text-body></ac:macro></li>
<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Service_Wordpress Component Proposal

Proposed Component Name Zend_Service_Wordpress
Developer Notes
Proposers Eric Clemmons
Zend Liaison TBD
Revision 1.0 - 2 September 2009: Initial Draft. (wiki revision: 8)

Table of Contents

1. Overview

Zend_Service_Wordpress allows you to easily consume a WordPress blog's content via WordPress' XML-RPC gateway via a fluent interface.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • This component will support connecting to a single & multi-blog site.
  • This component will allow read-only access to blog content.
  • This component will return authors.
  • This component will return posts.
  • This component will return comments.
  • This component will return categories.
  • This component will return tags.
  • This component will not save any data using Zend_Cache or to the filesystem.
  • This component will not allow modification to blog content.
  • This component will privately cache redundant XML-RPC calls.
  • This component will allow bypass of cached XML-RPC calls.
  • This component will allow sub-classing.

4. Dependencies on Other Framework Components

  • Zend_Service_Exception

5. Theory of Operation

  • Application Developer instantiates Zend_Service_Wordpress

6. Milestones / Tasks

Describe some intermediate state of this component in terms of design notes, additional material added to this page, and / code. Note any significant dependencies here, such as, "Milestone #3 can not be completed until feature Foo has been added to ZF component XYZ." Milestones will be required for acceptance of future proposals. They are not hard, and many times you will only need to think of the first three below.

  • Milestone 1: design notes will be published here
  • Milestone 2: Working prototype checked into the incubator supporting use cases #1, #2, ...
  • Milestone 3: Working prototype checked into the incubator supporting use cases #3 and #4.
  • Milestone 4: Unit tests exist, work, and are checked into SVN.
  • Milestone 5: Initial documentation exists.

If a milestone is already done, begin the description with "[DONE]", like this:

  • Milestone #: [DONE] Unit tests ...

7. Class Index

  • Zend_Magic_Exception
  • Zend_Magic (factory class)
  • Zend_Magic_MindProbe
  • Zend_Magic_MindProbe_Intent
  • Zend_Magic_Action
  • Zend_Magic_CodeGen

8. Use Cases


Connect to your blog


Get various blog information


List all tags


List all categories


Get recent posts


Get post information

9. Class Skeletons



wordpress wordpress Delete
proposal proposal Delete
service service Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Oct 08, 2009

    <p>Perhaps this should be Zend_Service_Blog with a Zend_Service_Blog_Adapter_Wordpress class, like Zend_Db and Zend_Db_Adapter_Mysql</p>

  2. Feb 17, 2011

    <p>If we were to follow the Zend_Service convention, then the name should remain Zend_Service_Wordpress IMO, since each component of Zend_Service is a different service - though I agree, it would be much better to have separate blog adapters to accomodate for different blogging platforms.</p>

    <p>Is anybody working on this now? I want to continue this component if possible <ac:emoticon ac:name="smile" /></p>