Classic Editor and Classic Widgets 1.1.1

Does "Classic Editor and Classic Widgets" work with WordPress 6.0.2 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
6PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: -302.19 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 version6.0.2
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 20,000+
WordPress.org page https://wordpress.org/plugins/classic-editor-and-classic-widgets/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 3

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=classic-editor-and-classic-widgets%2Fclassic-editor-and-classic-widgets.php&plugin_status=all&paged=1&s&_wpnonce=9c593cf2b7
Aspect after-activation
HTTP status 200
Load time 0.244 s
Memory usage 3.71 MiB
JS errors None
Resource errors None

Settings → Classic Editor

Page screenshot: Settings → Classic Editor
URL /wp-admin/options-general.php?page=classic-editor-and-classic-widgets
Aspect menu-item
HTTP status 200
Load time 0.170 s
Memory usage 3.72 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.315 s
Memory usage 3.57 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.317 s0.246 s-0.071 s3.72 MiB3.74 MiB+ 12.8 KiB
/wp-admin/edit.php0.193 s0.185 s-0.008 s3.76 MiB3.77 MiB+ 12.8 KiB
/wp-admin/post-new.php0.752 s1.025 s+0.273 s5.55 MiB3.85 MiB- 1.7 MiB
/wp-admin/upload.php0.384 s0.235 s-0.149 s3.69 MiB3.7 MiB+ 11.67 KiB
/wp-admin/options-writing.php0.262 s0.148 s-0.114 s3.62 MiB3.67 MiB+ 55.58 KiB
/wp-admin/media-new.php0.367 s0.198 s-0.169 s3.66 MiB3.68 MiB+ 11.84 KiB
/wp-admin/edit-tags.php?taxonomy=category0.183 s0.182 s-0.001 s3.69 MiB3.7 MiB+ 12.75 KiB
/wp-admin/post-new.php?post_type=page0.911 s0.582 s-0.329 s5.54 MiB3.83 MiB- 1.71 MiB
/wp-admin/options-discussion.php0.241 s0.176 s-0.065 s3.6 MiB3.67 MiB+ 76.16 KiB
/wp-admin/edit-comments.php0.210 s0.196 s-0.014 s3.7 MiB3.71 MiB+ 11.66 KiB
/0.270 s0.186 s-0.084 s3.61 MiB3.57 MiB- 38.96 KiB
Average 0.372 s0.305 s-0.066 s4.01 MiB3.72 MiB- 302.19 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
Sass
CSS
Language % Lines of code Comment lines Files
PHP59.6%4302312
Sass18.2%13102
CSS15.7%11391
JavaScript6.5%4702
Total 721 32 17

PHP Code Analysis | More results »

Lines of code 224
Total complexity 44
Median class complexity 6.5
Median method complexity 2.0
Most complex class GRIM_CEW\Gutenberg
Most complex function GRIM_CEW\Gutenberg::show_edit_links()
Classes 4
Methods 24
Functions 0

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.

No new entries found.

PHP Error Log 6 lines

[02-Sep-2022 17:42:11 UTC] PHP Notice:  Function wp_dequeue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>wp-block-library</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5831
[02-Sep-2022 17:42:11 UTC] PHP Notice:  Function is_feed was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. 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 3.1.0.) in /wp-includes/functions.php on line 5831
[02-Sep-2022 17:42:11 UTC] PHP Notice:  Function wp_dequeue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>wp-block-library-theme</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5831
[02-Sep-2022 17:42:16 UTC] PHP Notice:  Function wp_dequeue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>wp-block-library</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5831
[02-Sep-2022 17:42:16 UTC] PHP Notice:  Function is_feed was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. 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 3.1.0.) in /wp-includes/functions.php on line 5831
[02-Sep-2022 17:42:16 UTC] PHP Notice:  Function wp_dequeue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>wp-block-library-theme</code> handle. 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 3.3.0.) in /wp-includes/functions.php on line 5831
See also: All tests for this plugin, How to Hide the "Classic Editor" Admin Menu