CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • Possible bug with conflicting Civimember cron jobs
Pages: [1]

Author Topic: Possible bug with conflicting Civimember cron jobs  (Read 924 times)

narayanis

  • I post occasionally
  • **
  • Posts: 56
  • Karma: 2
Possible bug with conflicting Civimember cron jobs
July 24, 2011, 08:58:09 am
We had a patron who was approaching her membership expiration date. Reminders are set to go out 10 days in advance of expiration. However, she has received a reminder every day since reaching that 10-day threshold, so something doesn't seem to be resetting properly. We use Civi 3.4.4 and Drupal 6.22. The activity tab shows her getting the email at 00:15 every day.

UpdateMembershipRecord.php runs daily at 00:15
UpdateMembershipReminderDate.php runs daily at 23:50

It looks like UpdateMembershipRecord.php finds all records that have a non-NULL reminder date, sends the reminder if needed and then sets the reminder date to NULL. However, UpdateMembershipReminderDate.php looks specifically for memberships with a reminder date of NULL and then sets a reminder date. This seems like the two scripts are at odds with each other and cause an endless loop of reminders. Am I misunderstanding something?
« Last Edit: July 26, 2011, 12:08:54 pm by narayanis »

davej

  • Ask me questions
  • ****
  • Posts: 404
  • Karma: 21
Re: Possible bug with conflicting Civimember cron jobs
August 03, 2011, 06:22:02 am
Hi,

I've just been looking into UpdateMembershipReminderDate.php and found this issue:

http://issues.civicrm.org/jira/browse/CRM-7531

and a brief mention on IRC here:

http://irc.civicrm.org/logs/%23civicrm.log.2011-02-17.txt

I would think that UpdateMembershipReminderDate.php is intended to be run only as a one-off when renewal reminders are set up for an existing membership type. In this case the existing memberships would AFAIK not have a reminder date set and I think the script's purpose is to fix that. So my impression is that it shouldn't be run under cron.

Dave J

narayanis

  • I post occasionally
  • **
  • Posts: 56
  • Karma: 2
Re: Possible bug with conflicting Civimember cron jobs
August 03, 2011, 07:15:01 am
That makes sense when reading through the code on each of these jobs. There is no info in the documentation or in the files themselves about this, so would it be worth filing a bug so no one else runs into the same issue I did?
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • Possible bug with conflicting Civimember cron jobs

This forum was archived on 2017-11-26.