Local Delivery Drivers for WooCommerce 1.6.1

Does "Local Delivery Drivers for WooCommerce" work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
1PHP fatal errors
22PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 515.36 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: insignificant.
The plugin didn't make the site noticeably slower.

Environment
WordPress version5.7
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 1,000+
WordPress.org page https://wordpress.org/plugins/local-delivery-drivers-for-woocommerce/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 9

Delivery Drivers Settings ‹ Test site — WordPress

Page screenshot: Delivery Drivers Settings ‹ Test site — WordPress
URL /wp-admin/admin.php?page=lddfw-dashboard
Requested URL /wp-admin/plugins.php?action=activate&plugin=local-delivery-drivers-for-woocommerce%2Flocal-delivery-drivers-for-wooCommerce.php&plugin_status=all&paged=1&s&_wpnonce=b8286099a8
Aspect after-activation
HTTP status 200
Load time 1.713 s
Memory usage 3.56 MiB
JS errors None
Resource errors None

Delivery Drivers

Page screenshot: Delivery Drivers
URL /wp-admin/admin.php?page=lddfw-dashboard
Aspect menu-item
HTTP status 200
Load time 0.179 s
Memory usage 3.15 MiB
JS errors None
Resource errors None

Delivery Drivers → Routes

Page screenshot: Delivery Drivers → Routes
URL /wp-admin/admin.php?page=lddfw-routes
Aspect menu-item
HTTP status 200
Load time 0.239 s
Memory usage 3.15 MiB
JS errors None
Resource errors None

Delivery Drivers → Reports

Page screenshot: Delivery Drivers → Reports
URL /wp-admin/admin.php?page=lddfw-reports
Aspect menu-item
HTTP status 200
Load time 0.260 s
Memory usage N/A
JS errors None
Resource errors None

Delivery Drivers → Settings

Page screenshot: Delivery Drivers → Settings
URL /wp-admin/admin.php?page=lddfw-settings
Aspect menu-item
HTTP status 200
Load time 0.166 s
Memory usage 3.17 MiB
JS errors None
Resource errors None

Delivery Drivers → Affiliation

Page screenshot: Delivery Drivers → Affiliation
URL /wp-admin/admin.php?page=lddfw-dashboard-affiliation
Aspect menu-item
HTTP status 200
Load time 0.599 s
Memory usage 3.56 MiB
JS errors None
Resource errors None

Delivery Drivers → Contact Us

Page screenshot: Delivery Drivers → Contact Us
URL /wp-admin/admin.php?page=lddfw-dashboard-contact
Aspect menu-item
HTTP status 200
Load time 1.059 s
Memory usage 3.23 MiB
JS errors None
Resource errors None

Delivery Drivers → Upgrade  ➤

Page screenshot: Delivery Drivers → Upgrade  ➤
URL /wp-admin/admin.php?page=lddfw-dashboard-pricing
Aspect menu-item
HTTP status 200
Load time 0.179 s
Memory usage 3.52 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.354 s
Memory usage 3.01 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.267 s0.460 s+0.193 s2.82 MiB3.39 MiB+ 582.67 KiB
/wp-admin/edit.php0.185 s0.411 s+0.226 s2.86 MiB3.44 MiB+ 588.72 KiB
/wp-admin/post-new.php0.867 s1.100 s+0.233 s5.02 MiB5.61 MiB+ 602.38 KiB
/wp-admin/upload.php0.494 s0.422 s-0.072 s2.7 MiB3.17 MiB+ 489.87 KiB
/wp-admin/options-writing.php0.258 s0.181 s-0.077 s2.71 MiB3.16 MiB+ 457.78 KiB
/wp-admin/media-new.php0.226 s0.206 s-0.020 s2.67 MiB3.15 MiB+ 490.66 KiB
/wp-admin/edit-tags.php?taxonomy=category0.218 s0.220 s+0.002 s2.77 MiB3.19 MiB+ 433.7 KiB
/wp-admin/post-new.php?post_type=page1.150 s0.630 s-0.520 s5.01 MiB5.6 MiB+ 601.34 KiB
/wp-admin/options-discussion.php0.315 s0.220 s-0.095 s2.68 MiB3.15 MiB+ 490.91 KiB
/wp-admin/edit-comments.php0.235 s0.217 s-0.018 s2.78 MiB3.33 MiB+ 566.46 KiB
/0.288 s0.211 s-0.077 s2.65 MiB3.01 MiB+ 364.44 KiB
Average 0.409 s0.389 s-0.020 s3.15 MiB3.66 MiB+ 515.36 KiB

Code Statistics

Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.

PHP
PO File
Language % Lines of code Comment lines Files
PHP83.3%34,76117,692129
PO File11.3%4,7012,5024
CSS3.5%1,455514
JavaScript2.0%817634
Total 41,734 20,262 151

PHP Code Analysis | More results »

Lines of code 25,429
Total complexity 5,929
Median class complexity 17.0
Median method complexity 2.0
Most complex class Freemius
Most complex function FS_Plugin_Info_Dialog::install_plugin_information()
Classes 60
Methods 1,247
Functions 111

Additions

Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.

Options wp_options 22

Meta Boxes

{
    "shop_order": {
        "lddfw_metaboxes": {
            "title": "Delivery Driver",
            "context": "side"
        }
    }
}

Roles 1

ID Name
driverDelivery driver

PHP Error Log 32 lines

[12-Mar-2021 19:54:46 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:47 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:47 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:48 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:48 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:49 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:49 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function get_woocommerce_currency_symbol() in /wp-content/plugins/local-delivery-drivers-for-woocommerce/includes/class-lddfw-reports.php:340
Stack trace:
#0 /wp-content/plugins/local-delivery-drivers-for-woocommerce/includes/class-lddfw-reports.php(378): LDDFW_Reports->drivers_commissions_report()
#1 /wp-content/plugins/local-delivery-drivers-for-woocommerce/admin/class-lddfw-admin.php(1053): LDDFW_Reports->screen_reports()
#2 /wp-includes/class-wp-hook.php(292): LDDFW_Admin->lddfw_reports()
#3 /wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters()
#4 /wp-includes/plugin.php(484): WP_Hook->do_action()
#5 /wp-admin/admin.php(259): do_action()
#6 {main}
  thrown in /wp-content/plugins/local-delivery-drivers-for-woocommerce/includes/class-lddfw-reports.php on line 340
[12-Mar-2021 19:54:49 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:50 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:50 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:52 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:53 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:53 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:54 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:56 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:57 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:57 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:57 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:58 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:59 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:54:59 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:55:00 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[12-Mar-2021 19:55:00 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
See also: All tests for this plugin