December 23rd 2010 - Entry Posted to: AMFPHP,FlashPress,General,Zend AMF

I’m just finishing off the next version of FlashPress.

Apart from some bug fixes, the main change is the addition of a postComment, userLogin and userLogout methods.

Changes:

• New postComment method
• New getPostTems method (this depreciates getCategories)
• New userLogin method
• New userLogout method
• Addition of customTax property on PostVO object, to handle custom taxonomies on post objects
• Slight changes to TermVO object properties. One additional property added
• Bug fixes for getPost method
• Bug fixes for getUser methods and WpUserVO object
• Adjustments to the search method so it searches custom post types as well as built in

Some thoughts about the postComments method.
This is currently working fine in dev. I’m curious as to how you would like this method exposed. It does write to the DB, so I’m in half a mind to wrap it within the current writeable variables. However, in doing so, you make available the rest of the writeable methods, which might not be that desirable to all users. I’m hesitant to go down this path.

So, what about a new global constant that either allows/ restricts comments? Or I can simply hook into the wordpress options and check what is set within the ‘Discussion’ panel and on a per post basis and allow / restrict comments based off that?

At the moment the method does not validate against users. Any new comments are placed into the moderation queue. A subsequent comment from a commenter that has an approved comment is automatically approved. Which is left up to the wordpress commenting mechanism.

Commenting really requires basic user management. Do you want to see this in FlashPress. Something like a login / logout method? Which I’ve added.

Commenting now hooks into the WordPress options settings, honoring either the blog wide and or individual post commenting settings.

Any other methods that you think should be in? If not, I’ll freeze the API and just clean up the classes documentation, fix bugs and roll out a version 1 release along with some examples. Happy times.

6

December 17th 2010 - Entry Posted to: AMFPHP,General,wordpress,Zend AMF

There is another, seemingly dead WordPress – Flash project out there called FlashPress.

I’ve never gotten around to coming up with another name for what I’m doing.

Anyone got any ideas?

14

December 15th 2010 - Entry Posted to: ActionScript 3,AMFPHP,Zend AMF

Changes

1 / Changes to WpPostVo Object

• a / If the post has a featured image, the URL to it is included, otherwise its an empty string
• b / The posts tags are listed (if it has any) as an array of TermVo Objects
• c / The posts categories are listed (if it has any) as an array of TermVo Objects
• d / The posts attachments are listed as an array of their URLS

2 / Changed inheritance of WpPostVo and WpSearchVo. Inheritance chain is as follows: WpPostbase->WpPostVo->WpSearchVo. Reason for this change is that the WpSearchVo only differs from the WpPostVo in its use of the ‘score’ attribute. Also, it makes sense that the WpSearchVo object returns as much information as a standard WpPostVo object.

3 / Fixed an variable type issue with searching that meant that only integer based score results were returned. This has been changed to a Number.

4 / Rejigging of internal helper methods

5 / Removal of two redundant VoObjects, which had been replaced by WpTermVo.

6 / Package name of the actionscript demo has changed from ‘noponies’ to ‘com.reformation’. This is due to the slow move of this blog to a new location.

Let me know how performance is with this release. The internal post retrieval method is now doing more work, but should save you having to make extra database requests. I’ve tested it with a request for 100 posts and its quick. But let me know. Let me know if you encounter any bugs etc.

I’ve not had time to finish the more full featured demo, but its coming.

Download here: Flash Press 0.8 (791)

6