Modern admin dashboard

[balihr]

It's called backwards compatibility, so that plugins that use the "old" notifier don't need to change.

No no, it's called a brainf*rt. And I've been having a lot of those lately.

You really had me scratching my head here, but thanks for the push in the right direction! I really didn't think about the possibility of having a bridge to allow support for both...

So, if you could do me a favor and try this out. Revert the abuseipdb observer to the original, no changes to that file. And here's an updated version of index_dashboard.php: https://github.com/zenexpert/modern-..._dashboard.php
Thanks!

[lat9]

No no, it's called a brainf*rt. And I've been having a lot of those lately.

You really had me scratching my head here, but thanks for the push in the right direction! I really didn't think about the possibility of having a bridge to allow support for both...

So, if you could do me a favor and try this out. Revert the abuseipdb observer to the original, no changes to that file. And here's an updated version of index_dashboard.php: https://github.com/zenexpert/modern-..._dashboard.php
Thanks!

I don't use the AbuseIPDB plugin; the interoperability issue was reported by @retched.

[dbltoe]

I discovered one item that is a no-go for now. If I am missing it, let me know, but there seems to be no notification of log files in this new admin.

I harp on customers maintaining a lookout for problems to get them resolved before they become major.

Having to go to Tools > Display Log Files means they are going to get missed.

[OldNGrey]

I have ZC2.2.0 with Modern Admin Dashboard and the logfile notification is shown at the top of the screen.

[balihr]

I discovered one item that is a no-go for now. If I am missing it, let me know, but there seems to be no notification of log files in this new admin.

I harp on customers maintaining a lookout for problems to get them resolved before they become major.

Having to go to Tools > Display Log Files means they are going to get missed.

I'm not sure what to tell you, but I do believe you're missing it. All $messagestack output is shown below the header navigation menu - it's the very few lines of admin/includes/header.php
I'm assuming you're using the whole module (dashboard + header + order status colors).

I've just tested with the Display Logs plugin installed, forced one error, the log file was created and after refreshing the admin home page, the notification was there, same as OldNGrey's screenshot (just the yellow one, of course).

[dbltoe]

Loading on a new site, I got the following:

[23-Feb-2026 23:32:07 UTC] PHP Fatal error: Uncaught Error: Undefined constant "DATE_FORMAT_SHORT_NO_DAY" in /YOUR_ADMIN/stats_sales_report_graphs.php:260Stack trace:
#0 /YOUR_ADMIN/index.php(16): require()
#1 {main}
thrown in /YOUR_ADMIN/stats_sales_report_graphs.php on line 260


[23-Feb-2026 23:32:07 UTC] Request URI: /YOUR_ADMIN/index.php?cmd=stats_sales_report_graphs&report=4, IP address: 123.234.43.21
--> PHP Fatal error: Uncaught Error: Undefined constant "DATE_FORMAT_SHORT_NO_DAY" in /YOUR_ADMIN/stats_sales_report_graphs.php:260
Stack trace:
#0 /YOUR_ADMIN/index.php(16): require()
#1 {main}
thrown in /YOUR_ADMIN/stats_sales_report_graphs.php on line 260.


[23-Feb-2026 23:32:07 UTC] Request URI: /YOUR_ADMIN/index.php?cmd=stats_sales_report_graphs&report=4, IP address: 123.234.43.21
--> PHP Fatal error: Uncaught Error: Undefined constant "DATE_FORMAT_SHORT_NO_DAY" in /YOUR_ADMIN/stats_sales_report_graphs.php:260
Stack trace:
#0 /YOUR_ADMIN/index.php(16): require()
#1 {main}
thrown in /YOUR_ADMIN/stats_sales_report_graphs.php on line 260.

The define is missing from the file on GitHub but present in core files. I submitted a PR

'DATE_FORMAT' => 'm/d/Y',    'DATE_FORMAT_DATE_PICKER' => 'yy-mm-dd',
    'DATE_FORMAT_LONG' => '%A %d %B, %Y',
    'DATE_FORMAT_SHORT' => '%m/%d/%Y',
    'DATE_FORMAT_SHORT_NO_DAY' => '%B %Y',
    'DATE_FORMAT_SPIFFYCAL' => 'MM/dd/yyyy',
    'DATE_TIME_FORMAT' => '%%DATE_FORMAT_SHORT%%' . ' %H:%M:%S',
    'DEDUCTION_TYPE_DROPDOWN_0' => 'Deduct amount',
    'DEDUCTION_TYPE_DROPDOWN_1' => 'Percent',
    'DEDUCTION_TYPE_DROPDOWN_2' => 'New Price',

[carlwhat]

Loading on a new site, I got the following:

[23-Feb-2026 23:32:07 UTC] PHP Fatal error: Uncaught Error: Undefined constant "DATE_FORMAT_SHORT_NO_DAY" in /YOUR_ADMIN/stats_sales_report_graphs.php:260Stack trace:
#0 /YOUR_ADMIN/index.php(16): require()
#1 {main}
thrown in /YOUR_ADMIN/stats_sales_report_graphs.php on line 260


[23-Feb-2026 23:32:07 UTC] Request URI: /YOUR_ADMIN/index.php?cmd=stats_sales_report_graphs&report=4, IP address: 123.234.43.21
--> PHP Fatal error: Uncaught Error: Undefined constant "DATE_FORMAT_SHORT_NO_DAY" in /YOUR_ADMIN/stats_sales_report_graphs.php:260
Stack trace:
#0 /YOUR_ADMIN/index.php(16): require()
#1 {main}
thrown in /YOUR_ADMIN/stats_sales_report_graphs.php on line 260.


[23-Feb-2026 23:32:07 UTC] Request URI: /YOUR_ADMIN/index.php?cmd=stats_sales_report_graphs&report=4, IP address: 123.234.43.21
--> PHP Fatal error: Uncaught Error: Undefined constant "DATE_FORMAT_SHORT_NO_DAY" in /YOUR_ADMIN/stats_sales_report_graphs.php:260
Stack trace:
#0 /YOUR_ADMIN/index.php(16): require()
#1 {main}
thrown in /YOUR_ADMIN/stats_sales_report_graphs.php on line 260.

The define is missing from the file on GitHub but present in core files. I submitted a PR

'DATE_FORMAT' => 'm/d/Y',    'DATE_FORMAT_DATE_PICKER' => 'yy-mm-dd',
    'DATE_FORMAT_LONG' => '%A %d %B, %Y',
    'DATE_FORMAT_SHORT' => '%m/%d/%Y',
    'DATE_FORMAT_SHORT_NO_DAY' => '%B %Y',
    'DATE_FORMAT_SPIFFYCAL' => 'MM/dd/yyyy',
    'DATE_TIME_FORMAT' => '%%DATE_FORMAT_SHORT%%' . ' %H:%M:%S',
    'DEDUCTION_TYPE_DROPDOWN_0' => 'Deduct amount',
    'DEDUCTION_TYPE_DROPDOWN_1' => 'Percent',
    'DEDUCTION_TYPE_DROPDOWN_2' => 'New Price',

couple of things:

• this error is not related to the improved admin dashboard.
• looks like your codebase is somewhat old. i see that define having been added some 7 months ago.

best.

[balihr]

This error happens when you try to use this plugin on a Zen Cart 2.2.0 - the plugin was built for 2.1.0 and older and this constant was introduced in 2.2.0. Replacing the admin/includes/languages/lang.english.php in 2.2.0 with the one distributed with the plugin will cause this error on a 2.2.0 install, but that's not a bug in the plugin - it's user error for installing on a non-compatible version without merging files.

As mentioned on github, all development for this plugin for v2.2.0 has been put on hold as per Scott's request and me not wanting to flood the PR for 2.2.0 before it's discussed.