• Resolved umitdursoy

    (@umitdursoy)


    Apache Error:

    Do I have to manually delete this table before install? “yoast_migrations”

    [Wed Apr 29 12:20:56.294081 2020] [proxy_fcgi:error] [pid 10798:tid 140372223002368] [client 172.69.185.19:32464] AH01071: Got error 'PHP message: require('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_Adapter_MySQL_TableDefinition->finish, Yoast\\WP\\Lib\\Ruckusing_Adapter->execute_ddl, Yoast\\WP\\Lib\\Ruckusing_Adapter->query taraf\xc4\xb1ndan olu\xc5\x9fturulan CREATE TABLELJf2yoast_migrations(\nidint(11) UNSIGNED auto_increment NOT NULL,\nversionvarchar(191),\n PRIMARY KEY (id)) DEFAULT CHARSET=utf8; sorgusu i\xc3\xa7in WordPress veritaban\xc4\xb1 hatas\xc4\xb1 Table 'ljf2yoast_migrations' already exists'

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter umitdursoy

    (@umitdursoy)

    I deleted manually that table. And I re-install plugin. Nothing change.

    [Wed Apr 29 12:36:05.616689 2020] [proxy_fcgi:error] [pid 10797:tid 140372256573184] [client 172.69.55.91:40716] AH01071: Got error ‘PHP message: require_once(‘wp-admin/admin.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->verify_environment, YoastSEO_Vendor\\Task_Db_Migrate->auto_create_schema_info_table, Yoast\\WP\\Lib\\Ruckusing_Adapter->create_schema_version_table, YoastSEO_Vendor\\Ruckusing_Adapter_MySQL_TableDefinition->finish, Yoast\\WP\\Lib\\Ruckusing_Adapter->execute_ddl, Yoast\\WP\\Lib\\Ruckusing_Adapter->query taraf\xc4\xb1ndan olu\xc5\x9fturulan CREATE TABLE LJf2yoast_migrations (\nversion varchar(255)) …’, referer: https://www.kamprota.com/wp-admin/index.php
    [Wed Apr 29 12:36:09.783567 2020] [proxy_fcgi:error] [pid 10797:tid 140372558710528] [client 172.69.55.91:50408] AH01071: Got error ‘PHP message: 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_Adapter_MySQL_TableDefinition->finish, Yoast\\WP\\Lib\\Ruckusing_Adapter->execute_ddl, Yoast\\WP\\Lib\\Ruckusing_Adapter->query taraf\xc4\xb1ndan olu\xc5\x9fturulan CREATE TABLE LJf2yoast_migrations (\nid int(11) UNSIGNED auto_increment NOT NULL,\nversion varchar(191),\n PRIMARY KEY (id)) DEFAULT CHARSET=utf8; sorgusu i\xc3\xa7in WordPress veritaban\xc4\xb1 hatas\xc4\xb1 Table ‘ljf2yoast_migrations’ already exists’, referer: https://www.kamprota.com/wp-admin/index.php
    [Wed Apr 29 12:36:18.307405 2020] [proxy_fcgi:error] [pid 10634:tid 140372466390784] [client 172.69.55.91:10284] AH01071: Got error ‘PHP message: 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_Adapter_MySQL_TableDefinition->finish, Yoast\\WP\\Lib\\Ruckusing_Adapter->execute_ddl, Yoast\\WP\\Lib\\Ruckusing_Adapter->query taraf\xc4\xb1ndan olu\xc5\x9fturulan CREATE TABLE LJf2yoast_migrations (\nid int(11) UNSIGNED auto_increment NOT NULL,\nversion varchar(191),\n PRIMARY KEY (id)) DEFAULT CHARSET=utf8; sorgusu i\xc3\xa7in WordPress veritaban\xc4\xb1 hatas\xc4\xb1 Table ‘ljf2yoast_migrations’ already exists’, referer: https://www.kamprota.com/wp-admin/admin.php?page=wpseo_dashboard

    It looks like it′s there last update that have fucked all our sites up

    This is happening because MySQL configured to convert table names to lower case.

    I think Migration_Runner::run_migrations() uses prefix set in wp-config to check if migration table exists.

    To solve the problem rename your migration table from ljf2yoast_migrations to LJf2yoast_migrations

    I’m getting this same error. I’m on a Windows host and unable to rename the tables… it keeps converting them back to lower case, no matter what I do.

    So, I got an idea to change wp-config and set the table_prefix value to all lower case. The front end works, but not the admin area. Now I get the message:

    “Sorry, you are not allowed to access this page.”

    However, when I changed the prefix back to what it had been, the error cleared and now it seems to be working OK, and I can get into the admin area again.

    Maybe this will help some other people get over the hump of that error.

    Usually, you can’t rename table name from lowercase to uppercase just like that.
    It will keep the previous name. To workaround that you need to rename it to something else and then rename to the name with an uppercase letters

    I did try that, ansky, but it didn’t work. It seems to be only lower-case table names allowed on our Windows server, which is not picky about case in most any situation. Very annoying!

    Thread Starter umitdursoy

    (@umitdursoy)

    It should not be Upper-case/lower-case issue. We are not using first time upper/lower-case Table name like this in our websites. There is no conflict with other plugins. But Yoast. ? No sir. I don’t change my table name.

    Thread Starter umitdursoy

    (@umitdursoy)

    Wait a second. I have checked my database. Whole table names in database already changed to lower-case. I didn’t do that. In my Wp-Config , my table prefix set both upper and lower case characters. I sync database table name with Wp-config prefix name. And then i will remove the table which are causing conflict. I will re-install Yoast. Probably it will work just like @ansky said.

    Emily @cleanup, to have mixed case letters on Windows you need to set MySQL option:
    lower_case_table_names=2, or maybe it is also your DB software is not allowing it.

    To check the setting value you can run the query: SELECT @@lower_case_table_names;

    But a simpler solution would just use lower case DB prefix in wp-config.php, just like umitdursoy said.

    In my case, I already had lower_case_table_names=2, and solving the problem was as easy as renaming the problematic table from lowercase to the name with uppercase letters. (But I had to rename it to something else first)

    Plugin Support devnihil

    (@devnihil)

    @umitdursoy Can you please try the following and let us know whether this resolves the issue?:

      1. Install & activate the?Yoast Test Helper plugin
      2. Go to Tools -> Yoast Test
      3. Hit the “Reset indexables & migrations” button
      4. Delete your current Yoast SEO installation.
      5. Reinstall Yoast SEO 14.0.4.
      6. Click the “Click here to speed up your site now” button.
    Thread Starter umitdursoy

    (@umitdursoy)

    I have changed charset and its ok now.

    Plugin Support devnihil

    (@devnihil)

    @umitdursoy Thanks for confirming that updating the charset has fixed the problem. We are going ahead and marking this issue as resolved. If you require any further assistance please create a new issue.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Database Error’ is closed to new replies.