Snippets
Gravity Forms is a very easy to use yet flexible tool for building forms in WordPress. It uses quite a bit of JavaScript and custom CSS, so it's careful to only load its scripts and stylesheets when needed. But if you put a form into a custom field, e.g via Advanced Custom Fields, how will Gravity Forms know it needs to load them?
Gravity Forms plus its PayPal add-on make for a very easy donations form (and so does my Gravity Forms eWAY add-on). But the PayPal item description is pretty formulaic, and probably doesn't represent the donation very well especially when there are multiple options. A simple filter hook with a few lines of code can easily fix that though.
A common problem with input forms is that users get impatient and click the submit button twice. This can lead to double (or triple, or quadruple!) form submissions, which can really mess things up (especially if you've added a billing step to your form!) Stopping it can be surprisingly complex, but here's a simple piece of browser script that will prevent most users from making multiple submissions with Gravity Forms.
My eWAY payment gateways for WP e-Commerce and Gravity Forms now have some new features that should help some merchants building e-commerce solutions.
If you ever wanted to build an online donations form with Gravity Forms and bill people through DPS (apparently quite a popular payment…
Gravity Forms is a great way to build all sorts of forms in WordPress. It can be so simple that non-programmers can easily build their own basic forms. It's also incredibly flexible so programmers can extend it in myriad ways, even by adding some complex custom fields of their own. But as usual, there's a trade-off -- ease of use for non-programmers means lots of hoops to jump for programmers. Here's an overview of how I built some fairly complex compound fields for a custom application using Gravity Forms.