Hi,
We in the process of completing an association website, are experiencing a corruption problem CB and CBSubs. We have 2000+ membership records loaded and CB and CBSubs was working reliably previously, configuration of CB subs was not complete but we had tested settings on trial short duration plans.
Following some work on the website by the user manager (described below) the following problems were noted:
• Some users were unable to login, getting a Login denied message (Snap_S95-1). When the user was Re-enabled in CB User Management the problem happened again.
• Other users were not affected. (We have not been able to identify causation differences)
Prior to this problem we were doing the following work: CBJuice2, upload new users >6, update renewal date for users ( >15). CB, add several additional fields, delete two fields. CBSubs, modify plans with additional messages, add notification emails, modify field value settings, supress some plans from appearing to the public. CB Auto Actions, edit auto actions attached to various plans, add some new actions. (During this work no error/warning messages were delivered.)
The CB Tools menu was checked and all is green:
• Check CB DB: All Green
• Check CB User Fields DB: All green, incl Strict Column types
• Check CB Plugins DB: All Green
• Check User DB: All Green
CBJuice2 was used to download the CB registrations and all data appeared correct. Four users with the problem were uploaded via CBJuice2 in Edit mode (Snap_S95-3) and all input was accepted without error. Again, the problem occurred. A CBJuice2 download was done and it appeared correct. However, there is now an additional problem. The CB Edit User screen (Snap_S95-4) does not accept edits and the validation is faulty (this only applies to the four uploads).
New entries entered either manually via the front end or via the back end appear to work as normal.
A single test new entry using CBJuice2 uploaded without error but cannot be edited in the backend (Snap_S95-4) and cannot be access on the front end.
This appears to be a case of a corrupted Database.
Can you suggest a process to fully identify and correct the problem?
Regards, Robert