Answers.Body: <p>Suggestions from various folks on chat include the following settings in <code>my.cnf</code>:</p>
  
  <ul>
  <li><code>innodb_log_file_size</code> (<a href="https://stackoverflow.com/a/25373052">may be too small by default</a>)</li>
  <li><code>innodb_large_prefix=true</code></li>
  <li><code>innodb_file_format=barracuda</code></li>
  </ul>
  
  <p>I changed those and was still having issues. This setting fixed it for me (and may be due to the site running on MariaDB?).</p>
  
  <ul>
  <li><code>innodb_strict_mode=0</code></li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-08-07T15:58:46.330Z
Answers.LastActivityDate: 2019-08-07T15:58:46.330Z
Answers.UserDisplayName: Laryn
Answers.Body: <p>Also see <a href="https://civicrm.stackexchange.com/a/31644/225">https://civicrm.stackexchange.com/a/31644/225</a> where the suggested fix is:</p>
  
  <pre><code> ALTER TABLE civicrm_menu ROW_FORMAT=DYNAMIC 
  </code></pre>
  
  <p>Then rebuild the menus  </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-08-09T14:43:38.750Z
Answers.Text: Thanks! I just commented out the `innodb_strict_mode=0` setting as a test and performed this ALTER -- and it seems to fix it, too.
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-08-09T09:18:17.757Z
Answers.LastActivityDate: 2019-08-09T09:18:17.757Z
Answers.UserDisplayName: Aidan
Body: <p>I'm helping on a site that is on a different server than usual and see this error regularly in the back end when trying to complete various tasks (e.g. clear caches, run database updates, etc.) </p>
  
  <p><code>[debug_info] =&gt; TRUNCATE TABLE civicrm_menu [nativecode=1118 ** Row size too large (&gt; 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.]</code></p>
  
  <p>The site is mostly working, but as mentioned many tasks error out and the above shows in the debug log. What could cause this?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-08-07T23:07:44.140Z
Comments.Text: are they using multiple languages?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-08-08T13:46:39.710Z
Comments.Text: No, just English.
Comments.UserDisplayName: Laryn
Tags: <error><database><webserver>
Title: Database error when using CiviCRM admin UI: "Row size too large"
ThreadText: # Database error when using CiviCRM admin UI: "Row size too large"
  
  (Asked by: username_0 on 2019-08-07)
  
  I'm helping on a site that is on a different server than usual and see this error regularly in the back end when trying to complete various tasks (e.g. clear caches, run database updates, etc.)
  
  `[debug_info] => TRUNCATE TABLE civicrm_menu [nativecode=1118 ** Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.]`
  
  The site is mostly working, but as mentioned many tasks error out and the above shows in the debug log. What could cause this?
  
  **Tags:** error, database, webserver
  
  > **Comments:**
  > **username_1**: are they using multiple languages?  
  > **username_0**: No, just English.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2019-08-09. Score: 3 | Accepted answer
  
  Also see <https://civicrm.stackexchange.com/a/31644/225> where the suggested fix is:
  
  ```
   ALTER TABLE civicrm_menu ROW_FORMAT=DYNAMIC 
  
  ```
  
  Then rebuild the menus
  
  > **Comments:**
  > **username_0**: Thanks! I just commented out the `innodb_strict_mode=0` setting as a test and performed this ALTER -- and it seems to fix it, too.  
  
  ---
  
  ### Answer by username_0 on 2019-08-07. Score: 1
  
  Suggestions from various folks on chat include the following settings in `my.cnf`:
  
  * `innodb_log_file_size` ([may be too small by default](https://stackoverflow.com/a/25373052))
  * `innodb_large_prefix=true`
  * `innodb_file_format=barracuda`
  
  I changed those and was still having issues. This setting fixed it for me (and may be due to the site running on MariaDB?).
  
  * `innodb_strict_mode=0`
  
  
  ---
  
  