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.
Currently, the of a post generated from a Gravity Form submission is set via the Post Title, Post Body or Post Excerpt fields.
I’ll admit it. I’m a bit of a Gravity Wiz. And as such, I do a good bit of testing on really long multi-page Gravity Forms.
Request users to confirm important information on your forms by entering it twice. Ya know, like the option on the email field. Here’s the code: To install this snippet simply copy and paste the full code into your theme’s functions.php file.
Use this snippet in conjunction with Gravity Forms dynamic population functionality to populate the current user’s role into any form field.
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.
Want to really entice your visitors into submitting your Entry Limit-enabled form. Display the number of entries left based on the entry limit.
This simple snippet allows you to close comments on posts created via a Gravity Form.
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.
This snippet is almost identical to the snippet. The key difference is this will send a notification to post author rather than an email stored in a custom field.
This handy snippet allows you to send an email notification to the user who submitted a Gravity Forms generated post when that post is published.
If you’re using the Gravity Forms User Registration Add-on, this snippet will allow you to skip registration for users who are logged in when they submit the form.
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.