CiviCRM Community Forums (archive)

Hi, I'm having the exact same issue as general_ludd in this post: http://forum.civicrm.org/index.php/topic,24375.0.html

I'm running Drupal 7.15 and CiviCRM 4.1.2. I think that my membership types and status rules are set up correctly.

However, when trying to read the documentation (http://wiki.civicrm.org/confluence/display/CRMDOC40/Membership+Types) pointed to by petednz, I just cannot find the file that is referred to (/bin/UpdateMembershipRecord.php.txt) in my public_html/sites/all/modules/civicrm/bin folder.
I can however find a file called UpdateMembershipRecord.php, but it is under the folder /bin/deprecated, from which I interpret that this is a file that is not to be used anymore?? It also seems to be quite a lot shorter than the file referred to in the documentation.

I tried downloading the latest version of CiviCRM, but it seems the file is missing even here.

Where am I going wrong? Is it me, the documentation or my install that's got the biggest issues?? (guessing: me!)
I just cannot seem to figure this one out, and it's high time to update the statuses of all our members....

Thanks in advance for any pointers!

Ah, thank you! I really must have missed that loud warning at the end of upgrading somehow. Sorry about that! 

However, a new problem occurs: When I'm trying to run the cron job from command line, it doesn't quite seem to "click"?
Here's the command followed by it's output (I've taken the liberty to hide my user/pw and some of the path, otherwise it's a simple copy/paste). I'm running it from the civicrm folder:

$ php bin/cli.php -u <myuser> -p <mypassword> -e Job -a execute
PHP Notice:  Trying to get property of non-object in /###/###/domains/###/public_html/sites/all/modules/civicrm/CRM/Utils/System/Drupal.php on line 541
PHP Notice:  Trying to get property of non-object in /###/###/domains/###/public_html/sites/all/modules/civicrm/CRM/Utils/System/Drupal.php on line 542
PHP Notice:  Trying to get property of non-object in /###/###/domains/###/public_html/sites/all/modules/civicrm/CRM/Utils/System/Drupal.php on line 543
PHP Notice:  Trying to get property of non-object in /###/###/domains/###/public_html/sites/all/modules/civicrm/CRM/Utils/System/Drupal.php on line 546
PHP Notice:  Undefined offset: 0 in /###/###/domains/###/public_html/sites/all/modules/civicrm/CRM/Core/I18n/PseudoConstant.php on line 59
Jobs called from cli.php require valid user and password as parameter

I've tried run this using a user with administrator priveliges to my Drupal site, and all possible priveliges in the CiviCRM ACL list, so I don't understand what I'm missing (again).
Are someone able to give me a hint? Thanks in advance!

PS! I would prefer to run this as a non-administrator, but I'm really unsure what permissions are actually needed? Is there a list somewhere that I haven't been able to find?

Ah, there the cron is actually running as it should! One step closer! Thanks a lot Hershel! 

BUT, the original error is still there, our members still cannot renew their memberships, even if it says that "the membership expired on 31. july 2012". They still get the error message "You already have a lifetime membership and cannot select a membership with a shorter term".

I'm out of ideas, do you have any Hershel?

The membership in question is a "fixed 6 month" membership.

He did run through parts of the registration one time before actually managing, so he's got one old membership with status "Cancelled" which never was activated. Then he's got this one new membership that is expired, which is the one he's trying to renew.
I'm not sure, but I have a very strong suspicion that this will apply to all of our members.

Yes I did. These are the jobs I'm running:

Activity processor (Hourly)
Bounces fetcher (Daily)
Mailings scheduler (Hourly)
Membership status processor (Daily)
Participant status processor (Always)
Scheduled reminders sender (Daily)

All of these were ran successfully according to the log, except for bounces and activity which could not connect to MailStore.

Wow! That fixed it!  Thank you!

But why really? Is there a way to avoid that this happens when people aborts a payment?

Humm.. wonder if this is then something that should be reported as a bug, or if it is just something that I've done wrong (again).