Use multiple User Registration feeds to assign different user roles based on the submitted email domain.
A simple method for showing and hiding Gravity Form fields based on the current date.
If you’ve checked out the latest beta for the Gravity Forms User Registration add-on, you might have noticed one of the awesome new features is “Pending Activations”.
Level of difficulty: easy, really easy What you’ll need: Gravity Forms (Developer License) Gravity Forms User Registration Add-On Justin Tadlock’s Members Plugin About 15 minutes Introduction WordPress already has quite a lot of the functionality you need to create a basic membership site.
Had a request to demonstrate how it would be possible to populate a date which was one year from the current date into a Gravity Forms field.
Are you interested in adding a quick pre-submission confirmation page to your forms where users can preview their entered data before it is submitted.
Had an interesting question on the forum today: The site has multiple publications that are available for purchase, each has a separate price value.
A user on the Gravity Forms Support Forums posted today asking if it were possible to setup a shipping fee that was only applicable if the order total was over a certain amount.
This tutorial/snippet expands on the snippet. Here is a refresher on the issue: Currently, the post status of a post generated from a Gravity Form submission is set via the Post Title, Post Body or Post Excerpt fields.
The problem: You want to register users and allow them to optionally specify if they would like to create a site with their registration as well.
Here’s a little story and a little tip. I was recently speaking with a friend (yes, wizards do have friends) and he was sharing some of the requirements for a site he was working on.
The concept is pretty simple. Using Gravity Forms “Post Fields” you can create a form which generates a post when it is submitted.
Have you ever wanted to conditionally show or hide a field depending on whether the user is logged in or not. No, never. How about if you only want to require a captcha field for non-logged-in users.