CiviCRM Community Forums (archive)

Hi, everyone.

Bit of an odd one - I'm currently configuring a test site and one thing's not quite working which I think ought to be. When I have two contacts where A is the employer of B and there is a consequential inherited membership, I would like the membership to be removed from B when the relationship expires. I believe this is expected functionality. However, if I set the relationship to end at a certain date...

a) The relationship continues and,
b) The membership inheritance remains.

I have noticed that, while the end date remains in the Edit Relationship screen, the time always disappears if I click Save Relationship then Edit Relationship again. Is this perhaps the reason that the relationship doesn't end? Regardless, even if the end date comes and goes (I ran an overnight test), the relationship continues.

I can force the relationship to end by manually setting the end date to a previous day but, obviously, I need this to be automated. And, as a further wrinkle on this issue, I notice that, even if the relationship is manually set to be inactive, the membership is still active and inherited.

It's a confusing one...

Do I need to set up cron jobs for this, perhaps? Or am I missing something really obvious?

Huge thanks in advance for your help,

Robin

Thanks for the help, Lobo.

I thought it may have something to do with that, but just wanted to check whether the cron job specified at that wiki page would also update relationship status. I guess it's a suck-it-and-see situation, but do you suspect that it will cover relationships or that a patch will definitely need to be written? It seems odd to have an expiry date there in the gui for relationships but no way to trigger an expiry as yet. That said, I'm always happy to find a hole if it means either we or someone else can patch it!

In the short term, how easy would it be to remove the to date and time fields from the edit relationship page? I'm keen not to have something there if it doesn't actually function as expected.

Many thanks again for all your incredible work (and that goes for the entire core team),

Robin

That's great - thank you. I've commented out the end date section for now and, should our client require it, we'll definitely look into testing the cron and, if it's not working as expected, contributing some code. On a more personal note, I shall certainly make a contribution at some point.