Answers.Body: <p>You will need to comment out line 526 from /includes/civicrm.basepage.php</p>
  <pre><code>remove_filter('the_content', [$this, 'basepage_render']);
  </code></pre>
  <p>That should solve it.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-03T20:31:22.190Z
Answers.Text: Thanks a lot, Tommy! Commenting out that line and clearing WP and civi caches solved the problem.
Answers.UserDisplayName: AlainB
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-04T15:59:36.353Z
Answers.Text: @AlainB are you using Divi or Avada Theme?
Answers.UserDisplayName: Tommy B
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-04T19:02:02.623Z
Answers.Text: @TommyB  Are you finding this problematic on all sites or just those using themes like Avada and Divi?
Answers.UserDisplayName: Kevin Cristiano
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-04T19:33:47.793Z
Answers.Text: @KevinCristiano only Divi so far -- I only suspect avada --- This plugin looks like the long term solution https://github.com/phdccltd/civicrm-539-wp-content-fix
Answers.UserDisplayName: Tommy B
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-04T21:09:09.337Z
Answers.Text: @TommyB It seems that the guy who made the site used the Ken theme.
Answers.UserDisplayName: AlainB
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-05T20:57:44.320Z
Answers.Text: Thanks @TommyB  I am reluctant to have CiviCRM support all the cases that Page builders and themes put out there.  If needed a plugin would be preferable to us playing whack-a-mole on this.  Thanks for confirming where you've seen it.
Answers.UserDisplayName: Kevin Cristiano
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-17T09:19:52.290Z
Answers.Text: Thanks @TommyB for the solution
Answers.UserDisplayName: Renaud F
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-03T20:15:33.857Z
Answers.LastActivityDate: 2021-08-03T20:15:33.857Z
Answers.UserDisplayName: Tommy B
Body: <p>After upgrading Wordpress to 5.8 and CiviCRM to 5.39.0, the event registration page does not work.</p>
  <p>This is the url:</p>
  <ul>
  <li>MY-SITE/civicrm/?civiwp=CiviCRM&amp;q=civicrm%2Fevent%2Fregister&amp;reset=1&amp;id=120</li>
  </ul>
  <p>These are the symptoms:</p>
  <ul>
  <li>the h1 of the page is &quot;CiviCRM&quot;</li>
  <li>the body of the page is &quot;Do not delete this page. Page content is generated by CiviCRM.&quot;</li>
  <li>the title tag in the header contains the title of the event</li>
  <li>no profile fields, hence no possibility to register for the event.</li>
  <li>no errors in ConfigAndLog</li>
  <li>no javascript errors in browser web developer tools</li>
  <li>several cache clear had no effect</li>
  </ul>
  <p>What could be the cause of this error? What can I do to debug this further?</p>
  <p>Thanks!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-08-03T17:53:59.427Z
Comments.Text: I'd try flushing WP permalinks first.  Go to https://mysite.org/wp-admin/options-permalink.php   Just visiting the page should flush the permalinks.  No need to save anything.  If that fails, I'd delete the dirctories under `templates_c` to ensure the CiviCRM cache is fully cleared.
Comments.UserDisplayName: Kevin Cristiano
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-08-03T17:54:55.203Z
Comments.Text: One other thought:  is the base page set here:  https://mysite.org/wp-admin/admin.php?page=civi_options
Comments.UserDisplayName: Kevin Cristiano
Tags: <wordpress>
Title: Wordpress: how to debug "Do not delete this page. Page content is generated by CiviCRM."
ThreadText: # Wordpress: how to debug "Do not delete this page. Page content is generated by CiviCRM."
  
  (Asked by: username_0 on 2021-08-03)
  
  After upgrading Wordpress to 5.8 and CiviCRM to 5.39.0, the event registration page does not work.
  
  This is the url:
  
  * MY-SITE/civicrm/?civiwp=CiviCRM&q=civicrm%2Fevent%2Fregister&reset=1&id=120
  
  These are the symptoms:
  
  * the h1 of the page is "CiviCRM"
  * the body of the page is "Do not delete this page. Page content is generated by CiviCRM."
  * the title tag in the header contains the title of the event
  * no profile fields, hence no possibility to register for the event.
  * no errors in ConfigAndLog
  * no javascript errors in browser web developer tools
  * several cache clear had no effect
  
  What could be the cause of this error? What can I do to debug this further?
  
  Thanks!
  
  **Tags:** wordpress
  
  > **Comments:**
  > **username_1**: I'd try flushing WP permalinks first.  Go to https://mysite.org/wp-admin/options-permalink.php   Just visiting the page should flush the permalinks.  No need to save anything.  If that fails, I'd delete the dirctories under `templates_c` to ensure the CiviCRM cache is fully cleared.  
  > **username_1**: One other thought:  is the base page set here:  https://mysite.org/wp-admin/admin.php?page=civi_options  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2021-08-03. Score: 1 | Accepted answer
  
  You will need to comment out line 526 from /includes/civicrm.basepage.php
  
  ```
  remove_filter('the_content', [$this, 'basepage_render']);
  
  ```
  
  That should solve it.
  
  > **Comments:**
  > **username_0**: Thanks a lot, username_2! Commenting out that line and clearing WP and civi caches solved the problem.  
  > **username_2**: @username_0 are you using Divi or Avada Theme?  
  > **username_1**: @username_2  Are you finding this problematic on all sites or just those using themes like Avada and Divi?  
  > **username_2**: @username_1 only Divi so far -- I only suspect avada --- This plugin looks like the long term solution https://github.com/phdccltd/civicrm-539-wp-content-fix  
  > **username_0**: @username_2 It seems that the guy who made the site used the Ken theme.  
  > **username_1**: Thanks @username_2  I am reluctant to have CiviCRM support all the cases that Page builders and themes put out there.  If needed a plugin would be preferable to us playing whack-a-mole on this.  Thanks for confirming where you've seen it.  
  > **username_3**: Thanks @username_2 for the solution  
  
  ---
  
  