This is in reference to this thread which received ample attention at the beginning of this year when 3.1.6PRO ran into the 2012 end date: Unfortunately I think the problem has not been fixed properly via the steps described in the previous thread. This morning I checked one subscriber and saw this: http://screencast.com/t/j5nm6fZ4j2S As you can see the January sub has not been deactivated (i.e. the end date changed to 1/31/2013). Please see here: http://screencast.com/t/oCHyZieNlFcy The end date is still 2036. Here is another example: http://screencast.com/t/leohOoavJa Now, I am pretty sure I have implemented all the fixes that were required and I'm afraid this is going to once again cause chaos. What can I do?? I will also need to run a SQL call that allows me to see all old recurring subscriptions which are still active today. Meaning all subscriptions which should have been expired but retained the 2036 end date. Any help would be appreciated.
3.1.6 is a pretty old version. Have you not considered updating to at least the latest version of V3? 3.2.x was upgraded to cover this problem. Simply updating various individual files might always be fought with problems!
Yes, I have considered that but have made some changes to some of the PHP files. An upgrade would wipe most of that out, right? At least that's what aMember support told me.
Sounds like you know what your answer is ... why not copy over your directories to a 2nd location, including the database, and work on the steps to upgrade your site. Make sure you're able to successfully upgrade including the documentation of the changes and then apply on the live site? Ultimately if you're working on a copy of the directory AND a copy of the db, and you're certain there is a clear detachment from your live site, then you can experiment all you want.