4

Another option if you are using civicrm v4.6 or higher would be to use the date of the activity type "Membership Signup" to trigger a 'reminder'.


4

When a membership is created there is both a 'join date' (member since) and a 'start date' You should be able to set up a scheduled reminder to be triggered based on the 'join date' and you should get what you need.


4

It seems that there is a bug in CiviCRM 4.7, 4.7.1 and 4.7.2 which causes these symptoms (scheduled mailing stuck at "running" without actually sending, but will send using Execute Now). See here and here. I spent a day trying to find the problem before I came across the bug report, so hopefully this will save others some time looking for a misconfiguration ...


4

This is a problem that's popped up and been squashed a few times - it's a little trickier to fix than it seems. The current conversation about it is on Gitlab but CRM-17671 provides some historical perspective. Your best short-term solution is probably Xavier's answer on a very similar question.


3

The most likely causes for breakage with this change are: Cron job is pointing to HTTP only curl by default will not follow 302 redirects, while wget will. If you're using curl, it won't work automatically when pointed to the non-SSL URL (not without -L, anyway). The 302 redirect can make this less obvious, since everything else that points to http "just ...


3

I think the reminders portion of the memberships has migrated to "Scheduled Reminders" but I believe the status update portion remains in the "Scheduled Jobs" area. Once you get to 4.7 that warning about reminders is gone:


3

This error does show up in Civi 4.7.8 on Drupal 7.x. @PeteRoss Thanks. Haven't had chance to upgrade to 4.7.9 yet. Had to send scheduled event SMS to members, so modified sql in if statement in CRM/Mailing/BAO/MailingJob.php 525 if ($mailing->sms_provider_id) { .... .... 546 OR contact_a.do_not_sms = 0 ) - 547 ...


3

Check how long it takes to run on your system. if it doesn't take too long, I don't see any reason not to run it hourly.


3

At Administer > CiviMail > Mail Accounts (civicrm/admin/mailSettings) you want to see two accounts configured, one for Bounce processing and one for Activity processing It's possible what you're describing is what happens when there is no account configured for activity processing. If so, the error message is a bit misleading, but I suspect that's what you'...


3

Problem a result of a reminder that has no sending date. (see attached image) This error results in a syntax error that prevents all subsequent reminders from being sent. Solution is to add date or disable reminder with no date. (ConfigAndLog error messages show the ID for the reminder that has the error.) Will report as a bug with recommendation that ...


3

Do you have a cron job configured for CiviCRM that runs periodically? Can you check CiviCRM and/or Apache Error log for any errors? Scheduled Mailing jobs are executed in batches of 1000 or the batch limit specified under Administer >> CiviMail >> Mailer Settings. If the recent Schedule job log says 'Started' then the last job was terminated because of ...


3

We found that applying this line's change from this PR to the mosaico extension solved our problem: https://github.com/veda-consulting/uk.co.vedaconsulting.mosaico/pull/182/files#diff-d8205fe762b98a885815f3d4bb175886R294


3

First, you can view the error with greater detail if you enable "Debug and Backtrace", or view the CiviCRM log. The troubleshooting documentation will tell you how to do both. Second, I would assume that "connect failed" is a MySQL error. Is it possible that you have two civicrm.settings.php files in your path, one with the wrong MySQL password? Finally -...


3

Ok so this may seem like a silly issue to some but after some messing around I figured out cron didn't have access to the path where CV was installed so to fix it the crontab entry had to be changed to: */5 * * * * /usr/local/bin/cv api job.execute --user=admin --cwd=/var/www/html/siteroot There was no error as the mailer deamon was not firing correctly so ...


3

Rules run by delayed action should be in the civicrm_queue_item table. Please be sure not to delete any other rows that may be in there!


2

Sorry - we've not seen this (yet) - best to post an issue on our GitHub queue: https://github.com/iATSPayments/com.iatspayments.civicrm - so that both Alan and myself as well as iATS staff sees this. Perhaps the automatic ones are not run as -u your webuser but as another user - different env - different drush? My favourite/most stable/like clockwork (no ...


2

Your symptoms suggest that the issue is some kind of fatal error happening during the job execution itself. I'd recommend you run the job directly via the command line, i.e. something like drush -u 1 cvapi job.iatsverify And see if there are any errors showing up. Make sure it's the same php version ... My guess is some curious error that our code isn't ...


2

Yes, you can send a report as printer-friendly HTML, in the body of a Scheduled Job e-mail, using mail_report. Go to Administer -> System Settings -> Scheduled Jobs. Edit the Scheduled Job parameters to add format=print, which overrides the default option, which is to send the report as a PDF file attached to the e-mail. See here for more information ...


2

The "Disable expired relationships" scheduled job should set the is_active field to 0 for relationships with a past end date. A bit of history: Civi has always treated both past and disabled relationships as "inactive" however there were inconsistencies in some of the code (reports maybe) that were not doing so. I believe Fuzion contributed the ...


2

This is what I have: (I know you can read it :-) And in my code: function civicrm_api3_note_Migrate($params) { // param migrate_type determines what will be selected, defaulted to contact $validTypes = array('contact', 'contribution', 'participant', 'relationship'); if (!isset($params['migrate_type'])) { $entityTable = 'civicrm_contact'; } ...


2

The run_time field is set to current timestamp by default and its a not null field which mean that run_time will never NULL values. Can you please check you schema for civicrm_job_log. I am pasting below for CiviCRM version 4.7.29 mysql> DESCRIBE `civicrm_job_log`; +-------------+------------------+------+-----+-------------------+------------------------...


2

We are having this problem as well, also in WordPress 4.9.2. We have discovered that the issue arises because permissions get corrupted. According to SiteGround, our host, these permissions in particular are problematic: ./wp-content/uploads/civicrm/templates_c/en_US/%%31/313 ./wp-content/uploads/civicrm/templates_c/en_US/%%D6/D67 We don't know what is ...


2

I assume you mean the job that is used to send Scheduled Mailings . You do not have to create it. It is part of the standard configuration. So the only thing to do is to enable it. But to be complete here is the configuration:


2

I was also going to add that there are alternatives, e.g. CiviHosting offer this method which can be done via the hosting control panel https://civihosting.com/blog/how-to-make-a-cron-job-for-civicrm/ And then you can also use an extension to use the Drupal cron to trigger the CiviCRM cron: https://civicrm.org/extensions/civicrm-cron Not quite as ...


2

And after all that, it looks like it was a password error after all, just not the password I thought. cli.php is retrieving the Drupal MySQL username and password from CIVICRM_UF_DSN in civicrm.settings.php as Jon G suggested. The instructions in that file say 'If any of these contain a single quote or backslash, escape those characters with a backslash: \' ...


2

Harshal, Check the resource url is set properly. Navigate to CiviCRM >> Administer >> System Settings >> Resource URLS. Click on '?' to see if all the variables have correct values and are pointing to right directories. If not then you may need to update the civicrm.settings.php file for $civicrm_root variable until the you get th variables right in ...


2

One of the scheduled job parameters is "format". See https://docs.civicrm.org/user/en/latest/initial-set-up/scheduled-jobs/#job_mail_report


2

As suggested by Demerit you can use alterMailParams to abort the email if the report has 0 rows. It will work on simple use case but would be difficult or need to add more logic you passing any additional parameters when running cron job or through url to filter the result since the ReportTemplate.getrows api will return the results which is saved in the ...


2

This question is now resolved. It is not a bug, but a server misconfiguration. I am adding the resolution here for posterity. It turns out the issue was caused by the server being set to Europe/Berlin, but PHP-FPM defaulting to UTC. Setting PHP-FPM to Europe/Berlin through its configuration file solved the issue.


2

The email body content starts here for csv: https://github.com/civicrm/civicrm-core/blob/5.18.4/CRM/Report/Form.php#L3413, and a bit lower down for pdf. Note also the attachments are hardcoded in, a couple lines lower down. Note that in the report itself on the Title and Format tab you can add some text/html at the end of the header which will get included ...


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