fromsly changed the title to Important discovery: unable to search Chinese. .

Littlegolden yes i do it without ui operation at the first time.And I also confirmed the result through MYADMIN.

post - content is ok too.

Littlegolden
still can't search chinese ,is there something wrong with "my.ini" help me find out?


[client]
#绑定IPv4和3306端口
bind-address = 120.76.77.119
port = 3306

[mysql]
no-beep

# default-character-set=
default-character-set=utf8
[mysql.server]
default-character-set=utf8
[mysql_safe]
default-character-set=utf8
[mysqld]
port=3306
ngram_token_size=2
sql_mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION"
default_storage_engine=innodb

# mysql根目录
basedir="e:\mysql\"

# 放所有数据库的data目录
datadir="e:\\mysql\\data"
character-set-client-handshake = false
character-set-server = utf8
init_connect='SET NAMES utf8'
# character-set-server=

# 默认存储引擎innoDB
default-storage-engine=INNODB

# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

#日志输出为文件
log-output=FILE

# 是否开启sql执行结果记录,必须要设置general_log_file参数,日志的路径地址
# 即日志跟踪,1为开启,0为关闭
general-log=1
general_log_file="execute_sql_result.log"

# 配置慢查询,5.7版本默认为1
slow-query-log=1
slow_query_log_file="user-slow.log"
long_query_time=10

#默认不开启二进制日志
#log-bin=mysql-log

#错误信息文件设置,会将错误信息放在data/mysql.err文件下
log-error=mysql.err

# Server Id.数据库服务器id,这个id用来在主从服务器中标记唯一mysql服务器
server-id=1

#lower_case_table_names: 此参数不可以动态修改,必须重启数据库
#lower_case_table_names = 1  表名存储在磁盘是小写的,但是比较的时候是不区分大小写
#lower_case_table_names=0  表名存储为给定的大小和比较是区分大小写的 
#lower_case_table_names=2, 表名存储为给定的大小写但是比较的时候是小写的
lower_case_table_names=1

#限制数据的导入导出都只能在Uploads文件中操作,这个是在sql语句上的限制。
#secure-file-priv="D:\AppServ\mysql-5.7.23/Uploads"
#值为null ,也就是注释掉这个参数或者secure-file-priv=null。表示限制mysqld 不允许导入|导出
#值为/tmp/ ,即secure-file-priv="/tmp/" 表示限制mysqld 的导入|导出只能发生在/tmp/目录下
#没有具体值时,即secure-file-priv=      表示不对mysqld 的导入|导出做限制

# 最大连接数
max_connections=600
# 打开表的最大缓存数
table_open_cache=2000

# tmp_table_size 控制内存临时表的最大值,超过限值后就往硬盘写,写的位置由变量 tmpdir 决定 
tmp_table_size=16M

# 每建立一个连接,都需要一个线程来与之匹配,此参数用来缓存空闲的线程,以至不被销毁,
# 如果线程缓存中有空闲线程,这时候如果建立新连接,MYSQL就会很快的响应连接请求。
# 最大缓存线程数量
thread_cache_size=10

#*** INNODB Specific options InnoDB存储引擎的配置

# InnoDB表的目录共用设置。没有在 my.cnf 进行设置,InnoDB 将使用MySQL的 datadir 目录为缺省目录。
# 如果设定一个空字串,可以在 innodb_data_file_path 中设定绝对路径
#innodb_data_home_dir=

# 通常设置为 1,意味着在事务提交前日志已被写入磁盘, 事务可以运行更长以及服务崩溃后的修复能力。
# 如果你愿意减弱这个安全,或你运行的是比较小的事务处理,可以将它设置为 0 ,以减少写日志文件的磁盘 I/O。
innodb_flush_log_at_trx_commit=1

# InnoDB 将日志写入日志磁盘文件前的缓冲大小
innodb_log_buffer_size=1M

# InnoDB 用来高速缓冲数据和索引内存缓冲大小。
innodb_buffer_pool_size=1000M

innodb_log_file_size=48M

# InnoDB 会试图将 InnoDB 服务的使用的操作系统进程小于或等于这里所设定的数值。默认为8
innodb_thread_concurrency=9

innodb_autoextend_increment=64
innodb_buffer_pool_instances=8
innodb_concurrency_tickets=5000
innodb_old_blocks_time=1000
innodb_open_files=300
innodb_stats_on_metadata=0
innodb_file_per_table=1
innodb_checksum_algorithm=0

back_log=80
flush_time=0
join_buffer_size=256K
max_allowed_packet=4M
max_connect_errors=100
open_files_limit=4161
sort_buffer_size=256K
table_definition_cache=1400
binlog_row_event_max_size=8K
sync_master_info=10000
sync_relay_log=10000
sync_relay_log_info=10000

note: base on mysql5.7.28
PHP extensions all ready,Mysql has been upgraded from 5.6 to 5.7,so i guest,someting wrong with my.ini.anyone knows?thank you!

vmomenv vmomenv please use English as per our community guidelines. You may include both Chinese and a translation in English if you want. The developers can't follow what's being discussed if we can't understand, and I think it's particularly important that we can follow this thread to act on the suggestions. Thanks.

    clarkwinkelmann
    I've been testing on two servers and trying to reinstall MYSQL several for many times and days ,The above chinese friend's test results are the same as mine, only part of the content can be retrieved,not all. The number of users in China has been increasing...We hope that this problem can be solved .Thank you.sir!

      samtto is it still about the minimum number of characters, or a different issue ?

      We are all for fixing the issues, but we will need concrete, reproducible bug reports. There's also a big question of whether the issue is Flarum, PHP or MySQL related. If you are certain an issue is related to Flarum core, please open issues on GitHub with specific steps to reproduce, and if possible suggestions on what part of the code will need changes.

      If it's related to PHP or MySQL configuration, it would be great to open a discussion under resource with the configuration steps, so that we can get user feedback and then integrate them in the official documentation.

      Also keep in mind mind the search is not perfect for English either. We made compromises between functionality and performance in order to have something that returns most expected results, while still being fast . In the next updates we will try to make it easier for third-party search plugins so that you can use other search technologies to index the forum outside of MySQL, like ElasticSearch, Algolia and others. There's only so much that can be done in MySQL alone.

        clarkwinkelmann
        Due to lacking of knowledge, I can only stand in the user's position to find my own problems,I'm sure flarum will get better and better and look forward to seeing the next version update bring a better search experience. I am trying to set up the centos7 system to run flarum with vps (localed in America) in order ,to eliminate various influences of environment, I am busy recently, I will try it later.
        The following sites do not have these problems
        @Csineneo https://vivaldi.club/
        https://bbs.towerlight.top/
        https://freeerror.org/

          samtto I have an idle server. If you are free, you can try to copy your server over. Then I will take a look at what went wrong.

            clarkwinkelmann sure
            I tried to change the database, but the Chinese search is not perfect, there are many contents still can not be indexed

            Littlegolden
            I have sent my server account information to you, help to see what problem, thank you!