This is verified.
It may have something to do with this strange ordering of the upgrades when running sbin/upgrade.pl:
Found upgrade executable from 7.1.2 to 7.1.3. Found upgrade executable from 7.1.1 to 7.1.2. Found upgrade executable from 7.2.0 to 7.2.1. Found upgrade executable from 7.1.3 to 7.2.0.
It didn't appear to run the 7.1.3-7.2.0 upgrade, but I tried running the 7.1.3-7.2.0 upgrade manually and it failed because the commerceSalesTax table that was created in that upgrade was already there. (almost as if the upgrade WAS, in fact, run)
This could be my fault, I could have run the 7.1.3 upgrade before it was ready. (sbin/upgrade.pl isn't for dev sites, I'm going to assume)
Also should point out that I'm unable to run any Administrative Operation, but the rest of my pages seem to work fine. I can even login. Seems I can do any Auth operations.
All administrative operations fail with the same error message:
2006/11/08 17:55:20 - ERROR - dev.localhost.localdomain.conf - main::[[undef]] - Couldn't execute operation : WebGUI::Operation::Admin::www_switchOnAdmin. Root cause: Can't use an undefined value as an ARRAY reference at /data/WebGUI/lib/WebGUI/User.pm line 133.
I'm going to bet even money that the commerceSalesTax table had already existed, causing the fixes to fail, causing this problem.
This is not a bug.
You are going to have to figure out what went wrong in your upgrade and fix it manually, just like I'm about to do.
A notice for the future: Perhaps it's better that you ask one of our community forums before you go off and immediately call it a bug.
There exists, in fact, an entire forum devoted to install/upgrade help: http://www.plainblack.com/install/upgrade_help
Closing this. Follow proper decorum please. Ask someone on the forums if they can reproduce, THEN post a bug.
Please. There is free support available on the PlainBlack forums, or you can purchase support from PlainBlack.
The bug list is not a place to get support.
You can run manual updates by executing the perl scripts in docs/upgrades
Then you can see what part of the update fails and work around that.