Answers.Body: <p>The newer Civicrm Version had posed many issues for me. Also it does not work properly with PHP 7.3. Eventually I have resorted to stick with civi 5.8 which i have used in 2 other sites and working properly. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-02T18:32:02.717Z
Answers.Text: One other thing. Turning off all plugins and using the stock "2019" Wordpress theme, all is good. However, just changing the theme to Benevelant PRO breaks it. From my previous comment, keeping all plugins active and changing theme to stock 2019, still was broken, so there evidently is a plugin conflict as well. I will try to figure it out. The CiviCRM developers need to know they really should do something. Our paid theme and plugins are used worldwide, so it seems like this is a CiviCRM core issue.
Answers.UserDisplayName: Karl Rudnick
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-03T07:01:50.160Z
Answers.Text: And I narrowed the plugin conflict to just one plugin, "iframe"  (https://wordpress.org/plugins/iframe/)
Answers.UserDisplayName: Karl Rudnick
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-02T04:21:24.940Z
Answers.LastActivityDate: 2019-10-02T04:21:24.940Z
Answers.UserDisplayName: sri
Answers.Body: <p>Just seeing activity here, I realized I moved this query to chat.civicrm.org, Wordpress channel and haystack provided a general fix to civicrm core which has been in place since late fall 2019. I forgot to close things out back here on StackExchange. The ultimate problem was not that one plugin, iframe, but our theme, Benevolent Pro, was evidently calling register_hooks_front_end() before it actually should be. It was decided that could happen with other themes as well, so haystack suggested a fix to handle that case. I haven't had any problems since then. We are running Civi 5.21.3 (ESR) and Wordpress 5.4.2 currently. You can see the whole thread at:</p>
  <p><a href="https://chat.civicrm.org/civicrm/pl/9we4awu1c38b98eihypwdrbumh" rel="nofollow noreferrer">https://chat.civicrm.org/civicrm/pl/9we4awu1c38b98eihypwdrbumh</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-30T21:45:39.860Z
Answers.Text: good on you for updating. i will remove my answer :-)
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-01T01:19:37.817Z
Answers.Text: I also meant to mention that Haystack's "fix" was not just for me, but it has been in CiviCRM core since 5.18 or 5.19. Protects against sloppy 3rd party theme development.
Answers.UserDisplayName: Karl Rudnick
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-30T07:57:30.477Z
Answers.LastActivityDate: 2020-06-30T07:57:30.477Z
Answers.UserDisplayName: Karl Rudnick
Body: <p>We have been stuck at CiviCRM 5.12.4 for months now. I have had issues with my Contribution page (details not needed here) as I tried to upgrade through Civi 5.14.2. So, I held off until today to try one more time on the latest stable release (also to avoid the critical warning that 5.12.4 is OBE that scares our staff).</p>
  
  <p>We are running WordPress 5.2.3 and use iATS Payments 1.6.2. </p>
  
  <p>This is the behavior. If I am logged into Wordpress, when I click on a contribution page, both the contact info and the billing name and address are correctly filled in. However, hardly any of our visitors create and use a WordPress login. If I am not logged in, the page does NOT have the "My billing address is the same as above" checked by default as it did before. Worse yet, if I check to use the same address for billing as for contact, it does not propagate. Someone would have to fill in every field all over again. I think this "almost" works, but am wondering what could possibly be wrong. It seems like an issue with the handler for contribution pages, as the behavior seems to change every time I try a new version.</p>
  
  <p>I obviously am not going live on our main website with this behavior. If anyone would like to observe for themselves, please visit <a href="https://test.sdcbcdream.org/join/" rel="nofollow noreferrer">https://test.sdcbcdream.org/join/</a> . To see it work correctly (5.12.4), you may visit <a href="https://sdbikecoalition.org/join/" rel="nofollow noreferrer">https://sdbikecoalition.org/join/</a>. </p>
  
  <p>Thanks for any help. This one has me stumped as we have always had no issues moving forward with stable versions.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-28T22:01:10.307Z
Comments.Text: I hate to add, but even if all the info is filled out properly, it no longer goes to the page to confirm and then click "Make Contribution." The form is completely blanked out. That same behavior ALSO occurred attempting to upgrade through 5.13 and 5.14 versions. Is this possibly an issue with the iATS payment processor extension?
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-28T22:06:24.903Z
Comments.Text: One other issue is that we also have the option to simply send in a check. On our live site running Civi 5.12.4, when you check that all the credit card and billing fields dissappear and when you click Confirm Contribution, you are presented with the info where to send the check. With Civi 5.17.5, if you click on Send Payment by Check, all the credit card and billing fields remain. ???
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-30T16:39:28.077Z
Comments.Text: I've seen issues like this when there are javascript conflicts with the theme. Have you looked in the browser console to see if any error messages are showing up?
Comments.UserDisplayName: guyiac
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-30T19:37:33.273Z
Comments.Text: @guyiac, that is a good suggestion as I was wondering the same, as we upgraded to a new paid and supported them about a year ago. However, I switched to one of the standard Wordpress themes, "2019" in particular, with identical behavior. I find it hard to believe it is the them specifically. I suppose, CiviCRM 5.13.x and above has a weird conflict with the later Wordpress versions (I first encountered difficult with WP 5.1 I believe). Where do I look in the browser console for javascript errors? I've never done that. I run Chrome. THANKS for the suggestions.
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-30T22:55:55.237Z
Comments.Text: OK - ctrl-shift-J brings up the javascript console. Indeed there are errors. Among them, GET https://test.sdcbcdream.org/wp-content/uploads/elementor/css/global.css?ver=1569583742 net::ERR_ABORTED 404 (Not Found)
  (index):68 GET https://test.sdcbcdream.org/wp-content/uploads/elementor/css/post-4657.css?ver=1569589620 net::ERR_ABORTED 404 (Not Found). One of our admins installed a Wordpress extension, Elementor, for block editing (easier for non-tech staff). It looks like that may be what is getting in the way somehow. I'll dig into that. Anyone else have any suggestions?
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-30T23:09:25.460Z
Comments.Text: I deactivated the elementor plugin .... but when I click on "Confirm Contribution", a specific error that I clicked on had this statement in error [        // add validation rules
          CRM.validate.functions.push(function(){
            $('#selectProduct').rules('add', 'premiums');] This one contribution page does indeed have premiums and they've always worked. The whole thing seems to be a mess and don't know where to begin.
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-30T23:18:07.140Z
Comments.Text: On our working site, sdbikecoalition.org/join, there are only 2 warning JS messages. (1)[DOM] Found 3 elements with non-unique id #user_login; (2)[DOM] Found 3 elements with non-unique id #wp-submit. The exact same page test.sdcbcdream.org/join has real errors.
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-30T23:31:29.700Z
Comments.Text: And even Event links are not working such as: https://test.sdcbcdream.org/civicrm/?page=CiviCRM&q=civicrm/event/info&reset=1&id=172 and NO javascript console errors appear. The event page is simply not shown. Contrast that with https://sdbikecoalition.org/civicrm/?page=CiviCRM&q=civicrm/event/info&reset=1&id=172. Are we looking at a Wordpress version / CiviCRM version compatibility issue here?
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-10-01T03:41:25.253Z
Comments.Text: Maybe at this point see if you can reproduce on wpmaster.demo.civicrm.org which is 5.2.3, and if not, head to chat.civicrm.org in the wordpress channel.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-10-01T08:26:21.590Z
Comments.Text: Thanks for that suggestion. I created a contribution page at wpmaster.demo.civicrm.org and all "appeared" to work. Didn't have the patience to try an event as well, as I guess something is corrupt, probably the database, although possibly something buried in wp-content/uploads/civicrm which is not really touched during the upgrade except civicrm.settings.php. Anyone have a good idea what to test? Should I completely clear out CiviCRM in my test mirror, reinstall CiviCRM from scratch and either import my whole 5.17.5 database or just certain tables. Any database integrity tools?
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-10-01T15:06:09.140Z
Comments.Text: I also posted a short note on https://chat.civicrm.org pointing to this thread.
Comments.UserDisplayName: Karl Rudnick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-10-01T16:41:59.970Z
Comments.Text: I do believe this is just a plugin conflict. Turning off all plugins, 5.17.5 works, so I'll just work through adding one at a time until I solve this. I'll post that as an answer as I'm sure it will get to the root problem.
Comments.UserDisplayName: Karl Rudnick
Tags: <wordpress><civicontribute><iats>
Title: CiviCRM 5.17.5 and WordPress 5.2.3 just won't work
ThreadText: # CiviCRM 5.17.5 and WordPress 5.2.3 just won't work
  
  (Asked by: username_0 on 2019-09-28)
  
  We have been stuck at CiviCRM 5.12.4 for months now. I have had issues with my Contribution page (details not needed here) as I tried to upgrade through Civi 5.14.2. So, I held off until today to try one more time on the latest stable release (also to avoid the critical warning that 5.12.4 is OBE that scares our staff).
  
  We are running WordPress 5.2.3 and use iATS Payments 1.6.2.
  
  This is the behavior. If I am logged into Wordpress, when I click on a contribution page, both the contact info and the billing name and address are correctly filled in. However, hardly any of our visitors create and use a WordPress login. If I am not logged in, the page does NOT have the "My billing address is the same as above" checked by default as it did before. Worse yet, if I check to use the same address for billing as for contact, it does not propagate. Someone would have to fill in every field all over again. I think this "almost" works, but am wondering what could possibly be wrong. It seems like an issue with the handler for contribution pages, as the behavior seems to change every time I try a new version.
  
  I obviously am not going live on our main website with this behavior. If anyone would like to observe for themselves, please visit <https://test.sdcbcdream.org/join/> . To see it work correctly (5.12.4), you may visit <https://sdbikecoalition.org/join/>.
  
  Thanks for any help. This one has me stumped as we have always had no issues moving forward with stable versions.
  
  **Tags:** wordpress, civicontribute, iats
  
  > **Comments:**
  > **username_0**: I hate to add, but even if all the info is filled out properly, it no longer goes to the page to confirm and then click "Make Contribution." The form is completely blanked out. That same behavior ALSO occurred attempting to upgrade through 5.13 and 5.14 versions. Is this possibly an issue with the iATS payment processor extension?  
  > **username_0**: One other issue is that we also have the option to simply send in a check. On our live site running Civi 5.12.4, when you check that all the credit card and billing fields dissappear and when you click Confirm Contribution, you are presented with the info where to send the check. With Civi 5.17.5, if you click on Send Payment by Check, all the credit card and billing fields remain. ???  
  > **username_1**: I've seen issues like this when there are javascript conflicts with the theme. Have you looked in the browser console to see if any error messages are showing up?  
  > **username_0**: @username_1, that is a good suggestion as I was wondering the same, as we upgraded to a new paid and supported them about a year ago. However, I switched to one of the standard Wordpress themes, "2019" in particular, with identical behavior. I find it hard to believe it is the them specifically. I suppose, CiviCRM 5.13.x and above has a weird conflict with the later Wordpress versions (I first encountered difficult with WP 5.1 I believe). Where do I look in the browser console for javascript errors? I've never done that. I run Chrome. THANKS for the suggestions.  
  > **username_0**: OK - ctrl-shift-J brings up the javascript console. Indeed there are errors. Among them, GET https://test.sdcbcdream.org/wp-content/uploads/elementor/css/global.css?ver=1569583742 net::ERR_ABORTED 404 (Not Found) (index):68 GET https://test.sdcbcdream.org/wp-content/uploads/elementor/css/post-4657.css?ver=1569589620 net::ERR_ABORTED 404 (Not Found). One of our admins installed a Wordpress extension, Elementor, for block editing (easier for non-tech staff). It looks like that may be what is getting in the way somehow. I'll dig into that. Anyone else have any suggestions?  
  > **username_0**: I deactivated the elementor plugin .... but when I click on "Confirm Contribution", a specific error that I clicked on had this statement in error [        // add validation rules         CRM.validate.functions.push(function(){           $('#selectProduct').rules('add', 'premiums');] This one contribution page does indeed have premiums and they've always worked. The whole thing seems to be a mess and don't know where to begin.  
  > **username_0**: On our working site, sdbikecoalition.org/join, there are only 2 warning JS messages. (1)[DOM] Found 3 elements with non-unique id #user_login; (2)[DOM] Found 3 elements with non-unique id #wp-submit. The exact same page test.sdcbcdream.org/join has real errors.  
  > **username_0**: And even Event links are not working such as: https://test.sdcbcdream.org/civicrm/?page=CiviCRM&q=civicrm/event/info&reset=1&id=172 and NO javascript console errors appear. The event page is simply not shown. Contrast that with https://sdbikecoalition.org/civicrm/?page=CiviCRM&q=civicrm/event/info&reset=1&id=172. Are we looking at a Wordpress version / CiviCRM version compatibility issue here?  
  > **username_2**: Maybe at this point see if you can reproduce on wpmaster.demo.civicrm.org which is 5.2.3, and if not, head to chat.civicrm.org in the wordpress channel.  
  > **username_0**: Thanks for that suggestion. I created a contribution page at wpmaster.demo.civicrm.org and all "appeared" to work. Didn't have the patience to try an event as well, as I guess something is corrupt, probably the database, although possibly something buried in wp-content/uploads/civicrm which is not really touched during the upgrade except civicrm.settings.php. Anyone have a good idea what to test? Should I completely clear out CiviCRM in my test mirror, reinstall CiviCRM from scratch and either import my whole 5.17.5 database or just certain tables. Any database integrity tools?  
  > **username_0**: I also posted a short note on https://chat.civicrm.org pointing to this thread.  
  > **username_0**: I do believe this is just a plugin conflict. Turning off all plugins, 5.17.5 works, so I'll just work through adding one at a time until I solve this. I'll post that as an answer as I'm sure it will get to the root problem.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2020-06-30. Score: 3 | Accepted answer
  
  Just seeing activity here, I realized I moved this query to chat.civicrm.org, Wordpress channel and haystack provided a general fix to civicrm core which has been in place since late fall 2019. I forgot to close things out back here on StackExchange. The ultimate problem was not that one plugin, iframe, but our theme, Benevolent Pro, was evidently calling register\_hooks\_front\_end() before it actually should be. It was decided that could happen with other themes as well, so haystack suggested a fix to handle that case. I haven't had any problems since then. We are running Civi 5.21.3 (ESR) and Wordpress 5.4.2 currently. You can see the whole thread at:
  
  <https://chat.civicrm.org/civicrm/pl/9we4awu1c38b98eihypwdrbumh>
  
  > **Comments:**
  > **username_4**: good on you for updating. i will remove my answer :-)  
  > **username_0**: I also meant to mention that Haystack's "fix" was not just for me, but it has been in CiviCRM core since 5.18 or 5.19. Protects against sloppy 3rd party theme development.  
  
  ---
  
  ### Answer by username_3 on 2019-10-02. Score: 0
  
  The newer Civicrm Version had posed many issues for me. Also it does not work properly with PHP 7.3. Eventually I have resorted to stick with civi 5.8 which i have used in 2 other sites and working properly.
  
  > **Comments:**
  > **username_0**: One other thing. Turning off all plugins and using the stock "2019" Wordpress theme, all is good. However, just changing the theme to Benevelant PRO breaks it. From my previous comment, keeping all plugins active and changing theme to stock 2019, still was broken, so there evidently is a plugin conflict as well. I will try to figure it out. The CiviCRM developers need to know they really should do something. Our paid theme and plugins are used worldwide, so it seems like this is a CiviCRM core issue.  
  > **username_0**: And I narrowed the plugin conflict to just one plugin, "iframe"  (https://wordpress.org/plugins/iframe/)  
  
  ---
  
  