Strange error after upgrade to 1.11.5

  • Resolved José Luís

    (@jlcarneiro)


    7 years, 7 months ago

    Hi! I wasn’t having problems with 1.11.4 but after the latest update (to 1.11.5) the plugin gets DEactivated immediately and these three errors are added to my error_log file:

    [03-Aug-2017 13:41:56 UTC] Erro de banco de dados do WordPress Illegal mix of collations (utf8mb4_unicode_520_ci,IMPLICIT) and (utf8mb4_unicode_ci,IMPLICIT) for operation '=' para a consulta DELETE synch.*
				  FROM
					 wp_blc_synch AS synch
					 LEFT JOIN wp_posts AS posts
					 ON (synch.container_id = posts.ID and synch.container_type = posts.post_type)
				  WHERE
					 posts.post_status NOT IN ('publish') feita por activate_plugin, do_action('activate_broken-link-checker/broken-link-checker.php'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, blc_activation_hook, require('/plugins/broken-link-checker/includes/activation.php'), blcModuleManager->plugin_activated, blcModule->plugin_activated, blcContainerManager->activated, blcAnyPostContainerManager->resynch, blcPostTypeOverlord->resynch, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query

[03-Aug-2017 13:41:56 UTC] Erro de banco de dados do WordPress Illegal mix of collations (utf8mb4_unicode_520_ci,IMPLICIT) and (utf8mb4_unicode_ci,IMPLICIT) for operation '=' para a consulta UPDATE
					wp_blc_synch AS synch
					JOIN wp_posts AS posts ON (synch.container_id = posts.ID and synch.container_type=posts.post_type)
				  SET 
					synched = 0
				  WHERE
					synch.last_synch < posts.post_modified feita por activate_plugin, do_action('activate_broken-link-checker/broken-link-checker.php'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, blc_activation_hook, require('/plugins/broken-link-checker/includes/activation.php'), blcModuleManager->plugin_activated, blcModule->plugin_activated, blcContainerManager->activated, blcAnyPostContainerManager->resynch, blcPostTypeOverlord->resynch, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query

[03-Aug-2017 13:41:56 UTC] Erro de banco de dados do WordPress Illegal mix of collations (utf8mb4_unicode_520_ci,IMPLICIT) and (utf8mb4_unicode_ci,IMPLICIT) for operation '=' para a consulta INSERT INTO wp_blc_synch(container_id, container_type, synched)
				  SELECT posts.id, posts.post_type, 0
				  FROM 
				    wp_posts AS posts LEFT JOIN wp_blc_synch AS synch
					ON (synch.container_id = posts.ID and synch.container_type=posts.post_type)  
				  WHERE
				  	posts.post_status IN ('publish')
	 				AND posts.post_type IN ('page', 'post')
					AND synch.container_id IS NULL feita por activate_plugin, do_action('activate_broken-link-checker/broken-link-checker.php'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, blc_activation_hook, require('/plugins/broken-link-checker/includes/activation.php'), blcModuleManager->plugin_activated, blcModule->plugin_activated, blcContainerManager->activated, blcAnyPostContainerManager->resynch, blcPostTypeOverlord->resynch, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query

    I use PHP v5.6.31 and MySQL v10.0.31-MariaDB-cll-lve…

    What should I do?

Viewing 2 replies - 1 through 2 (of 2 total)

  • I have the same (shared hosting) web server set up as Jose Luse and appear to have continuing issues, of the server racing. I switched off the plug-in (by renaming folder) and switched back on site by site. Seemed to be OK with just the one switched on but the second produced high memory use, high number of processes, and IO use can also go high. (Currently still waiting for this to subside – hope it does very soon!). The second site relies on standard WP cron, while the first uses ‘WP-Cron Control’ plug-in. I am currently wondering whether this could be the cause. Or if there is another compatibility issue somewhere.

    • This reply was modified 7 years, 7 months ago by volresource.

    Further to my earlier post, as the server issue has re-occurred with BLC switched off, it seems to be down to the triggering of cron more generally, and not just for this plug-in. So please ignore my problem, for now at least.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Strange error after upgrade to 1.11.5’ is closed to new replies.