Open juluru06 opened 3 years ago
welcome[bot]
commented
3 years ago 👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
sklycorp
commented
3 years ago Can any one help me how to edit admin- Branding?
I am getting Server Error 500| Server Error
i got same error like this, i try to install/enable FileInfo extentions on my WHM cpanel, go to whm->Software->EasyApache4->php extentions and then search "fileinfo". enable it-preview-provision. done. refreshing my browser and that issue its gone. maybe if you use localhost, u can try to install fileinfo extentions, try this way https://www.php.net/manual/en/install.pecl.windows.php hope helping, sorry if i wrong, thnks goodluck.
efgait
commented
2 years ago Got the same issue, every time when saving a branding change I get a 500 Error. Version v5.3.7 - build 6587
Have you tried executing:
php artisan migrate
For me it fails with the following issue:
Migrating: 2019_04_06_060145_add_user_skin_setting
Illuminate\Database\QueryException : SQLSTATE[42000]: Syntax error or access violation: 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 (SQL: alter table users add skin varchar(191) null)
at /var/www/snipeit/vendor/laravel/framework/src/Illuminate/Database/Connection.php:669 665| // If an exception occurs when attempting to run a query, we'll format the error 666| // message to include the bindings with SQL, which will make this exception a 667| // lot more helpful to the developer instead of just the database's errors. 668| catch (Exception $e) {
669| throw new QueryException( 670| $query, $this->prepareBindings($bindings), $e 671| ); 672| } 673|
Exception trace:
1 Doctrine\DBAL\Driver\PDO\Exception::("SQLSTATE[42000]: Syntax error or access violation: 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") /var/www/snipeit/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDO/Exception.php:18
2 Doctrine\DBAL\Driver\PDO\Exception::new() /var/www/snipeit/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:114
3 PDOException::("SQLSTATE[42000]: Syntax error or access violation: 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") /var/www/snipeit/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:112
efgait
commented
2 years ago With debugging turned on I get the following additional details:
Illuminate\Database\QueryException thrown with message "SQLSTATE[42S22]: Column not found: 1054 Unknown column 'allow_user_skin' in 'field list' (SQL: update settings set site_name = mySite, brand = 1, skin = blue, allow_user_skin = ?, settings.updated_at = 2022-01-22 12:05:51 where id = 1)"
Stacktrace:
snipe
commented
2 years ago This issue has been discussed several times here. It's a database configuration issue.
https://github.com/snipe/snipe-it/search?q=row+size+too+large&type=issues
https://github.com/snipe/snipe-it/issues/9974#issuecomment-904036694 https://github.com/snipe/snipe-it/issues/9504#issuecomment-828760410 https://snipe-it.readme.io/docs/installation-issues#sqlstate42000-syntax-error-or-access-violation-1118-row-size-too-large
uberbrady
commented
2 years ago For the 'row size too large' error, a fix might work for you here: https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb/#converting-the-table-to-the-dynamic-row-format - specifically, run ALTER TABLE settings ROW_FORMAT=dynamic - then try and re-run migrations.
MariaDB KnowledgeBase
Fixing "Row size too large (> 8126). Changing some columns to TEXT or BLOB may help."
efgait
commented
2 years ago Thanks @snipe and @uberbrady for your speedy response and input, I have been able to complete the migration successfully after changing the row format for a couple of tables as suggest ALTER TABLE settings ROW_FORMAT=dynamic;. Flowing which I am able again to save branding changes; no more 500 Error. 😃
@juluru06 sorry for hijacking your post, hope you too will be able to resolve your problem soon.
Can any one help me how to edit admin- Branding?
I am getting Server Error 500| Server Error