2

This extension may be of interest, but it doesn't allow sending via API: https://github.com/mecachisenros/aws I think you would need to write your own code to integrate with the SES API. But AWS works perfectly fine via SMTP.


2

Also for me (in addition to directory permissions) is the fact that some distributions use different names for their docroot directory. Core uses ./web Varbase uses ./docroot OpenSocial uses ./html This can be accounted for if you add this to the composer.json in the extras section "civicrm-asset": { "path": "***docroot***/...


1

I checked and that function definitely does exist. The first things I would try are: Ensure you are using the search_kit extension in core (in the civicrm/ext/search_kit directory). Delete any others e.g. in your site's extension directory, or in civicrm/ext/search which is the old path before the extension was renamed). Clear all caches.


1

Depending on what exactly you need to accomplish, you can get a similar function from the proximity search in civi under Search - Custom Searches - Proximity Search. If you haven't already you'll need to set up geocoding/mapping in core: https://{your-site}/civicrm/admin/setting/mapping?reset=1


1

I have upgraded the extension 1.6.2 to 1.7.4. During upgraded extension upgrade function were not ruined upgrade_1_7_002 and upgrade_1_7_003. After manually run the SQL Queries issue is resolved.


1

I had something similar on a Backdrop site and it turned out to be caused by the way I had set up the directory structure. I was trying to get fancy using a symlink and the server was using the symlink as the website's document root, but in the civicrm.settings.php I was pointing to the other directory. Changing the settings file to also point to the symlink ...


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