Does Front Page Scheduler work with WordPress 6.6.2 and PHP 8.1.12? A smoke test was performed on .
6 | PHP fatal errors |
No JavaScript exceptions | |
1 | Page failed to load
|
No resource errors |
Memory usage: 27.72 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.
WordPress version | 6.6.2 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 200+ |
WordPress.org page | https://wordpress.org/plugins/front-page-scheduler/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=front-page-scheduler%2Ffront-page-scheduler.php&plugin_status=all&paged=1&s&_wpnonce=6ae4b72e40 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.234 s |
Memory usage | 3.5 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 500 |
Load time | 0.046 s |
Memory usage | N/A |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.322 s | 0.275 s | -0.047 s | 3.47 MiB | 3.49 MiB | + 14.78 KiB |
/wp-admin/edit.php | 0.201 s | 0.177 s | -0.024 s | 3.54 MiB | 3.55 MiB | + 15.15 KiB |
/wp-admin/post-new.php | 0.720 s | 0.571 s | -0.149 s | 5.75 MiB | 5.77 MiB | + 19.45 KiB |
/wp-admin/upload.php | 0.524 s | 0.374 s | -0.150 s | 3.49 MiB | 3.49 MiB | - 2.26 KiB |
/wp-admin/options-writing.php | 0.374 s | 0.189 s | -0.185 s | 3.41 MiB | 3.47 MiB | + 60.55 KiB |
/wp-admin/media-new.php | 0.271 s | 0.210 s | -0.061 s | 3.4 MiB | 3.47 MiB | + 73.93 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.186 s | 0.325 s | +0.139 s | 3.47 MiB | 3.49 MiB | + 20.6 KiB |
/wp-admin/post-new.php?post_type=page | 0.559 s | 0.617 s | +0.058 s | 5.75 MiB | 5.76 MiB | + 15.04 KiB |
/wp-admin/options-discussion.php | 0.209 s | 0.238 s | +0.029 s | 3.41 MiB | 3.47 MiB | + 62.23 KiB |
/wp-admin/edit-comments.php | 0.220 s | 0.194 s | -0.026 s | 3.49 MiB | 3.49 MiB | - 2.27 KiB |
Average | 0.359 s | 0.317 s | -0.042 s | 3.92 MiB | 3.94 MiB | + 27.72 KiB |
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.
Language | % | Lines of code | Comment lines | Files | |
---|---|---|---|---|---|
PHP | 43.7% | 166 | 101 | 1 | |
JavaScript | 34.5% | 131 | 63 | 1 | |
PO File | 18.4% | 70 | 9 | 1 | |
Markdown | 3.4% | 13 | 0 | 1 | |
Total | 380 | 173 | 4 |
Lines of code | 166 |
---|---|
Total complexity | 48 |
Median class complexity | 48.0 |
Median method complexity | 3.0 |
Most complex class | front_page_scheduler |
Most complex function | front_page_scheduler::override_option_page_on_front() |
Classes | 1 |
---|---|
Methods | 10 |
Functions | 0 |
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.
[14-Sep-2024 22:00:34 UTC] PHP Fatal error: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, bool given in /wp-content/plugins/front-page-scheduler/front-page-scheduler.php:62
Stack trace:
#0 /wp-content/plugins/front-page-scheduler/front-page-scheduler.php(40): front_page_scheduler::override_option_page_on_front()
#1 /wp-includes/class-wp-hook.php(326): front_page_scheduler::override_option_show_on_front()
#2 /wp-includes/plugin.php(205): WP_Hook->apply_filters()
#3 /wp-includes/option.php(247): apply_filters()
#4 /wp-includes/class-wp-query.php(1036): get_option()
#5 /wp-includes/class-wp-query.php(1868): WP_Query->parse_query()
#6 /wp-includes/class-wp-query.php(3852): WP_Query->get_posts()
#7 /wp-includes/class-wp.php(696): WP_Query->query()
#8 /wp-includes/class-wp.php(816): WP->query_posts()
#9 /wp-includes/functions.php(1336): WP->main()
#10 /wp-blog-header.php(16): wp()
#11 /index.php(17): require('...')
#12 {main}
thrown in /wp-content/plugins/front-page-scheduler/front-page-scheduler.php on line 62
[14-Sep-2024 22:00:36 UTC] PHP Fatal error: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, bool given in /wp-content/plugins/front-page-scheduler/front-page-scheduler.php:62
Stack trace:
#0 /wp-content/plugins/front-page-scheduler/front-page-scheduler.php(40): front_page_scheduler::override_option_page_on_front()
#1 /wp-includes/class-wp-hook.php(326): front_page_scheduler::override_option_show_on_front()
#2 /wp-includes/plugin.php(205): WP_Hook->apply_filters()
#3 /wp-includes/option.php(247): apply_filters()
#4 /wp-includes/class-wp-query.php(1036): get_option()
#5 /wp-includes/class-wp-query.php(1868): WP_Query->parse_query()
#6 /wp-includes/class-wp-query.php(3852): WP_Query->get_posts()
#7 /wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(370): WP_Query->query()
#8 /wp-includes/rest-api/class-wp-rest-server.php(1230): WP_REST_Posts_Controller->get_items()
#9 /wp-includes/rest-api/class-wp-rest-server.php(1063): WP_REST_Server->respond_to_request()
#10 /wp-includes/rest-api/class-wp-rest-server.php(439): WP_REST_Server->dispatch()
#11 /wp-includes/rest-api.php(420): WP_REST_Server->serve_request()
#12 /wp-includes/class-wp-hook.php(324): rest_api_loaded()
#13 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#14 /wp-includes/plugin.php(565): WP_Hook->do_action()
#15 /wp-includes/class-wp.php(418): do_action_ref_array()
#16 /wp-includes/class-wp.php(813): WP->parse_request()
#17 /wp-includes/functions.php(1336): WP->main()
#18 /wp-blog-header.php(16): wp()
#19 /index.php(17): require('...')
#20 {main}
thrown in /wp-content/plugins/front-page-scheduler/front-page-scheduler.php on line 62
[14-Sep-2024 22:00:36 UTC] PHP Fatal error: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, bool given in /wp-content/plugins/front-page-scheduler/front-page-scheduler.php:62
Stack trace:
#0 /wp-includes/class-wp-hook.php(326): front_page_scheduler::override_option_page_on_front()
#1 /wp-includes/plugin.php(205): WP_Hook->apply_filters()
#2 /wp-includes/option.php(247): apply_filters()
#3 /wp-includes/capabilities.php(106): get_option()
#4 /wp-includes/class-wp-user.php(782): map_meta_cap()
#5 /wp-includes/capabilities.php(985): WP_User->has_cap()
#6 /wp-includes/capabilities.php(877): user_can()
#7 /wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(1742): current_user_can()
#8 /wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(977): WP_REST_Posts_Controller->check_delete_permission()
#9 /wp-includes/rest-api.php(835): WP_REST_Posts_Controller->delete_item_permissions_check()
#10 /wp-includes/class-wp-hook.php(324): rest_send_allow_header()
#11 /wp-includes/plugin.php(205): WP_Hook->apply_filters()
#12 /wp-includes/rest-api/class-wp-rest-server.php(462): apply_filters()
#13 /wp-includes/rest-api.php(420): WP_REST_Server->serve_request()
#14 /wp-includes/class-wp-hook.php(324): rest_api_loaded()
#15 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#16 /wp-includes/plugin.php(565): WP_Hook->do_action()
#17 /wp-includes/class-wp.php(418): do_action_ref_array()
#18 /wp-includes/class-wp.php(813): WP->parse_request()
#19 /wp-includes/functions.php(1336): WP->main()
#20 /wp-blog-header.php(16): wp()
#21 /index.php(17): require('...')
#22 {main}
thrown in /wp-content/plugins/front-page-scheduler/front-page-scheduler.php on line 62
[14-Sep-2024 22:00:40 UTC] PHP Fatal error: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, bool given in /wp-content/plugins/front-page-scheduler/front-page-scheduler.php:62
Stack trace:
#0 /wp-content/plugins/front-page-scheduler/front-page-scheduler.php(40): front_page_scheduler::override_option_page_on_front()
#1 /wp-includes/class-wp-hook.php(326): front_page_scheduler::override_option_show_on_front()
#2 /wp-includes/plugin.php(205): WP_Hook->apply_filters()
#3 /wp-includes/option.php(247): apply_filters()
#4 /wp-includes/class-wp-query.php(1036): get_option()
#5 /wp-includes/class-wp-query.php(1868): WP_Query->parse_query()
#6 /wp-includes/class-wp-query.php(3852): WP_Query->get_posts()
#7 /wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(370): WP_Query->query()
#8 /wp-includes/rest-api/class-wp-rest-server.php(1230): WP_REST_Posts_Controller->get_items()
#9 /wp-includes/rest-api/class-wp-rest-server.php(1063): WP_REST_Server->respond_to_request()
#10 /wp-includes/rest-api/class-wp-rest-server.php(439): WP_REST_Server->dispatch()
#11 /wp-includes/rest-api.php(420): WP_REST_Server->serve_request()
#12 /wp-includes/class-wp-hook.php(324): rest_api_loaded()
#13 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#14 /wp-includes/plugin.php(565): WP_Hook->do_action()
#15 /wp-includes/class-wp.php(418): do_action_ref_array()
#16 /wp-includes/class-wp.php(813): WP->parse_request()
#17 /wp-includes/functions.php(1336): WP->main()
#18 /wp-blog-header.php(16): wp()
#19 /index.php(17): require('...')
#20 {main}
thrown in /wp-content/plugins/front-page-scheduler/front-page-scheduler.php on line 62
[14-Sep-2024 22:00:40 UTC] PHP Fatal error: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, bool given in /wp-content/plugins/front-page-scheduler/front-page-scheduler.php:62
Stack trace:
#0 /wp-includes/class-wp-hook.php(326): front_page_scheduler::override_option_page_on_front()
#1 /wp-includes/plugin.php(205): WP_Hook->apply_filters()
#2 /wp-includes/option.php(247): apply_filters()
#3 /wp-includes/capabilities.php(106): get_option()
#4 /wp-includes/class-wp-user.php(782): map_meta_cap()
#5 /wp-includes/capabilities.php(985): WP_User->has_cap()
#6 /wp-includes/capabilities.php(877): user_can()
#7 /wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(1742): current_user_can()
(+32 more lines)