Body: <p>I'm currently using CiviCRM version 5.72.0 with WordPress 6.5.</p>
  <p>I've encountered an odd issue after upgrading from 5.71.2 to 5.72.0. When individuals attempt to register for an event, the initial page of the event registration screen appears correctly on the frontend of the website. However, both the &quot;confirmation&quot; and &quot;thank you for registration&quot; screens are now appearing from the website backend, which is not typical. As these screens are located in the website backend, WordPress prompts users to log in, resulting in many individuals being unable to register for our events since they are not members. Is anyone else experiencing this issue after upgrading to 5.72.0?</p>
  <p><strong>Update</strong></p>
  <p>I deleted the 5.72.0 codebase and replaced it 5.71.2 version, and now  both the &quot;confirmation&quot; and &quot;thank you for registration&quot; screens appear on the website frontend, allowing people to register for our events again.</p>
  <p>However, the CiviCRM system status now displays an &quot;unexpected database version&quot; error due to a mismatch between the database and files.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-04-06T15:22:02.757Z
Comments.Text: Yes it's a bug. See https://lab.civicrm.org/dev/core/-/issues/5127#note_162796
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-04-06T16:54:41.870Z
Comments.Text: @aaron a patch has been released: https://github.com/civicrm/civicrm-wordpress/pull/318.  If you know how to apply patches, you can upgrade to 5.72 with this.  Otherwise, 5.72.1 should be released pretty soon (this is a serious bug, I think it alone justifies releasing 5.72.1) and you can upgrade then.
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-04-07T08:57:28.417Z
Comments.Text: Thanks for working on it over the weekend.  I reinstalled version 5.72.0 and applied the patch.  This is to confirm that I'm not experiencing the issue again.
Comments.UserDisplayName: Aaron
Tags: <civievent>
Title: CiviEvent: "Confirmation" and "Thank You" screen displayed in website backend after upgrading to 5.72.0
ThreadText: # CiviEvent: "Confirmation" and "Thank You" screen displayed in website backend after upgrading to 5.72.0
  
  (Asked by: username_0 on 2024-04-06)
  
  I'm currently using CiviCRM version 5.72.0 with WordPress 6.5.
  
  I've encountered an odd issue after upgrading from 5.71.2 to 5.72.0. When individuals attempt to register for an event, the initial page of the event registration screen appears correctly on the frontend of the website. However, both the "confirmation" and "thank you for registration" screens are now appearing from the website backend, which is not typical. As these screens are located in the website backend, WordPress prompts users to log in, resulting in many individuals being unable to register for our events since they are not members. Is anyone else experiencing this issue after upgrading to 5.72.0?
  
  **Update**
  
  I deleted the 5.72.0 codebase and replaced it 5.71.2 version, and now both the "confirmation" and "thank you for registration" screens appear on the website frontend, allowing people to register for our events again.
  
  However, the CiviCRM system status now displays an "unexpected database version" error due to a mismatch between the database and files.
  
  **Tags:** civievent
  
  > **Comments:**
  > **username_1**: Yes it's a bug. See https://lab.civicrm.org/dev/core/-/issues/5127#note_162796  
  > **username_2**: @aaron a patch has been released: https://github.com/civicrm/civicrm-wordpress/pull/318.  If you know how to apply patches, you can upgrade to 5.72 with this.  Otherwise, 5.72.1 should be released pretty soon (this is a serious bug, I think it alone justifies releasing 5.72.1) and you can upgrade then.  
  > **username_0**: Thanks for working on it over the weekend.  I reinstalled version 5.72.0 and applied the patch.  This is to confirm that I'm not experiencing the issue again.  
  
  ---
  
  ## 0 answers
  
  