Report - TemplatesNext ToolKit 3.2.3

Does TemplatesNext ToolKit work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on 2021-03-10 05:14:37 UTC.

Summary

Errors

27	PHP notices
	No JavaScript exceptions
	All test pages loaded successfully
	No resource errors

Performance

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

Page speed impact: 0.145 seconds
The average page load time increased by this amount after activating the plugin.

Environment

WordPress version	5.7
PHP version	7.4.8
MySQL version	8.0.21
PHP memory limit	256M

Plugin Info

Last updated	2023-01-17T16:17:00+00:00
Active installs	10,000+
WordPress.org page	https://wordpress.org/plugins/templatesnext-toolkit/
Badges	Get badge code

Pages 15

Plugins ‹ Test site — WordPress

URL	/wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL	/wp-admin/plugins.php?action=activate&plugin=templatesnext-toolkit%2Ftx-toolkit.php&plugin_status=all&paged=1&s&_wpnonce=1495a08a78
Aspect	after-activation
HTTP status	200
Load time	0.577 s
Memory usage	3.04 MiB
JS errors	None
Resource errors	None

Testimonials

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

Testimonials → Add New

URL	/wp-admin/post-new.php?post_type=testimonials
Aspect	menu-item
HTTP status	200
Load time	1.219 s
Memory usage	3.23 MiB
JS errors	None
Resource errors	None

Testimonials → Testimonial Categories

URL	/wp-admin/edit-tags.php?taxonomy=testimonials-category&post_type=testimonials
Aspect	menu-item
HTTP status	200
Load time	0.229 s
Memory usage	3.02 MiB
JS errors	None
Resource errors	None

Portfolio

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

Portfolio → Add New

URL	/wp-admin/post-new.php?post_type=portfolio
Aspect	menu-item
HTTP status	200
Load time	0.966 s
Memory usage	3.15 MiB
JS errors	None
Resource errors	None

Portfolio → Portfolio Categories

URL	/wp-admin/edit-tags.php?taxonomy=portfolio-category&post_type=portfolio
Aspect	menu-item
HTTP status	200
Load time	0.242 s
Memory usage	3.02 MiB
JS errors	None
Resource errors	None

itrans Slider

URL	/wp-admin/edit.php?post_type=itrans-slider
Aspect	menu-item
HTTP status	200
Load time	0.176 s
Memory usage	3.07 MiB
JS errors	None
Resource errors	None

itrans Slider → Add New

URL	/wp-admin/post-new.php?post_type=itrans-slider
Aspect	menu-item
HTTP status	200
Load time	0.847 s
Memory usage	3.16 MiB
JS errors	None
Resource errors	None

itrans Slider → itrans Slider Categories

URL	/wp-admin/edit-tags.php?taxonomy=itrans-slider-category&post_type=itrans-slider
Aspect	menu-item
HTTP status	200
Load time	0.292 s
Memory usage	3.02 MiB
JS errors	None
Resource errors	None

Team

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

Team → Add New

URL	/wp-admin/post-new.php?post_type=team
Aspect	menu-item
HTTP status	200
Load time	0.923 s
Memory usage	3.16 MiB
JS errors	None
Resource errors	None

Team → Team Categories

URL	/wp-admin/edit-tags.php?taxonomy=team-category&post_type=team
Aspect	menu-item
HTTP status	200
Load time	0.268 s
Memory usage	3.02 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.571 s
Memory usage	2.89 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	0.836 s
Memory usage	3.08 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.267 s	0.739 s	+0.472 s	2.82 MiB	3.09 MiB	+ 274.01 KiB
/wp-admin/edit.php	0.177 s	0.347 s	+0.170 s	2.86 MiB	3.18 MiB	+ 323.84 KiB
/wp-admin/post-new.php	0.894 s	1.822 s	+0.928 s	5.02 MiB	5.36 MiB	+ 340.39 KiB
/wp-admin/upload.php	0.475 s	0.482 s	+0.007 s	2.7 MiB	3.02 MiB	+ 332.88 KiB
/wp-admin/options-writing.php	0.256 s	0.192 s	-0.064 s	2.71 MiB	3 MiB	+ 301.38 KiB
/wp-admin/media-new.php	0.230 s	0.223 s	-0.007 s	2.67 MiB	3 MiB	+ 335.55 KiB
/wp-admin/edit-tags.php?taxonomy=category	0.223 s	0.211 s	-0.012 s	2.77 MiB	3.04 MiB	+ 275.1 KiB
/wp-admin/post-new.php?post_type=page	1.101 s	0.972 s	-0.129 s	5.01 MiB	5.34 MiB	+ 337.02 KiB
/wp-admin/options-discussion.php	0.285 s	0.258 s	-0.027 s	2.67 MiB	3 MiB	+ 337.12 KiB
/wp-admin/edit-comments.php	0.240 s	0.224 s	-0.016 s	2.78 MiB	3.04 MiB	+ 273.71 KiB
/	0.264 s	0.532 s	+0.268 s	2.71 MiB	2.89 MiB	+ 192.02 KiB
Average	0.401 s	0.546 s	+0.145 s	3.16 MiB	3.45 MiB	+ 302.09 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

CSS

Language		%	Lines of code	Comment lines	Files
	PHP	43.9%	10,658	5,676	137
	JavaScript	27.5%	6,670	745	46
	CSS	21.0%	5,091	197	43
	PO File	5.7%	1,384	567	11
	Sass	1.8%	427	94	7
	XML	0.1%	15	0	1
	Markdown	0.0%	8	0	1
	SVG	0.0%	5	0	1
Total			24,258	7,279	247

PHP Code Analysis | More results »

Lines of code	10,107
Total complexity	1,608
Median class complexity	7.0
Median method complexity	1.0
Most complex class	RWMB_Field
Most complex function	tx_image_resize()

Classes	103
Methods	524
Functions	154

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` 5

widget_nx-widget-portfolio-grid
widget_nx-widget-recent-comments
widget_nx-widget-recent-posts
widget_widget-advert-grid
widget_widget-nx-image

Custom Post Types 4

ID	Name
testimonials	Testimonials
portfolio	Portfolio
itrans-slider	itrans Slider
team	Team

Sidebar Widgets 5

ID	Name
nx-widget-recent-posts	NX Recent Posts
nx-widget-portfolio-grid	NX Portfolio Grid
widget-advert-grid	NX Advert Grid Widget
nx-widget-recent-comments	NX Recent Comments
widget-nx-image	NX Image Widget

Meta Boxes

{
    "portfolio": {
        "portfolio-feature-image-2": {
            "title": "2nd Feature Image",
            "context": "side"
        },
        "portfolio-feature-image-3": {
            "title": "3rd Feature Image",
            "context": "side"
        }
    },
    "itrans-slider": {
        "itrans-slider": {
            "title": "itrans Slide Meta",
            "context": "normal"
        }
    },
    "team": {
        "teammember": {
            "title": "Team Member Details",
            "context": "normal"
        }
    },
    "testimonials": {
        "testimonialmeta": {
            "title": "Testimonial Meta",
            "context": "normal"
        }
    }
}

PHP Error Log 27 lines

[10-Mar-2021 05:14: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
[10-Mar-2021 05:14: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
[10-Mar-2021 05:14: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
[10-Mar-2021 05:14: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
[10-Mar-2021 05:14:55 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 05:14:55 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 05:14:55 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 05:14: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
[10-Mar-2021 05:14: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
[10-Mar-2021 05:14: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
[10-Mar-2021 05:14: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
[10-Mar-2021 05:14: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
[10-Mar-2021 05:14: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
[10-Mar-2021 05:15:01 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 05:15:02 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 05:15:03 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 05:15:04 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 05:15:07 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 05:15:08 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 05:15:08 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 05:15:08 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 05:15:09 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 05:15:10 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 05:15:11 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 05:15:11 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 05:15: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 05:15: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

TemplatesNext ToolKit 3.2.3