We have added a public userlist and also the JoomUnited Google Map which supports CB lists with addresses etc to be on a google map.

What I have found is that when one clicks on a user while searching our member database just as a public browser (not logged in) that an email is stimulated to tell that member that their membership subscription is expired and that is time to renew.

How do we avoid that and control when these emails go out more precisely?

Thanks,

Stan

Kyle,

Actually, I am quite sure that our front end activity did trigger the expiration email that was sent out.
Here is how I know:

1. I added a public list on the frontend. (I hadn't done that ever before - as we always had the CB list behind registration) I also coupled it with a map from a separate component - My Maps Location (from Joom United)
2. As soon as I looked up a member on the map or on the list, the expiration email was sent to them if their membership was expired.
3. I did a second member, and the same thing happened.
4. Within the next 24 hours, I didn't lookup more, however a bunch more expiration emails were sent out from the CB Subs component which I figured correlated with Google bots hitting these now public pages.
5. I unpublished the public lists and map and these expiration notices have now stopped. I assuming it is because no-one is hitting them on the frontend and not because everyone who "needed" an expiration notice had already received one.
6. Furthermore, we have had the CB Subs running for several years, and the expiration notices never went out on their own, except when we were "working in the backend" in which case sometimes a member would receive one (if we had been in their user looking at their data) So - we suspected earlier that somehow we had triggered this activity.

Obviously we want to be in control of this activity and not have these triggered sporatically when someone clicks on their name in the list. We actually want it to be triggered by the rules we setup within the Subscription and when we want to send out expiration notices (which is how I think you all have intended it anyhow)

So, anyhow, we are needing some help to make this work correctly.

I have just renewed our CB Subs subscription so we can update to the latest, although our version is not that old (within the last year).

Thanks Kyle for your help in figuring this out.

Stan

Kyle,

Can you explain how to make these adjustments? This is exactly what we want to do and obviously we do not want front end activity triggering our expiration notices going out. We would rather have a defined rule of timing for when the expiration notices go out.
Thanks.