Its a hidden setting and can be set in below ways
Add below line in civicrm.settings.php
$civicrm_setting['Mailing Preferences']['simple_mail_limit'] = '100';
Via drush or cv
cv api Setting.create simple_mail_limit=100
drush cvapi Setting.create simple_mail_limit=60
SET value = '100'
WHERE name = 'simple_mail_limit';
I feel this is very difficult to have it as part of Civi tar ball because there are many things we need to consider and come up with generalised solution. eg Algorithm to set start/end date when copying an event. How many org want this to change.
Instead i would just create an extension that would provide an option(pop-up) to set start date and end date (...
If your event has more than 50 participants, then you could install the 'Transactional Email' extension, (nz.co.fuzion.transactional), which allows you to send emails using CiviMail to search results. We use this for many purposes.
It has really helped us to be able to send an email to event participants/members, using the full capabilities of CiviMail - ...
Set default via Administer -> Localisation -> Date Formats
Date Format: Time Only
Events use the activityDateTime, which can be adjusted here:
Administer -> Customise Data and Screens -> Date Preferences
Late to the party here, I know - but we ended up writing code to extend the report to add a "Registered by Contact Name" column to the output here.
Happy to share this code if it's still useful.
Some of the forms on Civicrm won't allow me to access dropdown menus. The menus are greyed out. I thought this was a browser issue as it happens only on Firefox and Chrome, but not on MS Edge. It is caused by the Dashlane password extension. I started Firefox in safe mode, with extensions disabled. The issue goes away. I have removed Dashlane from Firefox ...
It takes some manual work, but for some important Civi links and events etc., I've just been putting them in my .htaccess file in root of my linux/Apache setup. Here's an example.
Redirect 301 /contribute https://watershedmg.org/civicrm/contribute/transact?reset=1&id=5
Redirect 301 /Contribute https://watershedmg.org/civicrm/contribute/transact?reset=1&...
this issue is resolved since upgrading from civicrm 5.26 to civicrm 5.28 AND upgrading the omnipay multiprocessor plugin to 3.13. Without upgrading the plugin, the white screen still showed up. Now it is all perfect again.