-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling MySQL 4-byte support doesn't work #15974
Comments
Looks like a duplicate of #15058
Why do you enable utf8mb4 then?
The message is a warning shown for administrators. If it's not possible for you to enable utf8mb4 ignore it and look for another hosting in the long run (or ask your provider to fix it). Did you ask all-inkl (the usually suffix their php version with nmmX) to enable utf8mb4? @nextcloud/server-triage @jancborchardt mind to have a look at this kind of issues? The technical point is clear but many people are running into the same problem. They see some kind of message and follow the documentation to fix it. The fact that some messages are more or less important is not clear. |
I'm guessing this is an issue with the |
@skjnldsv: I can't change the config or restart the server. |
@kesselb: Because Nextcloud recommends it. |
When you say you can't, this is because the server is managed by someone else? |
Do you have a screenshot of how the error appears? We do have a priority of errors (red) and warnings (yellow) and notices (regular text color) in the admin overview, so that is a bit of an indicator of what is mroe and less important, no? So is it an issue with this message not being in the correct priority level? |
I'm not sure 🤔 Warning seems appropriate to me because some things does not work (like files or comments with emoji). Classified most of theses issues as duplicate of #15058. I suspect that people see the warning, head over to the documentation, skip the change server settings and restart server step (not possible because shared hosting), do the next steps and report an issue then. Don't know how people comes up with the idea that step 3+ work if they leave out step 1 or 2. We could add some warning to the documentation like "If you can't change your server settings don't enable utf8m4 ..." |
Most providers change this for you, if you ask for it.
I think notice is totally correct here, due to the reasons named by kesselb. If you accidently add an emoji in a calendar event or something your events will not sync anymore... |
If using Emojis causes stuff to not sync then I would class it as warning (or even error), not just as a notice. As adding emoji somewhere is not something people do accidentally, or rarely. |
Exactly, warning is yellow (which it is). notices are "black" (normal) text. |
Steps to reproduce
I followed the steps fpr MySQL described here: https://docs.nextcloud.com/server/latest/admin_manual/configuration_database/mysql_4byte_support.html
Expected behaviour
The administration and the News plugin stop telling me to change collation.
Actual behaviour
It fails in step 5 while changing collation for nc_addressbooks:
I can't change the config for MySQL... so the solutions that I found regarding some innodb-settings don't work for me.
Server configuration
Operating system: Linux 4.4.0-148-generic #174-Ubuntu SMP Tue May 7 12:20:14 UTC 2019 x86_64
Webserver: Apache (fpm-fcgi)
Database: mysql 5.6.44
PHP version: 7.3.6-nmm1
Modules loaded: Core, date, libxml, openssl, pcre, zlib, bcmath, bz2, calendar, ctype, dom, hash, filter, ftp, gettext, SPL, iconv, json, mbstring, posix, Reflection, session, standard, shmop, SimpleXML, soap, exif, sysvsem, sysvshm, tokenizer, wddx, xml, xmlreader, xmlwriter, zip, cgi-fcgi, propro, raphf, http, mysqlnd, PDO, curl, dba, fileinfo, gd, gender, gmp, htscanner, imagick, imap, interbase, intl, ldap, mongodb, mysqli, OAuth, odbc, pdo_dblib, pdo_mysql, PDO_ODBC, pdo_pgsql, pdo_sqlite, pgsql, Phar, pspell, recode, sodium, sqlite3, tidy, xsl, ionCube Loader, Zend OPcache
Nextcloud version: 16.0.1 - 16.0.1.1
Updated from an older Nextcloud/ownCloud or fresh install:
Where did you install Nextcloud from: unknown
Signing status
Array ( )
List of activated apps
Enabled:
Disabled:
Configuration (config/config.php)
{
"instanceid": "REMOVED SENSITIVE VALUE",
"passwordsalt": "REMOVED SENSITIVE VALUE",
"secret": "REMOVED SENSITIVE VALUE",
"trusted_domains": [
"REMOVED SENSITIVE VALUE",
"ssl-account.com"
],
"datadirectory": "REMOVED SENSITIVE VALUE",
"dbtype": "mysql",
"version": "16.0.1.1",
"dbname": "REMOVED SENSITIVE VALUE",
"dbhost": "REMOVED SENSITIVE VALUE",
"dbtableprefix": "oc_",
"dbuser": "REMOVED SENSITIVE VALUE",
"dbpassword": "REMOVED SENSITIVE VALUE",
"installed": true,
"forcessl": true,
"theme": "",
"maintenance": false,
"log_type": "syslog",
"logfile": "/www/htdocs/w00e5b01/nextcloud.log",
"loglevel": "2",
"logdateformat": "F d, Y H:i:s",
"trashbin_retention_obligation": "auto",
"mail_smtpmode": "smtp",
"mail_smtpsecure": "tls",
"mail_domain": "REMOVED SENSITIVE VALUE",
"mail_from_address": "REMOVED SENSITIVE VALUE",
"updater.release.channel": "stable",
"overwrite.cli.url": "REMOVED SENSITIVE VALUE",
"mail_smtpauthtype": "LOGIN",
"app_install_overwrite": [
"mail"
],
"mysql.utf8mb4": true
}
External storages: yes
External storage configuration
No mounts configured
Encryption: yes
User-backends:
Browser: Firefox 67.0
The text was updated successfully, but these errors were encountered: