Answers.Body: <p>You can listen for the <code>beforeSave</code> event, but by redirecting or rendering another template, you're essentially hijacking the request and cancelling the initial save.</p>
  
  <p>You could fork the plugin and add some custom logic using a flag you can tell whether it's an initial save and to redirect, or it's a subsequent save and to continue processing as normal.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-20T12:02:57.587Z
Answers.Text: That's an idea. Is there a way I can on entry save, send those values to another template to review? So, the entry would be saved like normal, then I'd just have a field that called "Finished" or something, and on the next page form submit, I'd update that entry if they finished the review process. I'd rather not fork the plugin and keep it's original functionality. Thanks.
Answers.UserDisplayName: Erik
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-20T17:47:27.340Z
Answers.Text: Yeah, you might be able to pull it off without forking... not 100% sure at the moment.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-20T17:52:48.700Z
Answers.Text: I believe I have a way. I've created a custom plugin, I look for `guestEntries.success`. From there I redirect to a page with the entry id in the URL (hashed so you can't just put an ID in) and I will use my custom plugin to do all that and have a 'review' page. I'm not 100% this will work, I'm working my way through it today. I can detail it out later if anyone is interested.
Answers.UserDisplayName: Erik
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-20T17:56:40.107Z
Answers.Text: Ahh, yeah... forgot about that event.  If it ends up working out, you should definitely add your solution as an answer. :)
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-20T18:07:39.840Z
Answers.Text: I will. I just don't want to mess with any plugins that already work. If I can extend them somehow with hooks, then that's the route I want to take.
Answers.UserDisplayName: Erik
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-18T04:58:06.100Z
Answers.LastActivityDate: 2016-06-18T04:58:06.100Z
Answers.UserDisplayName: Brad Bell
Answers.Body: <p>Not a Craft specific answer but you could use JS to prevent the form from submitting, and instead save those values in a cookie. After doing so, redirect the user to the review page, and use the cookie values to fill out a hidden form (all hidden except the submit/confirm button, of course).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-20T12:01:10.993Z
Answers.Text: That's not an option to be honest. Thanks.
Answers.UserDisplayName: Erik
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-18T19:19:23.167Z
Answers.LastActivityDate: 2016-06-18T19:19:23.167Z
Answers.UserDisplayName: Chase Giunta
Body: <p>With guest entries, am I able to redirect before actually saving the entry to say a review page for the user to see the entry?</p>
  
  <p>I figure I could use the <code>guestEntries.beforeSave</code> hook, but not sure how I'd show the information on the page... or pass to a template.</p>
  
  <p>Any suggestions?</p>
  
Tags: <guest-entries><plugin-guestentries>
Title: Before saving Guest Entries, redirect to an entry review page?
ThreadText: # Before saving Guest Entries, redirect to an entry review page?
  
  (Asked by: username_0 on 2016-06-15)
  
  With guest entries, am I able to redirect before actually saving the entry to say a review page for the user to see the entry?
  
  I figure I could use the `guestEntries.beforeSave` hook, but not sure how I'd show the information on the page... or pass to a template.
  
  Any suggestions?
  
  **Tags:** guest-entries, plugin-guestentries
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2016-06-18. Score: 1
  
  You can listen for the `beforeSave` event, but by redirecting or rendering another template, you're essentially hijacking the request and cancelling the initial save.
  
  You could fork the plugin and add some custom logic using a flag you can tell whether it's an initial save and to redirect, or it's a subsequent save and to continue processing as normal.
  
  > **Comments:**
  > **username_0**: That's an idea. Is there a way I can on entry save, send those values to another template to review? So, the entry would be saved like normal, then I'd just have a field that called "Finished" or something, and on the next page form submit, I'd update that entry if they finished the review process. I'd rather not fork the plugin and keep it's original functionality. Thanks.  
  > **username_1**: Yeah, you might be able to pull it off without forking... not 100% sure at the moment.  
  > **username_0**: I believe I have a way. I've created a custom plugin, I look for `guestEntries.success`. From there I redirect to a page with the entry id in the URL (hashed so you can't just put an ID in) and I will use my custom plugin to do all that and have a 'review' page. I'm not 100% this will work, I'm working my way through it today. I can detail it out later if anyone is interested.  
  > **username_1**: Ahh, yeah... forgot about that event.  If it ends up working out, you should definitely add your solution as an answer. :)  
  > **username_0**: I will. I just don't want to mess with any plugins that already work. If I can extend them somehow with hooks, then that's the route I want to take.  
  
  ---
  
  ### Answer by username_2 on 2016-06-18. Score: 1
  
  Not a Craft specific answer but you could use JS to prevent the form from submitting, and instead save those values in a cookie. After doing so, redirect the user to the review page, and use the cookie values to fill out a hidden form (all hidden except the submit/confirm button, of course).
  
  > **Comments:**
  > **username_0**: That's not an option to be honest. Thanks.  
  
  ---
  
  