[Gelöst] Split: How can guest users get emailed content from a post?

[Author]

Artikel

[jasonw-2]

What I'm really wanting to do with the forms on the front end for non-logged in visitors is to be able to have them email themselves a listing. They would click on a button to bring the form up, insert their email address, and this form will email them the pictures and information from that post. Is this possible as well? I really don't want people to have to register to use the forms. There will be bounce from that, I would imagine.

Thank you again, man. I really appreciate the help.

[Nigel Supporter Languages: Englisch (English ) Spanisch (Español ) Timezone: Europe/London (GMT+01:00)]

To avoid any confusion, let me be clear at the outset that a post form will publish a post. The primary purpose of the form may be to send an email (a form notification), and the generated post may be redundant if you don't want to keep a record of them, but it will get created. You may be happy manually deleting them from time to time, or set up batch jobs to clean them out (Toolset doesn't provide this), but it is something to think about.

Say you have a custom post type Articles that you want guest users to be able to request.

So you make a new post type "Requests", and add relevant custom fields (such as the guest's email address). You will also need to add a custom field which we will use to store the ID of the source article, which we will need in the notifications (so that we can send content from the article where the request was made rather than content from the request itself).

You make a form to "publish" requests which includes these fields (but which probably won't include post title, possibly not post content, unless you want the guest to include a message in their request).

For the id field you will automatically set its value to the current article, like so:

[cred_field field="source-id" force_type="field" class="form-control" output="bootstrap" value="[wpv-post-id]"]

You'll want to use CSS to hide it so that it is not visible in the form on the front end.

Now create your notification, which you will want to send when the form is submitted, and to send to the email address provided in the form field.

In the notification itself you can use standard Views shortcodes to output the title, the content etc., and you specify that these should be the title of the Article and not the request by providing an id attribute, the value of which comes from the hidden field you included in the form, something like this:

<p>source post title is [wpv-post-title id="[types field='source-id' output='raw'][/types]"]</p>

Is that all clear enough?

[jasonw-2]

Sounds perfect.

I will be trying to implement / create this in the next week or so. Seems like it's pretty straight up and I'll give it my best shot.

Thank you very much for taking the time to explain this. I will let you know how it goes. 🙂