Hello.
First of all, this is written while translating Japanese.
Sorry if you don't get it.
[issue]
Multibyte characters cannot be searched in "host.php" used for device search.
If use multibyte, it will be converted to hexadecimal and will not work properly.
exam)"ytksn" => "%uFF59%uFF54%uFF4B%uFF53%uFF4E"
URL will then like this=> "~~/cacti/host.php?host_status=-1&host_template_id=-1&site_id=-1&poller_id=-1&location=-1&rows=-1&filter=%uFF59%uFF54%uFF4B%uFF53%uFF4E&"
In this case, directly specifying a normal string in the "filter" field of the URL will work correctly. (~~&filter=ytksn)
The other search screens are fine.(graphs.php, sites.php...)
Please let us know if there is any information you need.
Any help is welcome!
------------------------------------------------------------
Cacti Version 1.2.19
Cacti OS unix
Cannot use multibyte in host.php(1.2.19)
Moderators: Developers, Moderators
Re: Cannot use multibyte in host.php(1.2.19)
Still unresolved, don't know why.
Do I need to use an earlier version?
Or do I have to rewrite the source code?
Do I need to use an earlier version?
Or do I have to rewrite the source code?
Re: Cannot use multibyte in host.php(1.2.19)
Can you raise this as an issue on GitHub? https://github.com/cacti/cacti/issues
Also, make sure that you are using mb4 for each of the tables.
Also, make sure that you are using mb4 for each of the tables.
Cacti Developer & Release Manager
The Cacti Group
Director
BV IT Solutions Ltd
+--------------------------------------------------------------------------+
Cacti Resources:
Cacti Website (including releases)
Cacti Issues
Cacti Development Releases
Cacti Development Documentation
The Cacti Group
Director
BV IT Solutions Ltd
+--------------------------------------------------------------------------+
Cacti Resources:
Cacti Website (including releases)
Cacti Issues
Cacti Development Releases
Cacti Development Documentation
Re: Cannot use multibyte in host.php(1.2.19)
Dear netniV,
Thanks for the reply,
I posted it as an issue on GitHub.
As far as the database settings are concerned, it was set to utf8mb4.
Also, some of the settings were different, but we recognize that they are not a problem.
character_set_filesystem => binary
character_set_system => utf8
Thanks for the reply,
I posted it as an issue on GitHub.
As far as the database settings are concerned, it was set to utf8mb4.
Also, some of the settings were different, but we recognize that they are not a problem.
character_set_filesystem => binary
character_set_system => utf8
Re: Cannot use multibyte in host.php(1.2.19)
You really shoudl be using utf8mb if I remember rightly, not just utf8.
Cacti Developer & Release Manager
The Cacti Group
Director
BV IT Solutions Ltd
+--------------------------------------------------------------------------+
Cacti Resources:
Cacti Website (including releases)
Cacti Issues
Cacti Development Releases
Cacti Development Documentation
The Cacti Group
Director
BV IT Solutions Ltd
+--------------------------------------------------------------------------+
Cacti Resources:
Cacti Website (including releases)
Cacti Issues
Cacti Development Releases
Cacti Development Documentation
Re: Cannot use multibyte in host.php(1.2.19)
The installation wizard will display this.
------------------------------------------------------------
Server Collation
Your server collation appears to be UTF8 compliant
Database Collation
Your database default collation appears to be UTF8 compliant
Table Setup
All your tables appear to be UTF8 and Dynamic row format compliant
------------------------------------------------------------
We think it probably won't be a problem.
Also, it looks like it has been fixed on github, so I will wait for 1.2.20.
Thanks.
------------------------------------------------------------
Server Collation
Your server collation appears to be UTF8 compliant
Database Collation
Your database default collation appears to be UTF8 compliant
Table Setup
All your tables appear to be UTF8 and Dynamic row format compliant
------------------------------------------------------------
We think it probably won't be a problem.
Also, it looks like it has been fixed on github, so I will wait for 1.2.20.
Thanks.
Who is online
Users browsing this forum: No registered users and 3 guests