[Resolved] WP could not create a database table for address cache.

[Author]

Posts

[Daniel]

Hello Shane,

I turned over to PHP 7.3 instead of 7.2 but with no success.

Please find the WordPress debug.log at hidden link. I opened it a while during visiting the maps site.

I also attached you a screenshot of Query Monitor with lots of database errors of Toolset Maps.

Best, Daniel

[Shane]

Hi Daniel,

Have you tried to do it with all the non-toolset plugins disabled?

Your debug log doesn't give any information so it seems the issue isn't throwing a PHP error.

Please try with all the non-toolset plugins disabled.

Thanks,
Shane

[Daniel]

Hello Shane,

disabling the plugins had no effect. It doesn't work

I delete the table and toolset maps directly started refreshing the old cache and it works.

But I recognized something different.

My databse does not accept this syntax like described here:
https://toolset.com/forums/topic/wp-could-not-create-a-database-table-for-address-cache/#post-1281629

CREATE TABLE IF NOT EXISTS 'wpbebev_toolset_maps_address_cache' (
  'address_passed' varchar(190) COLLATE utf8mb4_unicode_ci NOT NULL,
  'address' varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  'point' point NOT NULL,
  PRIMARY KEY ('address_passed')
) DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

But it accepted this modified code, like in the example you gave me:

CREATE TABLE IF NOT EXISTS wpbebev_toolset_maps_address_cache (
  address_passed varchar(190) COLLATE utf8mb4_unicode_ci NOT NULL,
  address varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
  point point NOT NULL,
  PRIMARY KEY (address_passed)
) DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; 

MySQL information is attached as Screenshot.

Best, Daniel

[Shane]

Hi Daniel,

Happy to see that it works now but it is quite strange that your Database doesn't accept queries with the quotations in it

Either way the caching should still work now.

If there are any further issues on this please let me know.

Thanks,
Shane

[Daniel]

Hello Shane,

the problem is not resolved. The site is now running the old caching system again, which works without any problems.

I have the same issue on a multisite on a complete different environment (Plesk/Onyx 17.8), but maybe it's better closing the thread and waiting for the future .

Thanks for the patience.

Daniel

[Shane]

Hi Daniel,

I suspect its due to your database configuration.

Is your database hosted on a private server? or is it on a shared hosting service ?

It could be why its not accepting the queries with the quotes.

Thanks,
Shane

[Daniel]

Hi Shane,

it is a managed server at IONOS Germany, one of the biggest providers in Germany.

Best, Daniel

[Shane]

Hi Daniel,

Our team is aware of this database issue, they have posted an errata with another workaround that you can try on an alternative site to see if it helps.
https://toolset.com/errata/database-collation-error-when-using-toolset-maps/

Thanks,
Shane

[Daniel]

If I run this SQL I got an error too:

SQL-Befehl:

alter table wpbebev_postmeta convert to character set utf8mb4 collate utf8mb4_unicode_520_ci

MySQL meldet: Dokumentation
#1273 - Unbekannte Sortierreihenfolge: 'utf8mb4_unicode_520_ci'

[Shane]

Hi Daniel,

Could you let me know which version of MYSQL your database is using ?

Thanks,
Shane

[Daniel]

Yes of course. It is 5.5.60-0+deb7u1

[Shane]

Hi Daniel,

I see, your MYSQL version is actually below the version that we require.

Our minimum requirements are MySQL 5.6 and above.

IF possible could you try updating your version of MYSQL and let me know if the problem still remains.

There is a more permanent fix coming for this specific issue but upgrading would give me a good idea of what caused the issue if it is fixed.

Thanks,
Shane

[Daniel]

Hi Shane,

because it's a managed system I can't update system components. Thanks again for your patience. I'll look forward to the fixes.

Best, Daniel

[Shane]

Hi Daniel,

Well the caching still works just that it is using the older method which is still good.

Hopefully I would the update would fully resolve the issue. For now there is not much I can do but I do know that your SQL version is lower than the minimum requirements of wordpress as well.

Perhaps you can consult with the hosting provider about this to see what they have to say about the MySQL version because eventually you might run into issues with wordpress core as well.

Thanks,
Shane