in the error log in logs/mundolatas_com.php.error.log picks up php errors. This is the most striking and indicates that the table is missing _toolset_connected_elements which must be from the plugin toolset-blocks,
[08-Aug-2022 10:22:49 UTC] Error Table 'mundolat_db4.w47fa_toolset_connected_elements' doesn't exist de la base de datos de WordPress para la consulta SELECT group_id
FROM w47fa_toolset_connected_elements
WHERE element_id = 250470
AND domain = 'posts' realizada por edit_post, wp_update_post, wp_insert_post, do_action('save_post'), WP_Hook->do_action, WP_Hook->apply_filters, WPML_Admin_Post_Actions->save_post_actions, WPML_Post_Translation->after_save_post, WPML_Post_Translation->maybe_set_elid, SitePress->set_element_language_details, WPML_Set_Language->set, WPML_Set_Language->insert_new_row, do_action('wpml_translation_update'), WP_Hook->do_action, WP_Hook->apply_filters, OTGS\Toolset\Common\Relationships\MainController->OTGS\Toolset\Common\Relationships\{closure}, OTGS\Toolset\Common\Relationships\DatabaseLayer\Version2\Persistence\WpmlTranslationUpdate\WpmlTranslationUpdateHandler->on_wpml_translation_update, OTGS\Toolset\Common\Relationships\DatabaseLayer\Version2\Persistence\WpmlTranslationUpdate\WpmlTranslationUpdateHandler->one_element_action, OTGS\Toolset\Common\Relationships\DatabaseLayer\Version2\Persistence\WpmlTranslationUpdate\WpmlTranslationUpdateHandler->one_element_insert, OTGS\Toolset\Common\Relationships\DatabaseLayer\Version2\Persistence\ConnectedElementPersistence->get_element_group_by_element_id
[08-Aug-2022 10:36:01 UTC] Error Table 'mundolat_db4.w47fa_toolset_connected_elements' doesn't exist de la base de datos de WordPress para la consulta SELECT connected_elements.wpml_trid
FROM w47fa_icl_translations
AS translations
JOIN w47fa_icl_translations
AS source_translation
ON ( translations.trid = source_translation.trid )
JOIN w47fa_toolset_connected_elements
AS connected_elements
ON (
connected_elements.element_id = translations.element_id
AND connected_elements.domain = 'posts'
AND translations.element_type LIKE 'post_%'
)
WHERE source_translation.element_id = 250473
LIMIT 1
Hello. Thank you for contacting the Toolset support.
The first thing I would say here that you should take full backup of your database and files so if somehow any worst thing happen, you have backup to restore it.
Then I suggest you should share a staging site where I can review your current setup.
However, I will require some more information that would really help:
The error says that the Toolset table is not existing with the database. Are you using new post relationship? Have you created any post relationship? or have you migrated your site to new Toolset Types post relationship?
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
I checked and I see that you did not created any post relationship as I do not see any post relationship with post relationship listing page:
=> hidden link
First of all, I strongly suggest before taking any next steps, you should take full backup of your database.
It seems the database table is missing somehow on your database. You should try to create the database table using the following script:
CREATE TABLE IF NOT EXISTS `wp_toolset_connected_elements` (
`id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT,
`element_id` bigint(20) UNSIGNED NOT NULL,
`domain` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`wpml_trid` bigint(20) UNSIGNED DEFAULT NULL,
`lang_code` varchar(7) COLLATE utf8mb4_unicode_520_ci DEFAULT '',
`group_id` bigint(20) UNSIGNED NOT NULL,
PRIMARY KEY (`id`),
KEY `group_id` (`group_id`),
KEY `element` (`domain`,`element_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
Again, even I strongly suggest you should run this on staging site rather production site and once you see everything working as expected on staging site after running the above SQL script then you should perform the same steps on production site after taking full backup of your database.
