Version 1.11.4 is broken

Hi folks.

Same thing with me: after upgrading, I am not able to access WP admin.

My PHP was updated last week to 7.1.3. So, it cann’t be a PHP version problem (at least in my case…).

I do not want to deactivate this plugin.

So, what can I do?

I commented the function cron_add_every_10_minutes, mentioned above, and the admin pages are available again.

I fear the plugin does not work now, beacuse of this. But it is still active.

WordPress supports PHP versions 5.2 and above… but versions prior to 5.5/5.6 are extremely old, and most plugins are now written to require v5.4 at a minimum, with some requiring v5.6.

This plugin seems to have previous versions available, using the WP Rollback plugin should work to revert back to v1.11.3 once v1.11.4 is deactivated.

While it’s best to ensure your website is running v5.6 or v7.x, and while you may have to change hosts to ensure that, the immediate need to have your site up might mean you need to simply avoid plugins with those newer requirements – rename their folders to deactivate them.

(In general, to find out which plugins are causing the issue, setting WP_DEBUG to true in the wp-config.php file using FTP or File Manager, and the full error should be displayed.)

If you’re running PHP v5.4 and above and still receiving an error, I would suggest you paste in the complete error message into a separate support thread, it may be different or unrelated to the latest version issue with PHP v5.3 and below.

Hi Rob

My error is the same the other guys reported:

This page isn’t working
xxxxxxxxxxx is currently unable to handle this request.
HTTP ERROR 500

The version 1.11.5 worked fine for me.

Has any one tested 1.11.5?

The issue has been fixed in version 1.11.5 which was released a few hours ago. I’ve tested it on my site and the plugin is now working perfectly again.

I just updated to BLC Version 1.11.5 and the issue is fixed!
Thank you!!
I also appreciate your comments about upgrading PHP and that is in the works – if it can be done.

Regards and thanks,
Angus

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?

• This reply was modified 7 years, 3 months ago by José Luís. Reason: typo