Mysql error # 1118 Row size too large

Hello,

I am getting a Mysql # 1118 error "Row size too large (>8126)" when I try to save an Event for which I have created several custom messages in 4 languages. The strange thing is that the error occurs on my remote server, but not on the (development) server at home. Would this be due to a configuration setting in Mysql or is there a setting somewhere in EB to create a workaround?

Thanks

Karel

I did a quick google search for your error message... I'm not a mySQL guru, but the mySQL docs page ( dev.mysql.com/doc/mysql-reslimits-excerp...umn-count-limit.html -- see the last bullet point and example on the page ) says something about this error being the result of innodb_strict_mode being enabled (SET SESSION innodb_strict_mode=1;).
My guess is that your local server does not have innodb_strict_mode set, whereas your remote server does. If you have some sort of global mySQL option setting on your server, your might be able to override there, or ask for hosting company for help. Also, you can try enabling this on your local server to see if you get the same error message.

If @Tuan has a better solution, I'm sure he'll tell you how to fix it later today or tomorrow

Hello

Please try to login to administrator area of your site, then access to the two urls below to see whether it solves the issue:

domain.com/administrator/index.php?optio...sk=tool.fix_row_size

domain.com/administrator/index.php?optio...k=tool.fix_row_size2

Of course domain.com needs to be replaced with URL of your site

Regards,

Tuan

Thanks for the fixes . They seem to work on my local server, but when I create a backup of the site with Akeeba and then try to restore it on a remote server, the database restoration keeps failing on an 1118 error.

The row issue only occurs with the jos_eb_events table as that is the one where I have added a number of multi-line custom messages in 4 different languages. I have set the row size to dynamic for this particular table and now at least changes to the content are not rejected on the remote server. Backung up remotely works OK, but restoring the database remotely continues to fail on an 1118 error and that worries me a bit.

Maybe you should run the URLs/Tools which I sent earlier directly on server?

Tuan

The problem was finally solved with the help of my provider. They changed the innodb global file format settings to BARRACUDA and the ROW_SIZE of the jos_eb_events table was set to DYNAMIC. innodb_strict_mode was turned OFF.

Editing the content as well as backing up and restoring the database now works OK.

I don't know whether you people can fix this from within EB, or at least issue a warning that certain mysql parameters are required for EB to work properly. The table content that has caused the problem to begin with (in 4 different languages) is nothing abnormal if one wants to provide users with adequate information.

Hi Karel

This is something we could not fix from EB or if we want to fix it, we will have to change the way data is stored for multilingual website (currently, for each additional language, we have to add some extra fields to store data for that language into the table and in case you have more languages with many data, it could cause the problem)

For now, please use the solution provided by your host. Thanks for sharing back the result

Regards,

Tuan