Hello,
Good day!
This is Neo again, and I hope this email finds you well.
As per further review, we found a database fatal errors with the Yoast
plugin in the PHP logs:
[Tue Apr 11 16:02:27.386735 2023] [proxy_fcgi:error] [pid 15146:tid
140462072559360] [client 180.190.27.62:0] AH01071: Got error 'PHP
message: WordPress database error Commands out of sync; you can't run
this command now for query SELECT * FROM aiheg_yoast_indexable
WHERE
object_type
= 'home-page' LIMIT 1 made by
WP_Fatal_Error_Handler->handle,
WP_Fatal_Error_Handler->display_error_template,
WP_Fatal_Error_Handler->display_default_error_template, wp_die,
_default_wp_die_handler, wp_robots, apply_filters('wp_robots'),
WP_Hook->apply_filters,
Yoast\\WP\\SEO\\Integrations\\Front_End\\WP_Robots_Integration->add_robots,
Yoast\\WP\\SEO\\Integrations\\Front_End\\WP_Robots_Integration->get_robots_value,
Yoast\\WP\\SEO\\Memoizers\\Meta_Tags_Context_Memoizer->for_current_page,
Yoast\\WP\\SEO\\Repositories\\Indexable_Repository->for_current_page,
Yoast\\WP\\SEO\\Repositories\\Indexable_Repository->find_for_home_page,
Yoast\\WP\\Lib\\ORM->find_one, Yoast\\WP\\Lib\\ORM->run,
Yoast\\WP\\Lib\\ORM::executePHP message: WordPress database error
Commands out of sync; you can't run this command now for query SELECT *
FROM aiheg_yoast_indexable
WHERE object_type
= 'home-page' LIMIT 1
made by WP_Fatal_Error_Handler->handle,
WP_Fatal_Error_Handler->display_error_template,
WP_Fatal_Error_Handler->display_default_error_template, wp_die,
_default_wp_die_handler, wp_robots, apply_filters('wp_robots'),
WP_Hook->apply_filters,
Yoast\\WP\\SEO\\Integrations\\Front_End\\WP_Robots_Integration->add_robots,
Yoast\\WP\\SEO\\Integrations\\Front_End\\WP_Robots_Integration->get_robots_value,
Yoast\\WP\\SEO\\Memoizers\\Meta_Tags_Context_Memoizer->for_current_page,
Yoast\\WP\\SEO\\Repositories\\Indexable_Repository->for_current_page,
Yoast\\WP\\SEO\\Repositories\\Indexable_Repository->find_for_home_page,
Yoast\\WP\\Lib\\ORM->find_one, Yoast\\WP\\Lib\\ORM->run,
Yoast\\WP\\Lib\\ORM::executePHP message: WordPress database error
Commands out of sync; you can't run this command now for query
\n\t\t\tSELECT MAX(p.post_modified_gmt) AS last_modified,
MIN(p.post_date_gmt) AS published_at\n\t\t\tFROM aiheg_posts AS
p\n\t\t\tWHERE p.post_status IN ('publish')\n\t\t\t\tAND p.post_password
= ''\n\t\t\t\tAND p.post_type = 'post'\n\t\t made by
WP_Fatal_Error_Handler->handle,
WP_Fatal_Error_Handler->display_error_template,
WP_Fatal_Error_Handler->display_default_error_template, wp_die,
_default_wp_die_handler, wp_robots, apply_filters('wp_robots'),
WP_Hook->apply_filters,
Yoast\\WP\\SEO\\Integrations\\Front_End\\WP_Robots_Integration->add_robots,
Yoast\\WP\\SEO\\Integrations\\Front_End\\WP_Robots_Integration->get_robots_value,
Yoast\\WP\\SEO\\Memoizers\\Meta_Tags_Context_Memoizer->for_current_page,
Yoast\\WP\\SEO\\Repositories\\Indexable_Repository->for_current_page,
Yoast\\WP\\SEO\\Repositories\\Indexable_Repository->find_for_home_page,
Yoast\\WP\\SEO\\Builders\\Indexable_Builder->build_for_home_page,
Yoast\\WP\\SEO\\Builders\\Indexable_Builder->bu...PHP message: WordPress
database error Commands out of sync; you can't run this command now for
query INSERT INTO aiheg_yoast_indexable
(object_type
, title
,
breadcrumb_title
, permalink
, blog_id
, description
,
is_robots_noindex
, open_graph_title
, open_graph_image
,
open_graph_image_id
, open_graph_description
,
open_graph_image_source
, open_graph_image_meta
,
object_published_at
, object_last_modified
, version
,
permalink_hash
, created_at
, updated_at
) VALUES ('home-page',
'Eventos y Conciertos en Costa Rica - adondeirhoy.com', 'Home',
'https://adondeirhoy.com/', '1', 'Sitio web #1 de conciertos en Costa
Rica. Informacion oficial de entretenimiento, eventos y conciertos en
Costa Rica', '0', '%%sitename%%', '', '0', '', NULL, NULL, NULL, NULL,
'2', '24:ed77d7bb502e15c255f471ce6a59927f', '2023-04-11 23:02:27',
'2023-04-11 23:02:27') made by WP_Fatal_Error_Handler->handle,
WP_Fatal_Error_Handler->display_error_template,
WP_Fatal_Error_Handler->display_default_error_templ...'
The Yoast table appears to be corrupted, which is causing the critical
error when the plugin is active. This is something you would need to look
into with the Plugin developers
]]>Help me please, how I can prevent post-sitemap partition or hide empty post-sitemaps from main sitemap?
I have 3 post sitemaps and 2 from them without posts, and I want to hide them
Thanks
]]>When check via browser still same.
What can I do?
Thank You
]]>Whats the issue? Any help appreciated.
]]>The rest seem to be working fine. Here’s what I have tried:
1. I disabled the plugin and re-enabled it.
2. I removed the plugin and reinstalled it.
3. I went to permalinks settings and clicked on ‘Save changes’
4. I turned the XML sitemaps button off and back on.
5. I tried loading these in a new “history-free” browser window.
Please let me know how to fix this.
Thanks.
When I try to access my post sitemap – it gives me 500 error.
https://www.coma.lv/sitemap_index.xml
Fatal error: Uncaught TypeError: Argument 2 passed to wp_permastructure::parse_permalinks() must be an instance of WP_Post, instance of stdClass given, called in /home3/coma/public_html/coma.lv/wp-includes/class-wp-hook.php on line 286 and defined in /home3/coma/public_html/coma.lv/wp-content/plugins/wp-permastructure/wp-permastructure.php:244 Stack trace: #0 /home3/coma/public_html/coma.lv/wp-includes/class-wp-hook.php(286): wp_permastructure->parse_permalinks(‘https://www.com…’, Object(stdClass), false) #1 /home3/coma/public_html/coma.lv/wp-includes/plugin.php(203): WP_Hook->apply_filters(‘https://www.com…’, Array) #2 /home3/coma/public_html/coma.lv/wp-includes/link-template.php(240): apply_filters(‘post_link’, ‘https://www.com…’, Object(stdClass), false) #3 /home3/coma/public_html/coma.lv/wp-content/plugins/wordpress-seo/inc/sitemaps/class-post-type-sitemap-provider.php(603): get_permalink(Object(stdClass)) #4 /home3/coma/public_html/coma.lv/wp-content/plugins/wordpress-seo/inc/sitemaps/class-post-type-sitemap-pr in /home3/coma/public_html/coma.lv/wp-content/plugins/wp-permastructure/wp-permastructure.php on line 244
]]>