Err 1118 – Row size too large (> 8126)

Dear TeamKaeru,

We can do specific customization for you if you contact us at support[at]web-dorado.com. Thank you.

Hi, I appreciate the contact but this will end up being an issue for more than just myself. If there are others that are using your plugin for their galleries, they won’t be able to backup and restore the table that contains this row size and that’ll be a problem for them should something go wrong with their site.

Is it possible that it can be fixed for all? Or is this just a problem that only I have had?

Thanks!

Dear TeamKaeru,

This is not a common issue for our clients. This is coming from your server settings, that’s the reason we have asked you to contact us for customization. Thank you.

Dear Sona,

This is not an issue with TeamKaeru’s server settings. I have the same problem, and all the people running MySQL 5.7 will experience the same problem. Be prepared to receive more and more similar reports.

Your wp_bwg_theme table has WAY too many fields: 438 fields, which is a textbook case of bad design.

See this question for more information:
https://dba.stackexchange.com/questions/45837/mysql-row-size-too-large-8126

To quote the answer:

SUMMARY : Bill Karwin said it before and I agree: REDESIGN THE TABLE. That will circvumvent the row length issue for sure.

Please don’t blindly challenge the facts, and learn from the experts in the aforementioned thread: this table is poorly designed, and its contents should be split across several tables.

You might get away with switching the table engine to MyISAM (a pretty bad idea), or switching InnoDB to the Barracuda file format + switching to innodb_file_per_table + switching to ROW_FORMAT=DYNAMIC to get the options field data out of the row, which might save just enough space to fit in the 8126 bytes.

But that doesn’t change the facts. You cannot impose a specific database configuration to accommodate a bad design.

I would appreciate if you could fix this issue ASAP!

Kind regards,
Ben

Actually, after further investigation, ROW_FORMAT=DYNAMIC cannot help either.

Even without the LONGTEXT options field, the sum of all inline data for a row is 17059 bytes, which is way above the limit.

So as far as I can see, there is no configuration setting that can make this table work with MySQL 5.7. The quick-and-dirty way would be to change to ROW_FORMAT=DYNAMIC and change all VARCHARs to TEXT, so that no data is stored inline.

I would definitely recommend against manually modifying the structure of a plugin table, though.

The only solution is to fix the Photo Gallery plugin.

@ben,

Thank you for your notes. The issue with the client is somewhat different. The mentioned issue has already been resolved a few updates ago.

@sona Thanks for your reply.

Indeed, in the changelog, I can see: 1.2.76: Changed: Theme DB table structure.

But I’m running the latest version, 1.2.93, and still, the wp_bwg_theme table has this weird structure with 438 fields.

How is this possible?

Thanks in advance,
Ben

As far as I can see in the bwg_update.php file, your added an options field to store a json-encoded array of most of the other fields, but forgot to drop these obsolete fields, so the problem remains!

@benmorel,

We have preserved the structure for those clients who might have been using custom themes, but this doesn’t apply to new installs and we will soon even remove it from the coding. But if we have completely removed it all custom-theme based galleries would crash requiring fresh installation. Thank you.

@sona Can I safely remove these fields from the table then?
Won’t this crash the next update when you “officially” remove them?

@benmorel,

Yes, you can safely remove the fields from database. Thank you.

@sona Thank you for your reply!

@benmorel,

Thank you for using our plugin. If you face any further issues do not hesitate to contact us again. Thank you.

Seriously…

I registered to www.remarpro.com just to comment on this one.

I can’t believe it.

I can’t restore my database due to this incompetence.

That’s why I hate WordPress, a bunch of kiddies can improvise themselves at being web developers.

Thank you for your headache,

Sincerely

@mikegleasonjr: Why are you posting in a 4 month old, resolved, topic? And what does your problem have to do with this plugin?