View Issue Detail

ID	Project	Category	Submitted / Last Updated
01059	UserSpice	Misc	2020-11-09 08:04:38 / 2021-05-21 18:19:25
Reported	Cory	Assigned To	Unassigned
Priority	none	Reported	5.2.2
Status	closed	Resolution Version and Commit
Summary	Updating to 5.2.0
Description	When I ran the updater because my database was out of date, I got an error &quot;Failed to add container_open_class column to settings table&quot;. So I manually ran &quot;ALTER TABLE settings ADD COLUMN container_open_class varchar(255) NULL DEFAULT &#039;container-fluid&#039;&quot; using phpmyadmin, which gave me this error #1118 - Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs I don&#039;t really know enough to say if this is just an oddity with my host or a default for MariaDB but figured I would report it here just in case it isn&#039;t. If it is just an issue with my host, what would you suggest I do?

November 2021

Thanks for this. I'm looking into it?
November 2021

So I ran in to other problems relating to this same issue, there are a few settings I can change to fix this, but for now I just changed some of the type lengths for some columns that seemed larger then needed in both my settings and users tables, (ex site_name from varchar(255) to varchar(50), can't imagine I will need it larger), I was considering just changing them to text but I don't know enough about databases and your code to know if that could cause any other issues.  So other issues I ran into besides the one when updating UserSpice was also when I installed plugins that attempted to add settings to both my settings and users table. More details on the issue below. https://stackoverflow.com/questions/22637733/mysql-error-code-1118-row-size-too-large-8126-changing-some-columns-to-tehttps://stackoverflow.com/questions/15585602/change-limit-for-mysql-row-size-too-large
November 2021

I'm not sure what to do with this. Is it working now?
November 2021

Most users did not report this error and it ran without issues. I'll close this issue as a one-off and we can reference it if it comes up again.