Membership renewal button missing

In all cases the Renewal button was missing from their Membership Renewal screen. Our Total Occurrences was set to 3 (1 year memberships). All of these members had subscribed to a 1 year membership and should have been able to renew two more times. The renewal button should still be displayed because they had not reached the maximum term, however it was missing.

I now have Total Occurrences set to 0 (unlimited) as you advised.

Once set to 0 is the renewal button now visible for those experiencing the issue?

For all of the members with this situation we know about, I re-imported using the procedure described earlier. So, those all do have the button back, but that was before I started this thread. We have no idea how many have not been discovered yet.

So far, there have been about 20 memberships affected by this, but none in the past 10 days or so. As I stated previously, this did not happen before I updated to CB Subs 2.0.1.

We have also been experiencing sporadic difficulties with several other components as we update those to current versions (which are compatible with J2.5), so I have been wondering if J1.5.26 might be stressed beyond its capabilities. As I also stated previously, when I updated to CB Subs 2.0.2, CB Subs crashes to WSOD, requiring a roll-back to 2.0.1. There is obviously a conflict introduced with this new update.

I've been trying to convince this client to upgrade to J2.5 since the beginning of the year and we are working on that now, but it's not planned until the first of next year. Hopefully, with the migration to J2.5, some of these issues will settle down. At this point, I think this will take much more time to diagnose than it is worth and I don't want to consume any more of your time than I already have.

I'll continue with it as it is and handle any new instances manually as I have been until the migration. If it continues after the migration, I'll have to revisit this as a support issue.

Thank you for your assistance.

It's likely what you're experiencing is a bug in 2.0.1. I recall this being a problem, but I can't recall which version. If it crashes your site on install then it's very likely an ioncube problem, but don't know as didn't debug it (can if you would like to upgrade).

Our production server is using a Linux version of ionCube v4.2.2, while my development server is using ionCube Windows v5.3. Would this conflict affect both of these versions?

I do see that there is an update to the ionCube Windows version. I'll update that, try to update to CB Subs 2.0.2 and report back.

Thanks

That could be it, does 2.0.2 work fine on the linux server as it should as that's latest ioncube. If it's only the windows server with a problem then a simple upgrade to ioncube should resolve the crashing issue.