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 »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • Membership Status Update & Renewal Reminders - Testing (Scheduled Jobs)
Pages: [1]

Author Topic: Membership Status Update & Renewal Reminders - Testing (Scheduled Jobs)  (Read 912 times)

Tim Gummer

  • I’m new here
  • *
  • Posts: 12
  • Karma: 1
  • CiviCRM version: 3.3 - 4.1
  • CMS version: Drupal 6 & 7
  • MySQL version: 5.1.66
  • PHP version: 5.1.66-0+squeeze1
Membership Status Update & Renewal Reminders - Testing (Scheduled Jobs)
June 20, 2013, 07:20:31 pm

[size=78%]Is there any way to [/size]
  • separate updating and sending renewal reminders - or at least delay the latter?
  • test message templates on individuals or groups


We have a project activating  scheduled jobs has been somewhat delayed, so there are quite a few status updates and reminders about to happen when we do. We'd like to have some sense of how many reminders are going out before they do - hence delaying would be good - is there anything out side of just shutting down mail services that would allow this?


More importantly we need to edit, theme and test the System Workflow messages. How can we:
  • get some idea of the untokenized content for each message
  • test messages?
I've done quite a bit of work with civimail in the past, and despite it's limitations (hosted images, cross client checking anyone?) at least it's always had a simple test on yrself faclity. Not so here it would seem - unless I'm missing something. Unfortunately this isn't area where the staff concerned will be prepared to fly blind.


TIA




kreynen

  • I post occasionally
  • **
  • Posts: 105
  • Karma: 8
Re: Membership Status Update & Renewal Reminders - Testing (Scheduled Jobs)
June 21, 2013, 07:03:54 am
This probably doesn't help unless you were already considering changing hosts, but the way we handle this on Pantheon is to clone the current live site to the test environment, configure mail to 'Redirect to Database', run the scheduled job.  Even if you aren't using Pantheon to manage you a dev->test->live workflow, it sounds like you at the point you need a testing version of the site. 

There's only so much testing you can do by changing settings in the live environment. 

Tim Gummer

  • I’m new here
  • *
  • Posts: 12
  • Karma: 1
  • CiviCRM version: 3.3 - 4.1
  • CMS version: Drupal 6 & 7
  • MySQL version: 5.1.66
  • PHP version: 5.1.66-0+squeeze1
Re: Membership Status Update & Renewal Reminders - Testing (Scheduled Jobs)
June 22, 2013, 10:34:25 pm
thanks - yes do have a staging environment  - though its slightly dominated by other experiments at the moment, so its messy using it for this process  - but can be done. And what you are saying does resonate with other advice I'm getting - do it all on staging. SO be it.


Thanks again!

TIM

Tim Gummer

  • I’m new here
  • *
  • Posts: 12
  • Karma: 1
  • CiviCRM version: 3.3 - 4.1
  • CMS version: Drupal 6 & 7
  • MySQL version: 5.1.66
  • PHP version: 5.1.66-0+squeeze1
Re: Membership Status Update & Renewal Reminders - Testing (Scheduled Jobs)
June 22, 2013, 11:24:14 pm
Ugh - now i'm testing this on our dev version, and getting very inconsistant results from executing Update Membership Statuses and Send Renewal Reminders[/size]    


an earlier test on the entire db logged:
 [/size]Success (Processed 3116 membership records. Updated 0 records.)


A new test with slimmed down test set of members (main body of members 'soft' deleted) with their join and start dates set variously to result in grace or lapsed states, got:
Finished execution of Update Membership Statuses and Send Renewal Reminders with result: Success (Processed 3116 membership records. Updated 0 records.)
 
Which is problematic on two levels - setting my test memberships to old period dates doesn't trigger status changes, AND the script is apparently nominally processing (actually not processing ) the full 3116 memberships most of which are in the trash.


SO - er, any thoughts as to what could be stopping memberships with technically lapsed dates, NOT have their status updated?


Perplexed!






Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • Membership Status Update & Renewal Reminders - Testing (Scheduled Jobs)

This forum was archived on 2017-11-26.