A recent discovery, prompted by and unrelated event, highlighted the fact that certain member's Last Visit Dates were not being updated by either recent visits, membership renewals or even new registrations. In the case of new registrations, the LVD field is blank. Some of the member's LVD fields are over a year old.
In checking the Subscriptions records, it appears to affect about 25% of recent member activity. Further research shows that all of the affected accounts have been properly processed for payment and proper records (baskets, payments, notifications, etc.) have been maintained by the system. So, it appears to be simply an issue of the LVD field not being updated. But what would ignore only certain accounts and process others?
I checked a sampling from our July records and found several affected accounts, and also checked about half a dozen January records and found none. I'm not sure when I updated to CB Subs v2.0.1, but believe it was close to July. Unfortunately, when I try to update to v2.0.2, it crashes the system and presents the WSOD, and I must roll back to 2.0.1. This was true on both the production and the development servers. The update must conflict with another installed component or module, but I have no idea which it might be or how to determine which.
So, the question is; is this a systemic problem not related to v2.0.1 (since some of the dates far precede v2.0.1)or has it been corrected with v2.0.2?
Note: we are planning to migrate to J2.5.x in the beginning of next year, so I seem to be saddled with this issue until then.
Thank you.
J 1.5.26, CB 1.8.1, CB Subs 2.0.1