release

The last three months have been a bit of a blur. One of the things that has fallen off my plate was updating the GetPaid blog. So, here's a roundup of news from GetPaid:

Product

• The preferred means of consumption is the recipe! Tarballs are soooo Plone 2! (nothing against tarballs, actually, just no one is packaging them - if you want to lend a hand let us know via the mailing list). So while there aren't any new tarballs about since the 0.6.2 version, GetPaid has actually advanced to 0.7.5 and just reached rev2400! The recipe itself is at version 1.4.1 thanks to the continued efforts of the marvellous Lucie Lejard (aka La Reina de la Receta). Here's some of the changes to look out for:
• Payment processors: Payflopro is now a supported payment processor (larubbio)! ClickandBuy is also supported (olauzanne)! Pagseguro (Brazilian processor) is also in the works (rafaelcrocha) as well as VCS South Africa (hannesc). Ogone, PayPal, and Authorize.net all got an updates.
• PloneFormGen integration: after the demise of the former mercurial repository where this product was hosted, the action adapter to integrate GetPaid with PloneFormGen was migrated into the GetPaid repository (mcgruff.scruff).
• Variable donations amount: GetPaid now natively supports variable donations amounts that can be added to your cart (larubbio)
  
• Salesforce.com Integration: There is a new prodcut, Products.SalesforceGetPaidAdapter. It subclasses from the current Products.salesforcepfgadapter and allows you to specify what fields in your form, and in getpaids order get saved to salesforce when the order's finance workflow moves to CHARGED.(larubbio)
• More goodies: The cart now allows annotations (larubbio), checkout checks for site root to get store settings (lucielejard), discount details are reflected on the thank you page (flejard)
  

Documentation

• How to use the PloneFormGen integration (download PDF)
  
• Features page got light update. 
• Creating Content Types That Are Buyable, Shippable or Donations (dunny, copied from Products.PloneGetPaid documentation to web)
• How do I set up buildout for an existing Plone site with the getpaid recipe? (lucielejard)
• How to tie actions to payments (A brief explanation on how to tie workflow transitions, mailing, etcetera to a payment happening in getpaid) (perrito)
  

Sites

Collecting data on this has been a bit thin lately, even though several people have shared information about sites in the works. One that did launch with GetPaid just today is the York College/City University of New York. If you have additional sites that are live with GetPaid, please let us know via the mailing list!

Community

• Mailing list: 163 people
• Planning continues at our Features Brainstorm doc: http://code.google.com/p/getpaid/wiki/BrainstormingFeatures . Join in! Some of these features are on the drawing boards for Spring development.
  

Not your average Plone cookies or pizzas recipe, this is a recipe for getting paid!

Thanks to Lucie for updating the GetPaid recipe.You can get the new version on pypi:
http://pypi.python.org/pypi/getpaid.recipe.release/1.2 (see this link for readme on using the recipe to make it easy to add ecommerce to your Plone site).

The changes are:

* update the version for: getpaid.core, Products.PloneGetPaid, five.intid, getpaid.googlecheckout, getpaid.paypal and getpaid.discount
* added getpaid.report and getpaid.warehouse to the recipe

Several fixes have gone into a minor release of GetPaid that is now available in both a tag in SVN and a bundled product for download. This includes a fix to ensure it works on Plone 3.1.5+, a fix to the pagination of orders management, and other small changes. No significant feature changes from the original 0.6 branch, but this is now the recommended version.

• You can download it here: http://code.google.com/p/getpaid/downloads/list
  
• Find it in svn here: https://getpaid.googlecode.com/svn/tags/0.6.2
  
• Or read more about GetPaid here: www.PloneGetPaid.com
  

Just in time for the Plone Conference sprint, our Remote Sprint Goddess, Lucie, finished a release recipe for GetPaid, making it much easier for you to include GetPaid in your own recipe. Please give her your thanks and pat on the back!

More from Lucie:

The recipe is working and uploaded on pypi:
http://pypi.python.org/pypi/getpaid.recipe.release/1.0

You have all the detail on how to use it if you follow the link above. I will probably continue updating it today and make the documentation
prettier. I am currectly using it for one of our sites and seems to work correctly so far.

Surveying the State of the Art in Plone Ecommerce

I intended my talk for the conference to be a good learning experience that pushed my own understanding of GetPaid. As I am not a developer, I certainly don't know how to do a lot of things that people do with GetPaid. But, as GetPaid was my motive for actually learning how to use svn and making my first checkin, I figure I should be able to figure some of this stuff out using the available documentation and my knowledge of GetPaid. So as part of my talk, which will be walking through what you can do with GetPaid: out of the box, with community addons and with basic customziations, I have been asking a lot of questions! This has motivated some new documentation being produced that will continue to support new community members who are finding GetPaid. Also, I found a few bugs that are now in our tracker.

Some of the things I will show:

• Managing inventory with GetPaid
• One-page checkout (with PloneFormGen integration)
• Making a store

• Pay-to-publish content (working that integrates a payment step for job listings, ads, applications, etc)
• Making your own content type buyable (programmatically)
• Showing GetPaid information on your templates

Sprint Preparation and Plans

Distribution

• Eggify components and get to pypi (everything in externals already there)
• getpaid.warehouse
• getpaid.report
• Finish GetPaid? recipe; Document usage
• Buildouts:
• Test and finish reorganization (base, 30, 25, currently on meteoroid-branch) and document buildouts (how to add getpaid)
• Document and use in DevGettingStarted
• Merge branch or copy files on existing buildout
• update anonymous buildout (diff svn externals and cfg file). Fairly easy, as it was last updated in August.

Bugs & Issues

• fix issues
• Issue #209
•  Issue #202 
• Issue #117
• Improve paypal processor: make multi-item checkout possible, make/fix admin screen for processor

i18n

• update translations
• Spanish: in progress (FranGM, Wu, cjj)
• French (very close to done)
• German
• Italian
• Chinese
• Dutch

Testing

• add greater test coverage:
• getpaid.report

Documentation

• gather/improve/update/add documentation (list specific here)
• Review and improve content type integration for devs doc
• How to show price (or other GetPaid? properties) on a template in your site
• How to wire payment process to a workflow state change (ie create a piece of content, but pay before it is published)
• How to get and use getpaid.formgen
• How to customize the checkout process (including using available slots, ie for comments)
• Enabling components in buildouts
• Using the new buildouts
• Using the recipe
• Review mailing list and document errors messages (on plone.org doc collection) and how to fix them
• How to get and use getpaid.salesforce
• ReorganizeIssueTracker (in progress; cjj, gabrielle)

Release prep

• 0.7.0 release (would support 2.5 and 3 together)
• update changelog on plone.org/products/getpaid
• branch code
• make a branch to separate future 2.5 and 3 support (dennis)

If you haven't tried it already, check out the latest release from GetPaid and join 600 others!

Also, please note that we will have remote sprints this month! This Friday and the following one and then 2 days (Aug 21-22). Read more or see the sprint information wiki (includes svn refactoring proposal).

A while ago, we created the release branch for GetPaid's second major release, 0.6. However, we didn't officially release it (with packaged code etc), and in the meantime, several fixes and changes came in. So, we are now releasing 2 versions.

0.6.0: This is the originally branched code. Works well and preserves "backwards" compatibility for those using customized GetPaid code.

0.6.1: This is a final release. Includes API refactoring and unicode fixes. May break your customized GetPaid code but not too much :)

Both of these work on Plone 2.5 and 3.0, and apparently on Plone 3.1 also (though we currently aren't providing a buildout for 3.1).

To check out the changelogs, see http://groups.google.com/group/getpaid-changes 

As of earlier today, we had 258 tests passing on 2 versions of Plone (2.5 and 3.0) - yippeee!

So, with much joy, we are moving the trunk to the 0.6 branch for this release.

Next we will tag a 0.6.0 release candidate.

This release got a new directory of documentation as well as a lot of work on new features for shipping, fulfillment and reporting. Have a look at the latest buildout!

Ricardo has been helping us to clean up issues and we are down to 10 listed in the tracker, with several of those actually falling into the "continuous enhancement" category, as opposed to blockers or priority items for this release.

Here's a quick look at progress towards the 0.6 release and an update on the release.

• We are over 620 downloads of the 0.3 release tarball! (plus buildout usage)
• A bug got fixed in the 0.3 buildout branch this past week
• Several bugs got fixed in the trunk, including restored Plone 2.5 compatibility for the buildout, report-related bugs, template changes, and more.  Also, a tool got added to extract email addresses from customer records. Check out the change logs to see more.
  
• We are down to 14 issues tagged for M2 (actually less once we verify closure...). See the issues and grab one to fix or test!
  
• The 0.6 release branch will be made later this week. If you have goodies to include or bugs to fix, please do them asap!
  

Thanks for tuning in. Grab an issue, test the tools, and let us know how it looks so we can make way for 0.6 :)