CiviCRM Community Forums (archive)

Most times, but not always, when we renew memberships or record new contributions in a contact file, the system generates a notice for a scheduled Text Message or Phone Call for that contact file, which then appears on the CiviCRM home page. This is being generated by they system, not by us actually scheduling these activities. In fact, we've never used the activities scheduling function.

Is this some type of bug? Has anyone else experienced this problem?


Larry,

Toronto, ON

Hi Dave:

I'm the developer/host for this site.

Yes, i saw some similar issues (on a 2.1 upgrade), and it's possible the sms/phone calls are supposed to be a different activity, but what are they supposed to be? The off-line donations trigger the membership updates and then also these mystery activities at the same time (with the same subject). So I assume the activity is being generated by the membership cron code.

Re: versions - it's

Drupal 5
PHP 5.1
Mysql 5.0
CiviCRM 2.0.6

Also, i just noticed it happenning on a different install (same version).

Re: phone/sms - the older ones are sms, then it magically switched to phone after some months.

Hi Dave:

okay, that makes sense, but it looks more complicated than that in this case. Maybe this would help:

select * from civicrm_activity where source_contact_id = 14361;
+------+-------------------+------------------+------------------+---------------------------------------------------------------------+---------------------+---------------+----------+----------+----------+--------------+---------+-----------+-------------+-----------+---------+
| id   | source_contact_id | source_record_id | activity_type_id | subject                                                             | activity_date_time  | due_date_time | duration | location | phone_id | phone_number | details | status_id | priority_id | parent_id | is_test |
+------+-------------------+------------------+------------------+---------------------------------------------------------------------+---------------------+---------------+----------+----------+----------+--------------+---------+-----------+-------------+-----------+---------+
| 6861 |             14361 |             6326 |                6 | $ 10.00 - Offline membership signup (by xxxxxxxxxxxxxxx@xxxxxx.com) | 2009-01-03 21:51:00 | NULL          |     NULL | NULL     |     NULL | NULL         | NULL    |         2 |        NULL |      NULL |       0 |
| 6862 |             14361 |             3382 |                7 | Donation - Status: New                                              | 2009-01-03 00:00:00 | NULL          |     NULL | NULL     |     NULL | NULL         | NULL    |         2 |        NULL |      NULL |       0 |
| 6982 |             14361 |             NULL |                2 | Donation -                                                          | 2009-01-03 00:00:00 | NULL          |     NULL | NULL     |     NULL | NULL         | NULL    |         1 |        NULL |      NULL |       0 |
+------+-------------------+------------------+------------------+---------------------------------------------------------------------+---------------------+---------------+----------+----------+----------+--------------+---------+-----------+-------------+-----------+---------+
3 rows in set (0.00 sec)
It's that third record that's the irritant, and:

1. it's set to a status of 1 (scheduled) - that's what makes it irritating.
2. from the id number, it looks like it is generated after the membership-cron generated one, (but still possibly by the same script?).
3. the activity type id is 2. We haven't done anything to customize the activities, so I don't believe the problem is related to the activity label mapping. I'm also not sure why these phantom entries started off as sms entries (except maybe we disabled sms at some point?)

Does that add any more clues to what's going on?

One more clue ... we did fiddle with the Membership status rules. One of the changes was to reduce the "New" End Event Adjustment to 1 day from 30 days. I wonder if that's confusing some rule? The "Current" status runs from Start to End (No change) and we disabled the Pending "Status" [hmm .. that looks suspicious, when I edit it, it looks active]. I wonder if the abstractions around membership transitions might be so complicated that it's generating phantom entries somehow?