2

The solution was to make sure the Civi scripts loaded on the page. This answer provides guidance on how to do that.


1

The problem may have had to do with SSL certificates. Callback was using a HTTPS POST callback URL but no SSL certificate was in place. After switching the callback URL to HTTP POST, we are now receiving inbound texts. We are still getting Schema Validation Required responses. Will post again if having an SSL cert makes those go away.


1

I stumbled across a work around purely by accident but to cut a long story short: Problem is that since the upgrade database url points to an unsecure http file, my server then wants to redirect to the secure url - resetting the session - requiring an admin login (not sure why this is since automatic SSL redirects have been disabled). Using the upgrade url, ...


1

It is indeed a confirmed bug in CiviCRM 5.34 which is now tracked under the following issue: https://lab.civicrm.org/dev/wordpress/-/issues/94


1

It sounds like you're running PHP 7.2 or greater with a version of CiviCRM that doesn't support PHP 7.2+. If you edit your question to include your CiviCRM version, that could help folks troubleshoot. However, it sounds like you may need to upgrade your CiviCRM to a version that supports 7.2.


1

You could use JetPack or another widget visibility plugin to prevent showing the page in the footer when you're on the CiviCRM Base Page. EDIT: The following code prevents CiviCRM from overriding the content a second time: add_action( 'civicrm_basepage_parsed', 'my_civicrm_disable_content_filter' ); function my_civicrm_disable_content_filter() { // Once ...


1

As others point out, there are no clear answers. The number of simultaneous users is also an important factor. But here are some tips from my administration of a similarly-sized database: I run everything on a 4GB server. This is usually sufficient, but when my client had a very high-traffic event, I saw some monitoring warnings (though I couldn't detect ...


1

The registration part is quite straight forward and described in the manual at https://docs.civicrm.org/user/en/latest/organising-your-data/profiles/#wordpress-user-account-registration-option. The profile allows you to collect additional information and populate existing or custom fields. The login and forgotten password screens are WordPress pages so you ...


1

The correct endpoint for WordPress is wp-json/civicrm/v3/rest. Its documented in the developer manual, see https://docs.civicrm.org/dev/en/latest/api/v3/wp-rest/#endpoints. When you just copy the URL that is suggested in the API explorer you are left in the dark.


Only top voted, non community-wiki answers of a minimum length are eligible