peterkay

add me to the update – btw this really crashed hard – the whole site bombed – took it offline.

Fixed! The root cause of my problem was that my wp_config had:

define(‘DB_COLLATE’, ‘utf8_unicode_ci’);

but there was no:
define(‘DB_CHARSET’, ‘utf8’);

so the fix was to have this in my wp_config:
define(‘DB_CHARSET’, ‘utf8’);
define(‘DB_COLLATE’, ‘utf8_unicode_ci’);

and on experimenting, this also worked:
define(‘DB_CHARSET’, ‘utf8’);
define(‘DB_COLLATE’, ”);

I’m glad I decided to spend more time on this and went to github to report the bug – they gave me the hint and apparently updated this thread too. Thanks guys! Hope this helps others.

ok @mazedulislamkhan and @devnihil I’ll put more time into this. I created a github bug:

https://github.com/Yoast/wordpress-seo/issues/15151

yeah, no thanks @devnihil . I’ve already spent hours on this issue. I’ll be uninstalling this plugin instead.

• This reply was modified 4 years, 10 months ago by peterkay.

@marcanor does this help? I have a much larger error file – LMK where to uplaod.

[Thu Apr 30 15:54:31.878965 2020] [php7:notice] [pid 10218] [client 98.150.153.227:63114] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘COLLATE utf8_unicode_ci /* From [aimforawestage.wpengine.com/wp-json/yoast/v1/st’ at line 1 for query ALTER TABLE wp_yoast_migrations CONVERT TO COLLATE utf8_unicode_ci /* From [aimforawestage.wpengine.com/wp-json/yoast/v1/statistics] in [/nas/content/live/aimforawestage/wp-content/plugins/wordpress-seo/lib/ruckusing-adapter.php:350] */ made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, wpseo_init, YoastSEO, Yoast\\WP\\SEO\\Main->load, Yoast\\WP\\SEO\\Loader->load, Yoast\\WP\\SEO\\Loader->load_initializers, Yoast\\WP\\SEO\\Initializers\\Migration_Runner->initialize, Yoast\\WP\\SEO\\Initializers\\Migration_Runner->run_free_migrations, Yoast\\WP\\SEO\\Initializers\\Migration_Runner->run_migrations, YoastSEO_Vendor\\Ruckusing_Task_Manager->execute, YoastSEO_Vendor\\Task_Db_Migrate->execute, YoastSEO_Vendor\\Task_Db_Migrate->prepare_to_migrate, YoastSEO_Vendor\\Task_Db_Migrate->run_migrations, AddCollationToTables->up, YoastSEO_Vendor\\Ruckusing_Migration_Base->query, Yoast\\WP\\Lib\\Ruckusing_Adapter->query, referer: https://aimforawestage.wpengine.com/wp-admin/index.php

@marcanor here’s what I just did and getting same “unable to create tables” error:

– Reset indexables & migrations
– Deleted Yoast (.03)
– Reset indexables & migrations
– Clear cdn cache
– Install yoast

I’m going to get w/ our host to get you error logs

Thank you @marcanor . I followed your steps and get the same result. This is on a site with no other plugin, using the Twenty Twenty theme.

Problem solved:

there reason why this occurred was because my server didn’t have a Mime-type for wmv files. By adding one line in my .htaccess file:

AddType video/x-ms-wmv .wmv

the WMV enclosures now works perfectly.

BTW: I found this out by stepping through the code. Very elegant, people! You rely on the server to classify audio/video codes to generate your enclosure entries. Nice work!

hmm…maybe this can help, when I use this:

https://www.votehawaii.com/index.php?feed=rss2

she works like a charm, in Pluck & Feed Validator.

However when I use this:
https://www.votehawaii.com/wp-rss2.php

I get errors all over the place, including “The system cannot locate the object specified. Error processing resource ‘https://www.votehawaii.com/wp-rss2.php’. “

so to me this smells like something is timing out on the rss2 page. Perhaps it’s related to a server setting that I’m not aware of or don’t have.

I’ve got a similar, weird problem. My rss feed at https://www.votehawaii.com/wp-rss2.php *seems* to be coming up ok in that I can pull it up in my browser

EXCEPT:

1. Pluck doesn’t like or recognize it. It errors out with a 404

2. The WEIRDEST of all is when I go to feedvalidator.org, it returns to me with a 404 error, yet when I feed it https://www.votehawaii.com, it comes back with “this looks like a web page”.

the 404 (page not found) error throws me off. it shows in my browser so it can’t be a 404, can it?