I suspect this is really easy to do, but for the life of me I can't figure it out - is it possible to add an entry to an existing form from the admin area of WordPress rather than filling out the form on the front end of the site?
Thanks!
PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.
Can you add an entry to a form from the back end?
-
You can use the preview link to submit entries from the backend. I'm not aware of another way.
I like using the forms on the front end when I have to manually enter information for someone (like I took a handwritten entry for some reason, and I want it in the database with all the other entries.) It helps me see how easy or painful data entry in my form is.
Please post what it is you're trying to avoid on the front end, and maybe we can help with another way of entering the data without using the front end.
Posted 13 years ago on Sunday July 31, 2011 | Permalink -
The reason we'd want to enter entries from the backend is that if the form is set up to send confirmations, it will send one, and in cases where we're adding an entry manually, we don't want a confirmation to be sent to the user - it's confusing.
Posted 13 years ago on Monday August 1, 2011 | Permalink -
@illuminea Good point. Notifications are sent even when using the Preview functionality. We can look at adding an option to the Preview screen so you can disable sending of one or both notifications. Until we do this i'm not sure of an easy way around this problem.
Posted 13 years ago on Monday August 1, 2011 | Permalink -
How about adding a hidden field to the form called "notification", allow it to be populated via query string, then use the gform_disable_user_notification hook to turn off notifications when the form is accessed and that hidden notification field is "false".
Then you could access the form at http://example.com/registration-form/?notification=false and no notification would be sent because of the gform_disable_user_notification function you added to your functions.php.
You could also just embed the same form in a private/password protected page with the value for that field embedded in the shortcode, and then administrators who are making back end entries could use the same form, but on a new page, and not have to worry about the query string.
Would that approach work?
It does not appear that it's really easy to do, but I think it's doable.
Posted 13 years ago on Monday August 1, 2011 | Permalink
