[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
BillMax announce -- Problem with 2.0.6 Upgrade
For those customers that have upgraded from 2.0.X (where X is anything but 5)
to 2.0.6, the upgrade process may leave BillMax in a state where
credit card encryption is turned off.
Since credit cards in the database are encrypted already, this will
result in the wrong value being returned and used as the clear text
credit card number.
To determine if you have this problem, view an old account (created
prior to the upgrade) with a user that has credit card viewing
priviledges. If you see a string of characters that aren't digits
then you have the problem.
If you have this problem, you can fix it easily by running
the following sql:
update globalconf set encryptcc=1;
in the mysql monitor program. If you created any accounts with
credit cards since the upgrade, but before the change above,
you will need to reenter the credit card number in the web
interface. To get a list of credit card numbers and accounts to
reenter, execute the following sql:
select number, ccnum from account where ccnum = ccnumenc and ccnum != ""
and paytype = 2 order by number;
For each returned item from the query above, go to the account (number column
above) and renter the credit card number (ccnum column above).
This problem has been fixed in the 2.0.6 package on our
ftp site so subsequent 2.0.6 upgrades are OK.
Thank you.
BillMax Billing Solutions
----------------------------------------------------------------------------
To unsubscribe from the "BillMax Announce" mailing list, please
send a message to "majordomo@billmax.com" with "unsubscribe announce"
in the message body. The message must be sent from the exact email
address on the list.