You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Make sure the following InnoDB settings are set on your MySQL server::
21
+
1. Make sure the following InnoDB setting is enabled on your database server::
19
22
20
23
[mysqld]
21
24
innodb_file_per_table=1
22
25
23
-
2. Restart the MySQL server in case you changed the configuration in step 1.
26
+
2. Restart the database server if you changed the configuration in step 1.
24
27
25
28
You can then verify that the change worked:
26
29
@@ -38,35 +41,50 @@ The result should look like this::
38
41
+-----------------------+-------+
39
42
1 row in set (0.00 sec)
40
43
41
-
3. Open a shell, change dir (adjust ``/var/www/nextcloud`` to your nextcloud location if needed), and put your nextcloud instance in maintenance mode, if it isn't already::
44
+
3. Open a shell, change to the Nextcloud installation directory (adjust
45
+
``/var/www/nextcloud`` as needed), and enable maintenance mode if it is not
Now you should be able to use Emojis in your file names, calendar events, comments and many more.
81
+
Nextcloud can now use the full range of Unicode characters - such as emojis - in file names,
82
+
calendar events, and comments.
69
83
70
84
.. note::
71
85
72
-
Also make sure your backup strategy still work. If you use ``mysqldump`` make sure to add the ``--default-character-set=utf8mb4`` option. Otherwise your backups are broken and restoring them will result in ``?`` instead of the emojis, making files inaccessible.
86
+
Make sure your backup strategy supports ``utf8mb4``. If you use
87
+
``mysqldump``, add the ``--default-character-set=utf8mb4`` option.
88
+
Otherwise, four-byte Unicode characters may not be preserved correctly
89
+
when the backup is restored. (A common symptom of this problem is the
90
+
appearance of ``?`` instead of emojis in text and file names).
0 commit comments