This system is of 3 parts. It’s goal is to backup a copy of a post to a central server.
—————————————–
PART2: a simple form to test the above
—————————————–
A simple WordPress Plugin that upon publish (not draft) posts a copy of the blog post/page, the tags and the categories to a centralized server. Basically a extended and authenticated RSS feed.
Unlike RSS, Update and Delete events should also notify the server with the appropriate action.
A sample call/post would have the following fields.
Post to: wppostbackup.com/wpinput.php?
Access Key: 151141155151
Action: Create | update | delete
Item: Post | Page
URL: http://myblog.blogspot.com/123/A-Blog-Post
Title: My Blog Post
Body: A bunch of copy
Tags: tag1, tag2, tag3
Comments: comment1, comment2, comment3
The plugin admin has two fields, an API key and a url for the server to post to (e.g. wppostbackup.com)
The plugin must be able to detect updates to the plugin and have sources held at the server e.g.
http://www.wppostbackup.com/plugin/version1.zip
The plugin must be compatible with WordPress MU
The plugin must keep a 30 day log of what it does to the server and the state of the reply. In the case that say the API key is delined it should show that with a red text.
—————————————–
PART2: a simple form to test the above
—————————————–
basically just a conventional web form to submit the data above.
—————————————–
PART3: a server to accept these and generate keys.
—————————————–
This is the app that the parts (1) and (2) talk to.
There should be a facility to create, list, update and delete system users
There should be 3 users roles
A super admin role, who can Create/Read/Update admins or bloggers.
A admin role, who can create bloggers
A blogger role, who can CRUD blogs and CRUD the
each blogger needs a unique API key to be generated, that goes in the plugin of the blog.
this API key can be valid, expired). If the key is not valid the system will ignore the submission and notify the admin section of the plugin or the form.
Bloggers can have multiple blogs in this admin, they should have the url for the blog and the username and password.
Beneath each Blogs have a list of entries (that sent from the plugin or form) and event log with each one (e.g. created at time, updated at time, deleted ) these can be created or deleted.
This is a rush project, Need this by next Tue.
