Guides & Tutorials7.3 Update TroubleshootingTroubleshooting a blank admin dashboard after update

Troubleshooting a blank admin dashboard after update

If none of the admin dashboard widgets are loading following an upgrade to version 7.3, the problem most likely lies in the table collation values. To confirm this:

Confirming the Issue

  1. Navigate to Setup > General Settings > Other tab
  2. Enable the SQL Debug option
  3. Return to the admin dashboard to reproduce the problem
  4. Now navigate to Utilities > Logs > Activity Log
  5. Make a note of any MySQL errors, such as:
Smarty Error: SQLSTATE[HY000]: General error: 1267 Illegal mix of collations (latin1_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '=' (SQL: select count(tblorders.id) as aggregate from tblordersinner join tblorderstatuses on tblorders.status = tblorderstatuses.title where tblorderstatuses.showpending = 1)

or

Smarty Error: SQLSTATE[HY000]: General error: 1267 Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' (SQL: select count(tblorders.id) as aggregate from tblordersinner join tblorderstatuses on tblorders.status = tblorderstatuses.title where tblorderstatuses.showpending = 1)

Resolving the Issue

To resolve the error, it is necessary to edit the MySQL database structure to make sure that both the tables have the same collation setting.

NOTE: Before making changes to the database, always backup first

In the first example, the collation settings are different:

  • tblorders = latin1_general_ci
  • tblorderstatuses = latin1_swedish_ci

To resolve the first error, the values need to be the same. The following command can be run against the database to resolve the error in the first scenario:

ALTER TABLE tblorderstatuses CONVERT TO CHARACTER SET latin1 COLLATE latin1_general_ci;

In the second example, the collation settings are different:

  • tblorders = utf8_general_ci
  • tblorderstatuses = utf8_unicode_ci

To resolve the second error, the values need to be the same. The following command can be run against the database to resolve the error in the second scenario:

ALTER TABLE tblorders CONVERT TO CHARACTER SET utf8 COLLATE utf8_unicode_ci;

Issue Persists

If the error persists, or you are not comfortable making these changes to your WHMCS database, please create a support ticket with technical support.