Markdown editor not accessible in 7.0.2

hambier · September 8, 2020, 7:13pm

Ok, this was easier than expected:

I had a look at the source code referenced by @daniel.pan in another comment and concluded that the relevant table hasn’t been changed in quite some time and so the table definition given for base_filecomment should still be valid.
The hexadecimal parts are part of the original source code, so they should be left unchanged. (I have no idea, though, what their meaning is.)
Still no idea, but before dropping the table I looked around a bit to check that the table doesn’t hold any data. Here’s a shortened summary:

# mysql -u seafile -p          
Enter password:                              
Welcome to the MySQL monitor.  Commands end with ; or \g.

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| ccnet-db           |
| seafile-db         |
| seahub-db          |
+--------------------+

mysql> use seahub-db

mysql> show tables;
+-------------------------------------------+
| Tables_in_seahub-db                       |
+-------------------------------------------+
| abuse_reports_abusereport                 |
...
| base_dirfileslastmodifiedinfo             |
| base_filecomment                          |
| base_filecontributors                     |
| base_filediscuss                          |

mysql> select * from base_filecomment;
Empty set (0.01 sec)

mysql> describe base_filecomment
    -> ;
+-------------------------+--------------+------+-----+---------+----------------+
| Field                   | Type         | Null | Key | Default | Extra          |
+-------------------------+--------------+------+-----+---------+----------------+
| id                      | int(11)      | NO   | PRI | NULL    | auto_increment |
| repo_id                 | varchar(36)  | NO   | MUL | NULL    |                |
| parent_path             | longtext     | NO   |     | NULL    |                |
| repo_id_parent_path_md5 | varchar(100) | NO   | MUL | NULL    |                |
| item_name               | longtext     | NO   |     | NULL    |                |
| author                  | varchar(255) | NO   | MUL | NULL    |                |
| comment                 | longtext     | NO   |     | NULL    |                |
| created_at              | datetime     | NO   |     | NULL    |                |
| updated_at              | datetime     | NO   |     | NULL    |                |
| detail                  | longtext     | YES  |     | NULL    |                |
| resolved                | tinyint(1)   | NO   | MUL | 0       |                |
+-------------------------+--------------+------+-----+---------+----------------+

mysql> drop table base_filecomment;
Query OK, 0 rows affected (3.71 sec)

mysql> CREATE TABLE `base_filecomment` (
    ->   `id` int(11) NOT NULL AUTO_INCREMENT,
    ->   `author` varchar(255) NOT NULL,
    ->   `comment` longtext NOT NULL,
    ->   `created_at` datetime NOT NULL,
    ->   `updated_at` datetime NOT NULL,
    ->   `uuid_id` char(32) NOT NULL,
    ->   `detail` longtext NOT NULL,
    ->   `resolved` tinyint(1) NOT NULL,
    ->   PRIMARY KEY (`id`),
    ->   KEY `base_filecomment_uuid_id_4f9a2ca2_fk_tags_fileuuidmap_uuid` (`uuid_id`),
    ->   KEY `base_filecomment_author_8a4d7e91` (`author`),
    ->   KEY `base_filecomment_resolved_e0717eca` (`resolved`),
    ->   CONSTRAINT `base_filecomment_uuid_id_4f9a2ca2_fk_tags_fileuuidmap_uuid` FOREIGN KEY (`uuid_id`) REFERENCES `tags_fileuuidmap` (`uuid`)
    -> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.88 sec)

mysql> quit;

Now editing markdown files is fine expect for an annoying warning message “Editing files in this browser can lead to slight display problems.” (Firefox 80.0, Linux)