CiviCRM Community Forums (archive)

This isn't really an essential feature for me as I don't work using the Member Status, but I've noticed that all members whose expiry date is between now and the beginning of this month (Oct 1-16) is set to 'Current'. I've not amended the rules at all, so the 'expired' status should be set to kick in as soon as the expiry date passes the present.

Is this rule only run by the month? So when I get to November, all those incorrect 'Current' statuses all get set to 'Grace' and so on.

I'm sure that this isn't a result of incorrect statuses on import (which I did recently) as the system shows up an error when you try and import incorrect statuses.

Anyone else experienced this? Like I said, this is no big deal, but worth pointing out.

Cheers Speleo,
I've set up the cron job to run on my Windows PC according to the instructions here: http://drupal.org/node/31506
I've deleted the .txt extension so now the file is called UpdateMembershipStatus.php...
But...
When I try to run the job I get this error:
ERROR: You need to send a valid user name and password to execute this file
When running it manually or automatically. Is there some other file I need to put the username and password into? And it is my computer un/pw - not the CiviCRM/Drupal login details???
Cheers in advance.
James.

Cheers speleo,
Haven't tried it yet but found the answer here: http://forum.civicrm.org/index.php/topic,1018.0.html


"In the UpdateMembershipRecord.php, found the following line:
Code:

CRM_Utils_System::authenticateScript( true );


and changed it to

Code:

CRM_Utils_System::authenticateScript( false );


I realize this makes it not authenticate, but frankly, I'd rather have this than passing the userid and password in a url, especially if done in a cronjob."

A quick google and I found it here: http://wiki.civicrm.org/confluence/display/CRMDOC/Membership+Types

The bin/UpdateMembershipRecord.php.txt file just needs renaming as far as I can see. But, agreed, it's not apparent enough. It would be nice if there was some way of operating the script within CiviCRM - but I suppose that the cronjob needs are OS specific and cannot be controlled within the CRM software.