net

Now seeing similar error:

Uncaught TypeError: Cannot read properties of undefined (reading 'hooks')
    at 1434 (wpac-frontend-js.js?ver=2.2.0:2:26023)
    at o (wpac-frontend-js.js?ver=2.2.0:2:47649)
    at wpac-frontend-js.js?ver=2.2.0:2:47977
    at wpac-frontend-js.js?ver=2.2.0:2:47986
    at wpac-frontend-js.js?ver=2.2.0:2:47990

That’s the code:

var t = (0,
            window.wp.hooks.createHooks)();

‘transition_post_status’ action is the cause.

Need something to measure execution of hooks in production without turning off plugins.

Also found https://derrick.blog/2020/01/15/debugging-wordpress-hooks-speed/ but it doesn’t work properly.

Speed difference is 20x.

Actually the slowness has nothing to do with a object cache, it’s the same when it is enabled or disabled.

I guess some plugin is causing it, even though $fire_after_hooks parameter is set to false in wp_update_post call.

Any idea how to identify the bottleneck? Tried https://github.com/WPProfiler/core but for some reason it didn’t work properly with this Ajax call.

Default WP_REDIS_READ_TIMEOUT is 1 second:
https://github.com/rhubarbgroup/redis-cache/#configuration:~:text=WP_REDIS_READ_TIMEOUT

Don’t see any read timeout in redis.conf:
https://github.com/redis/redis/blob/unstable/redis.conf

PhpRedis default read timeout is 0 (disabled):
https://github.com/phpredis/phpredis?tab=readme-ov-file:text=readTimeout#:~:text=in%20milliseconds%20(optional)-,readTimeout,-%3A%20float%2C%20value%20in

What are the other consequences of raising WP_REDIS_READ_TIMEOUT to 10 seconds?

The situation with Yoast SEO version 22.2 is even worse:

[05-Mar-2024 09:36:46 UTC] RedisException: read error on connection to /var/run/redis/redis.sock in /home/wordpress/wp-content/object-cache.php:743
Stack trace:
#0 /home/wordpress/wp-content/object-cache.php(743): Redis->select()
#1 /home/wordpress/wp-content/object-cache.php(536): WP_Object_Cache->connect_using_phpredis()
#2 /home/wordpress/wp-content/object-cache.php(256): WP_Object_Cache->__construct()
#3 /home/wordpress/wp-includes/load.php(856): wp_cache_init()
#4 /home/wordpress/wp-settings.php(131): wp_start_object_cache()
#5 /home/wordpress/wp-config.php(128): require_once('...')
#6 /home/wordpress/wp-load.php(50): require_once('...')
#7 /home/wordpress/wp-blog-header.php(13): require_once('...')
#8 /home/wordpress/index.php(17): require('...')
#9 {main}

[05-Mar-2024 09:42:21 UTC] RedisException: socket error on read socket in /home/wordpress/wp-content/object-cache.php:1830
Stack trace:
#0 /home/wordpress/wp-content/object-cache.php(1830): Redis->eval()
#1 /home/wordpress/wp-content/object-cache.php(1730): WP_Object_Cache->{closure}()
#2 /home/wordpress/wp-content/object-cache.php(162): WP_Object_Cache->flush_group()
#3 /home/wordpress/wp-content/plugins/wordpress-seo/src/builders/indexable-link-builder.php(710): wp_cache_flush_group()
#4 /home/wordpress/wp-content/plugins/wordpress-seo/src/builders/indexable-link-builder.php(623): Yoast\WP\SEO\Builders\Indexable_Link_Builder->update_incoming_links_for_related_indexables()
#5 /home/wordpress/wp-content/plugins/wordpress-seo/src/builders/indexable-link-builder.php(136): Yoast\WP\SEO\Builders\Indexable_Link_Builder->update_related_indexables()
#6 /home/wordpress/wp-content/plugins/wordpress-seo/src/actions/indexing/abstract-link-indexing-action.php(65): Yoast\WP\SEO\Builders\Indexable_Link_Builder->build()
#7 /home/wordpress/wp-content/plugins/wordpress-seo/src/integrations/admin/background-indexing-integration.php(221): Yoast\WP\SEO\Actions\Indexing\Abstract_Link_Indexing_Action->index()
#8 /home/wordpress/wp-includes/class-wp-hook.php(324): Yoast\WP\SEO\Integrations\Admin\Background_Indexing_Integration->index()
#9 /home/wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#10 /home/wordpress/wp-includes/plugin.php(565): WP_Hook->do_action()
#11 phar:///home/wp/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(364): do_action_ref_array()
#12 phar:///home/wp/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(286): Cron_Event_Command::run_event()
#13 [internal function]: Cron_Event_Command->run()
#14 phar:///home/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func()
#15 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}()
#16 phar:///home/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(491): call_user_func()
#17 phar:///home/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(431): WP_CLI\Dispatcher\Subcommand->invoke()
#18 phar:///home/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(454): WP_CLI\Runner->run_command()
#19 phar:///home/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1269): WP_CLI\Runner->run_command_and_exit()
#20 phar:///home/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#21 phar:///home/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(83): WP_CLI\Bootstrap\LaunchRunner->process()
#22 phar:///home/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap()
#23 phar:///home/wp/php/boot-phar.php(20): include('...')
#24 /home/wp(4): include('...')
#25 {main}

[05-Mar-2024 09:42:21 UTC] RedisException: read error on connection to /var/run/redis/redis.sock in /home/wordpress/wp-content/object-cache.php:743
Stack trace:
#0 /home/wordpress/wp-content/object-cache.php(743): Redis->select()
#1 /home/wordpress/wp-content/object-cache.php(536): WP_Object_Cache->connect_using_phpredis()
#2 /home/wordpress/wp-content/object-cache.php(256): WP_Object_Cache->__construct()
#3 /home/wordpress/wp-includes/load.php(856): wp_cache_init()
#4 /home/wordpress/wp-settings.php(131): wp_start_object_cache()
#5 /home/wordpress/wp-config.php(129): require_once('...')
#6 /home/wordpress/wp-load.php(50): require_once('...')
#7 /home/wordpress/wp-blog-header.php(13): require_once('...')
#8 /home/wordpress/index.php(17): require('...')
#9 {main}

@tillkruess define( 'WP_REDIS_READ_TIMEOUT', 2 ); didn’t help.

@maybellyne @tillkruess found two function calls introduced in 22.1 that could be related to this issue:

\wp_cache_flush_group( ‘orphaned_counts’ )
https://github.com/Yoast/wordpress-seo/commit/511b71efe351840269eb2c5c484ef7158f2ac086#diff-3b3c3fe90f75b2e93fe8ed4d29c14aebd7f0924f5b198c9cea29f9ccbce90b86R722

\wp_cache_delete( ‘orphaned_count_’ . $post_type )
https://github.com/Yoast/wordpress-seo/commit/511b71efe351840269eb2c5c484ef7158f2ac086#diff-3b3c3fe90f75b2e93fe8ed4d29c14aebd7f0924f5b198c9cea29f9ccbce90b86R727

@ronalfy any update on this? Thanks.

I have reached out to Redis Object Cache plugin developer, but obviously there is some code change introduced in Yoast SEO version 22.1 that has something to do with this?

Great, many thanks for your help @freemp!

That worked, many thanks! Will you include it in the next update?

Nope, it’s the same.

@nextscripts any plans to fix this?

That’s great, thank you!

It is also important to use wp_head with higher priority than header code block is using, so blacklist shortcode can execute first.

I think this question and answer should be added to FAQ.

I understand that Black and White Lists are per block, so would need to add 200 post ids to black list to every block?

Is there some general black list to avoid doing that and to avoid editing each post just to add shortcode?

Thanks Ronald, I think it is more visible this way.

Now not sure about previous suggestion for centering it inside the comment form, since this form is not necessarily visible on screen if user scrolls too much.

Maybe to display the message below Submit button, like Contact Form 7 does, and leave it there, instead of fading out from the screen.