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.
- 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.