4
This is a known issue with all scripts in CiviCRM's extern directory - pointing directly to a PHP script inside wp-content is considered highly likely to be malicious. This will be solved out-of-the-box once the CiviCRM WP REST API Wrapper is merged into the CiviCRM WordPress plugin, but for now you probably need to install that and follow the instructions ...
4
Do not worry, the Health Check loopbacks and REST API checks are inaccurate. Nothing is actually wrong. You can install Disable Health Check.
4
You can embed the Drupal site's form (any form, whether from Civi or Drupal) into your wordpress site using an iframe.
Here's an example of exactly that:
https://patientscanada.ca/donate/
There are three steps to make this work:
Create an alternative theme on the Drupal site that is suitable for embedding in an iframe. There's a Drupal theme here: https://...
3
It sounds like you don't want to use CiviCRM public pages because it would visually take people away from your main website.
An option could be to theme your CiviCRM public pages so that this transition is absolutely seamless -> here's an example of a CiviCRM public page we're drafting at the moment (with iATS Payments processor but that's not the point) - ...
3
In case it helps anyone, this is what I did:
Initial set-up:
- a working Joomla site, with Civicrm and Joomla tables in the same database
- a separate installation of Wordpress on the same server (articles and static content already imported from the Joomla site and redirects set up as required)
Aim: migrate the Joomla Civicrm tables and data to the ...
2
I encountered this bug myself last week and fixed it; I forgot about this post until @herb posted a comment on it.
The fix will be in CiviCRM 5.25+, but the bug is logged as https://lab.civicrm.org/dev/financial/issues/119, and the fix is incredibly simple to apply.
2
Based on comments, it sounds like you have a permission issue. It's possible you have an ACL issue, but it's pretty unlikely; you would know if you set up ACLs.
Go to Administer menu » Users and Permissions » Permissions (Access Control).
Click the WordPress Access Control link.
Check the permissions: CiviCRM: profile create and CiviCRM: profile view and ...
2
Based on Mr. Burns' comforting response above, and Mr. Earnhardt's instruction on how to selectively remove tests, I added the following code to the functions.php file in my WordPress theme:
function prefix_remove_rest_availability( $tests ) {
unset( $tests['direct']['rest_availability'] );
return $tests;
}
add_filter( 'site_status_tests', '...
1
This is a regression bug since 5.22.1. Just submitted PR to core, can you please try upgrading after applying patch? If the patch works it would be helpful to add your QA results on PR to help the PR to get merged in next release.
Thanks
Pradeep
1
Turns out the issue was with captcha on our site. The plugin Captcha by BestWebSoft and all other captcha's that I have tested, including Wordfence captcha cause cron error. I found a captcha plugin that allowed me to restrict registration but not login pages in the mean time.
1
Try clearing your CiviCRM cache CiviCRM >> Administer >> System Settings >> Cleanup Caches and Update Paths.
Check if the Support menu is enabled in CiviCRM >> Administer >> Customize Data and Screens >> Navigation Menu
The api3 explorer link is
/wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fapi3#explorer
1
Couple of observations:
You may need to double-check that you can reach your MySQL database, since CiviCRM apparently can't (it's confusing since it reports that it can't connect, yet various operations can be done)
Your MySQL user needs to be able to create triggers. You probably need to contact your host to request this capability.
1
There's an example of how to do the second part of this in the integration module's README.
Checksum support to auto-populate form with URLs like example.com/some-page?cid={contact.contact_id}&{contact.checksum}
The part I'm not aware of is how to properly redirect from one form to a second form with the right contact ID and checksum. I don't have ...
1
The problem was WP Bakery and how it hijacks the page; getting rid of WP Bakery for a simpler page editor was the solution.
1
Are you by any chance using a caching plugin or extension? We had this error on event registrations and had to exclude the event pages from being cached. That resolved the issue.
Only top voted, non community-wiki answers of a minimum length are eligible
