- We need to put the form on a post (type) along with a description text and other fields.
Gravity Forms can be embedded in a page, a post, a widget or a template.
- Only logged in users can submit an entry and only once in the form's lifetime.
You can satisfy this requirement with the "no duplicates" rule on the username or email address.
- For events with limited seats we need to limit the total number of entries.
You can limit the number of entries per form.
- Easy duplication of previous forms for similar events, templates maybe?
Duplicating a form is a one-click operation in the form builder.
- The form must have a opening and closing date.
This feature is included as well, and you can show alternate content when the form is not visible because of these rules.
- The user should be able to edit it's entry while the form is still open.
If you mean the user should be able to go back and edit their entry before the form expires or event passes, this is not a built in feature of Gravity Forms. There is no provision to let a user go back and edit their entry. You could probably do it as a customization, pulling up entries a logged in user has made, let them select the one they want to edit, then retrieve the values they submitted and pre-fill the form with them. They can change whatever needs to be changed, then you could update the existing entry and delete the new entry which would be recorded for the edit. It's not built in, but it could be accomplished with some programming.
- Some users might be banned from events altogether, this is noted in the user meta data. Can we hook into pre rendering of the form and display a error for those users? We have experience in WP development.
This is an interesting on. You can use the gform_pre_render filter to prevent a user from seeing a form. You could apply a gform_pre_render filter to all forms (or just select forms) to always check the logged in user's meta to see if they are blocked from events, and if so, not show the form and show alternate content. Or, you could do this before Gravity Forms is involved by protecting the page where the form exists, or wrapping the Gravity Forms shortcode in some sort of shortcode or function to check the user meta and see if they are banned from events and thus should not see the form.
Let us know if you have any more questions.
Posted 11 years ago on Tuesday January 22, 2013 |
Permalink