Report - WP User Frontend 3.5.14

Does WP User Frontend work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on 2021-03-10 04:13:56 UTC.

Summary

Errors

34	PHP notices
	No JavaScript exceptions
1	Page failed to load 1 404 Not Found
	No resource errors

Performance

Memory usage: 711.74 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 version	5.7
PHP version	7.4.8
MySQL version	8.0.21
PHP memory limit	256M

Plugin Info

Last updated	2025-04-23T11:02:00+00:00
Active installs	20,000+
WordPress.org page	https://wordpress.org/plugins/wp-user-frontend/
Badges	Get badge code

Pages 24

WPUF › Setup Wizard

URL	/wp-admin/index.php?page=wpuf-setup
Requested URL	/wp-admin/plugins.php?action=activate&plugin=wp-user-frontend%2Fwpuf.php&plugin_status=all&paged=1&s&_wpnonce=03b07d1a30
Aspect	after-activation
HTTP status	200
Load time	0.693 s
Memory usage	N/A
JS errors	None
Resource errors	None

Dashboard → WPUF Setup

URL	/wp-admin/wpuf-setup
Aspect	menu-item
HTTP status	404
Load time	0.473 s
Memory usage	2.98 MiB
JS errors	None
Resource errors	None

User Frontend

URL	/wp-admin/admin.php?page=wpuf-post-forms
Aspect	menu-item
HTTP status	200
Load time	0.423 s
Memory usage	3.56 MiB
JS errors	None
Resource errors	None

User Frontend → Registration Forms

URL	/wp-admin/admin.php?page=wpuf-profile-forms
Aspect	menu-item
HTTP status	200
Load time	0.300 s
Memory usage	3.51 MiB
JS errors	None
Resource errors	None

User Frontend → Subscriptions

URL	/wp-admin/edit.php?post_type=wpuf_subscription
Aspect	menu-item
HTTP status	200
Load time	0.198 s
Memory usage	3.5 MiB
JS errors	None
Resource errors	None

User Frontend → Coupons

URL	/wp-admin/admin.php?page=wpuf_coupon
Aspect	menu-item
HTTP status	200
Load time	0.167 s
Memory usage	3.4 MiB
JS errors	None
Resource errors	None

User Frontend → Transactions

URL	/wp-admin/admin.php?page=wpuf_transaction
Aspect	menu-item
HTTP status	200
Load time	0.287 s
Memory usage	3.61 MiB
JS errors	None
Resource errors	None

User Frontend → Tools

URL	/wp-admin/admin.php?page=wpuf_tools
Aspect	menu-item
HTTP status	200
Load time	0.440 s
Memory usage	3.62 MiB
JS errors	None
Resource errors	None

User Frontend → Tools → Import

URL	/wp-admin/admin.php?page=wpuf_tools&tab=import
Aspect	menu-item-tab
HTTP status	200
Load time	0.280 s
Memory usage	3.51 MiB
JS errors	None
Resource errors	None

User Frontend → Tools → Export

URL	/wp-admin/admin.php?page=wpuf_tools&tab=export
Aspect	menu-item-tab
HTTP status	200
Load time	0.271 s
Memory usage	3.51 MiB
JS errors	None
Resource errors	None

User Frontend → Premium

URL	/wp-admin/admin.php?page=wpuf_premium
Aspect	menu-item
HTTP status	200
Load time	0.369 s
Memory usage	3.52 MiB
JS errors	None
Resource errors	None

User Frontend → Help

URL	/wp-admin/admin.php?page=wpuf-support
Aspect	menu-item
HTTP status	200
Load time	0.273 s
Memory usage	3.57 MiB
JS errors	None
Resource errors	None

User Frontend → Settings

URL	/wp-admin/admin.php?page=wpuf-settings
Aspect	menu-item
HTTP status	200
Load time	0.768 s
Memory usage	3.61 MiB
JS errors	None
Resource errors	None

User Frontend → Settings → Frontend Posting

URL	/wp-admin/admin.php?page=wpuf-settings
Aspect	menu-item-tab
HTTP status	200
Load time	0.692 s
Memory usage	3.61 MiB
JS errors	None
Resource errors	None

User Frontend → Settings → Dashboard

URL	/wp-admin/admin.php?page=wpuf-settings
Aspect	menu-item-tab
HTTP status	200
Load time	0.553 s
Memory usage	3.61 MiB
JS errors	None
Resource errors	None

User Frontend → Settings → My Account

URL	/wp-admin/admin.php?page=wpuf-settings
Aspect	menu-item-tab
HTTP status	200
Load time	0.571 s
Memory usage	3.61 MiB
JS errors	None
Resource errors	None

User Frontend → Settings → Login / Registration

URL	/wp-admin/admin.php?page=wpuf-settings
Aspect	menu-item-tab
HTTP status	200
Load time	0.582 s
Memory usage	3.61 MiB
JS errors	None
Resource errors	None

User Frontend → Settings → Payments

URL	/wp-admin/admin.php?page=wpuf-settings
Aspect	menu-item-tab
HTTP status	200
Load time	0.566 s
Memory usage	3.61 MiB
JS errors	None
Resource errors	None

User Frontend → Settings → E-Mails

URL	/wp-admin/admin.php?page=wpuf-settings
Aspect	menu-item-tab
HTTP status	200
Load time	0.601 s
Memory usage	3.61 MiB
JS errors	None
Resource errors	None

User Frontend → Settings → Privacy Options

URL	/wp-admin/admin.php?page=wpuf-settings
Aspect	menu-item-tab
HTTP status	200
Load time	0.526 s
Memory usage	3.61 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.565 s
Memory usage	3 MiB
JS errors	None
Resource errors	None

Add New Post ‹ Test site — WordPress

URL	/wp-admin/post-new.php
Aspect	new-meta-boxes
HTTP status	200
Load time	1.278 s
Memory usage	5.75 MiB
JS errors	None
Resource errors	None

Add New Page ‹ Test site — WordPress

URL	/wp-admin/post-new.php?post_type=page
Aspect	new-meta-boxes
HTTP status	200
Load time	0.869 s
Memory usage	5.73 MiB
JS errors	None
Resource errors	None

Widgets ‹ Test site — WordPress

URL	/wp-admin/widgets.php
Aspect	new-sidebar-widgets
HTTP status	200
Load time	1.048 s
Memory usage	3.68 MiB
JS errors	None
Resource errors	None

Benchmark

URL	Load time			Memory usage
URL	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.276 s	0.344 s	+0.068 s	2.82 MiB	3.59 MiB	+ 787.55 KiB
/wp-admin/edit.php	0.175 s	0.241 s	+0.066 s	2.86 MiB	3.61 MiB	+ 770.02 KiB
/wp-admin/post-new.php	1.037 s	1.024 s	-0.013 s	5.02 MiB	5.75 MiB	+ 744.21 KiB
/wp-admin/upload.php	0.510 s	0.312 s	-0.198 s	2.7 MiB	3.51 MiB	+ 829.74 KiB
/wp-admin/options-writing.php	0.240 s	0.188 s	-0.052 s	2.71 MiB	3.41 MiB	+ 715.52 KiB
/wp-admin/media-new.php	0.231 s	0.205 s	-0.026 s	2.67 MiB	3.41 MiB	+ 757.84 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.184 s	0.208 s	+0.024 s	2.77 MiB	3.46 MiB	+ 706.08 KiB
/wp-admin/post-new.php?post_type=page	1.139 s	1.132 s	-0.007 s	5.01 MiB	5.73 MiB	+ 740.26 KiB
/wp-admin/options-discussion.php	0.311 s	0.261 s	-0.050 s	2.67 MiB	3.43 MiB	+ 768.84 KiB
/wp-admin/edit-comments.php	0.224 s	0.227 s	+0.003 s	2.78 MiB	3.47 MiB	+ 708.71 KiB
/	0.267 s	0.564 s	+0.297 s	2.71 MiB	3 MiB	+ 300.41 KiB
Average	0.418 s	0.428 s	+0.010 s	3.16 MiB	3.85 MiB	+ 711.74 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

JavaScript

PO File

CSS

Language		%	Lines of code	Comment lines	Files
	PHP	45.5%	31,620	7,571	194
	JavaScript	24.3%	16,885	1,242	67
	PO File	14.3%	9,981	5,594	5
	CSS	8.9%	6,218	51	13
	LESS	6.6%	4,564	130	19
	JSON	0.4%	245	0	1
	YAML	0.0%	32	0	1
	SVG	0.0%	17	0	17
Total			69,562	14,588	317

PHP Code Analysis | More results »

Lines of code	26,547
Total complexity	4,768
Median class complexity	14.0
Median method complexity	2.0
Most complex class	WPUF_Render_Form
Most complex function	wpuf_show_custom_fields()

Classes	123
Methods	1,007
Functions	141

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.

Database Tables 2

wp_wpuf_subscribers
wp_wpuf_transaction

Options `wp_options` 12

widget_wpuf_login_widget
wpuf_address_options
wpuf_dashboard
wpuf_frontend_posting
wpuf_general
wpuf_installed
wpuf_mails
wpuf_my_account
wpuf_payment
wpuf_privacy
wpuf_profile
wpuf_version

Custom Post Types 4

ID	Name
wpuf_subscription	Subscription
wpuf_forms	Forms
wpuf_profile	Forms
wpuf_input	Posts

Sidebar Widgets 1

ID	Name
wpuf_login_widget	WPUF Ajax Login

Meta Boxes

{
    "post": {
        "wpuf-select-form": {
            "title": "WPUF Form",
            "context": "side"
        },
        "wpuf-post-lock": {
            "title": "WPUF Lock User",
            "context": "side"
        },
        "wpuf-custom-fields": {
            "title": "WPUF Custom Fields",
            "context": "normal"
        }
    },
    "page": {
        "wpuf-custom-fields": {
            "title": "WPUF Custom Fields",
            "context": "normal"
        },
        "wpuf-select-form": {
            "title": "WPUF Form",
            "context": "side"
        },
        "wpuf-post-lock": {
            "title": "WPUF Lock User",
            "context": "side"
        }
    },
    "attachment": {
        "wpuf-custom-fields": {
            "title": "WPUF Custom Fields",
            "context": "normal"
        },
        "wpuf-select-form": {
            "title": "WPUF Form",
            "context": "side"
        },
        "wpuf-post-lock": {
            "title": "WPUF Lock User",
            "context": "side"
        }
    },
    "wpuf_subscription": {
        "wpuf-metabox-subscription": {
            "title": "Pack Description",
            "context": "normal"
        },
        "wpuf_subs_metabox": {
            "title": "Subscription Options",
            "context": "advanced"
        }
    }
}

PHP Error Log 34 lines

[10-Mar-2021 04:14:12 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
[10-Mar-2021 04:14:13 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
[10-Mar-2021 04:14:14 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
[10-Mar-2021 04:14:14 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
[10-Mar-2021 04:14:15 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
[10-Mar-2021 04:14:15 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
[10-Mar-2021 04:14:16 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
[10-Mar-2021 04:14:16 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
[10-Mar-2021 04:14:17 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
[10-Mar-2021 04:14:17 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
[10-Mar-2021 04:14:19 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
[10-Mar-2021 04:14:20 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
[10-Mar-2021 04:14:21 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
[10-Mar-2021 04:14:23 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
[10-Mar-2021 04:14:24 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
[10-Mar-2021 04:14:25 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
[10-Mar-2021 04:14:27 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
[10-Mar-2021 04:14:28 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
[10-Mar-2021 04:14:30 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
[10-Mar-2021 04:14:32 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
[10-Mar-2021 04:14:32 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
[10-Mar-2021 04:14:33 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
[10-Mar-2021 04:14:35 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
[10-Mar-2021 04:14:35 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
[10-Mar-2021 04:14:35 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
[10-Mar-2021 04:14:36 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
[10-Mar-2021 04:14:36 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
[10-Mar-2021 04:14:38 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
[10-Mar-2021 04:14:38 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
[10-Mar-2021 04:14:39 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
[10-Mar-2021 04:14:40 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
[10-Mar-2021 04:14:43 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
[10-Mar-2021 04:14:44 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
[10-Mar-2021 04:14: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

WP User Frontend 3.5.14