FlashPress Feature Requests?

I’m currently re-writing my Flash press PHP service.

I’ve moved it to using the Wordpress api as opposed to working on the database directly.

Most methods are complete, with some no longer needed. For instance, all posts / pages can be returned with a simple ‘getContent” method, but would you rather have seperate, ‘getPost’,’ getPosts’, ‘getPage’, ‘getPages’ etc methods?

What additional features would you like to see in this service? Remember, that the service has access to most of the Wordpress API. There is no point recreating each an everything method, but there might be some methods that are more useful than others. I’ve also added in two methods for calling Wordpress methods beyond what the service supports, one for the Wordpress API and one that handles SQL requests, channeled through the Wordpress API.

Anyway, let me know your thoughts, if you have any.

At the moment, I’ve only supporting ZendAMF but will test out AMFPHP if I get the chance.

Update:
I’ve got it mostly completed. Just have to work on documentation and some examples. I’ve got reading and writing to the Wordpress database for posts / pages and attachments. And reading support for most other Wordpress features.

To get Write support for attachments (image resizing) you will have to require admin.php, but as you have to require a Wordpress file to get access to the Wordpress API anyway, I’m sure thats not a problem for anyone. Let me know if it is.

AMFPHP | Zend AMF service for connecting to Wordpress

For a project I have in development I needed to once again create or connect to a CMS.

I’ve previously rolled my own CMS using AMFPHP, which works fine. However, I thought I’d give using Wordpress a go as a CMS system for Flash sites, with an AMFPHP connection between Flash and the wordpress database.

I stumbled on Amfphp WordPress Integration (AWI) which seemed to offer what I was after. However, it has not been updated for a long time, and supports wordpress 2.3 or so and below. The project I have on needs to take advantage of wordpress’s tagging and categorising of content, which was the main element missing from the awi project. So, I re wrote it, and added in many more methods and dropped many of the existing ones.

You can view an example of it at work here: http://www.noponies.com/dev/cloud/ Which is using a hacked version of the WP-Cumulus Wordpress plugin, from here: http://www.roytanck.com/tag-cloud/. Instead of using a PHP method to create XML, I’m just using AMFPHP to call a getTagCloud method, and using the data in a similar fashion to how the WP-Cumulus Flash file works. Clicking on either a category (white text) or a tag (grey text) calls another method that pulls the various posts that are filed under that particular category or tag. Pretty simple stuff.

Ironically after embarking on this little project, I found a few other similar ones, this one (Flexpress) here by Jonnie Spratley which can be found here http://jonniespratley.com/blueprints/ and this swc library FlexDb from here: http://ghalex.com/blog/?p=53. Always annoying to re invent the wheel.

I’ve called my project, FlashPress, which is who I intended it to target (Flash devs) or people like me.

As of version 0.2 this also works fine with Zend AMF, and I’ll update the source file with some demos of connecting using Zend AMF.

Anyway, enough rambling, you can download a version here;

Source Files Version 0.2
Flash Press (1820) -

Let me know if there are bugs etc. I’m not really a PHP guy, nor a MYSQL guy, so I’m definitely interested in hearing about ways to improve things.