No valid membership status for given dates

[Upperholme]

Working with version 4.4.0 on Wordpress.

Noticed that adding a relationship that should lead to an inherited membership is not working fully. Here's what is happening:

I add the relationship to the contact record. This gives me a page not found error upon submission. Going back to the contact record I can see that the relationship has in fact been created, but Io also get an error message:

"No valid membership status for given dates.
The membership cannot be saved because the status cannot be calculated."

The membership record has not been created.

Looking at the membership form the organisational point of view, i.e. contact/view/membership&action=view and revising the list of Related Contacts/Memberships I can see that my contact is listed, but there is no current membership listed against the contact, and I am provided with a link to 'Create' the membership, when of course this should have happened automagically.

Looking at this thread (http://forum.civicrm.org/index.php/topic,19445.msg80949.html#msg80949) I'm thinking it might be something to do with date formats as my site is localised and the display format is not the same as the format used to store the date in the DB.

Any pointers as to how to resolve this would be most welcome. Manually creating the membership works, but is less than ideal.

Regards
Graham

[CiviTeacher.com]

That error normally comes from invalid "membership status rules" or a set of rules with a "gap" in which your date range has fallen.

Suggest you check your status rules.

Also if you are still running 4.4.0, UPGRADE.

[Upperholme]

Thanks for the advice. I've already checked the status rules and they seem fine. I'll check again.
Upgrading is also on the to-do list, but i don't think that';s going to solve this particular issue.

[Upperholme]

Update on this one: I have reviewed the membership status rules. The Expired status looked to have 'End date' set as both starting and ending events, which suggested that this might be the cause of the problem. I've removed the ending event from the status, and we are no longer seeing the error message, which is a step forward.

Testing the thing out, I have an organisation which has a lifetime membership, commencing sometime back in 2012. I added an individual contact with an 'employee of' relationship to this organisation commencing on today's date, so I would expect them to immediately have the same membership by relationship. They are indeed given a membership, but it has the status 'expired'. The organisation's membership, and that other individuals with an 'employee of' relationship to the organisation, all have memberships with the status 'current'.

This is not what I would expect.

Looking again at the membership status rules, 'current' is the default one, so if anything iwould expect the new employee to be given a current membership. Why is it set as expired?

[phunter]

Seeing the same issue on the demo site.
Any lifetime membership goes to expired after the first three months.

See: http://drupal.demo.civicrm.org/civicrm/contact/view?reset=1&force=1&cid=212&selectedChild=member

[Upperholme]

Thanks phunter. I did spend some time working through various scenarios on the demo site to see if I could reproduce the issue, but didn't cover this option. It's positive news that this is a repeatable issue, and therefore likely to be bug.

[Upperholme]

Issue created: http://issues.civicrm.org/jira/browse/CRM-13937

[KarinG]

I've figured out what's causing the issue. I've posted my notes on http://issues.civicrm.org/jira/browse/CRM-13937

[KarinG]

We've arrived at a patch:
https://github.com/civicrm/civicrm-core/commit/12bf31e5543b01928cb4a8b5a3bd473fc387fa51#diff-0

It will be in the 4.4.4 release - but you can apply this patch to your current 4.4.x to get this working right away.