Database Error Duplicate Column Name

That’s strange. It seems like it’s trying to install the same table twice, while it should be installing the table for each of your sites, using a different prefix (e.g. wp_1_, wp_2_, etc.)

Have you tried disabling W3TC temporarily and installing the plugin? It might be that W3TC is caching the query.

After installing the plugin you can re-enable W3TC.

Thank you for the quick response. I will try that and let you know.

Thanks again.

The error is still there.

[Mon Sep 09 11:12:35.258685 2019] [proxy_fcgi:error] [pid 93916:tid 140650867562240] [client 202.14.12.94:51180] AH01071: Got error ‘PHP message: WordPress database error Duplicate column name ‘local’ for query ALTER TABLE wp_caos_webfonts ADD COLUMN local varchar(128) AFTER font_style; 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, hwlRunDbUpdates, hwlAddLocalColumn’

Please advise.

Then I’ll have to figure this out and replicate the issue on a local machine. Are you trying to install the plug-in from the Site Root or ‘within’ a site (if that’s even possible?)

from the site root and then configuring it within each site. i also tried deleting the plugin completely and dropping the tables from each site and reinstall same issue.

could it be a conflict with another plug in like caos local analytics. Please let me know as I have caos analytics running successfully on the site.

cheers

I have the same problem/error on WPEngine and multisite. Hope you find a solution soon.

Hi guys,

I found out that some extra steps are necessary to properly create the database tables in Multisite. I’ll release an update ASAP.

Apologies for the inconvenience.

Thanks, Perfect!

Hi @kristoffer132 and @unalgu,

To debug your issue I’ve setup a local environment using Multisite. To be honest, I couldn’t replicate this issue.

The only thing I can think off, is that it has something to do with your caching plugins or that your database prefix settings aren’t setup properly.

Before creating a new site in my environment, I:
– Disabled all plugins,
– Created the new site,
– Activated OMGF,
– Changed and saved the settings,
– ‘Download Fonts’,
– ‘Generate Stylesheet’.

Eerything was saved and generated correctly. To generate a different stylesheet for each site, I changed the cache-directory option, to /cache/site1/omgf, /cache/site2/omgf, etc. and downloaded the fonts and generate the stylesheet again.

Since OMGF depends entirely on WordPress wp_options-table and saving mechanisms, in a Multisite environment and depending on the site you’re managing, it always displays and saves the values correctly in the wp_options-table of the corresponding site. This could be wp_options, wp_2_options, etc. The same goes for OMGF’s table, called ‘caos_webfonts’, which will be created as wp_caos_webfonts, wp_2_caos_webfonts, etc.

So, in short, OMGF is already fully compatible with Multisite environments and I couldn’t find any code I’d have to change to increase compatibility.

What you could try, is Network Deactivating all plugins and activate only OMGF per site and configure it to your wishes. And if you have the possibility, try the steps I described above on a completely new site, with all plugins disabled, perhaps another plugin is interfering with the creation of tables.

Hi @kristoffer132 and @unalgu,

I think I fixed it! It was a bug, but it wasn’t related to Multisite ??

Please update to version 1.9.9, when I enabled WP_DEBUG on one of my environments all of the sudden this error popped up. So, it should be fixed now!