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
Error when using MySQL Dump on some hosting provider.
Issue is from the argument "--protocol=tcp".
In /htdocs/core/class/utils.class.php line 298, the condition "if (!empty($dolibarr_main_db_port))" will never be empty.
If no value is put in conf.php for $dolibarr_main_db_port, it'll be set to 3306 by default so the condition in /htdocs/core/class/utils.class.php line 298 will never be empty.
Only option for now is to manually remove "--protocol=tcp" from line 299 in /htdocs/core/class/utils.class.php.
That resolve the issue but it's not clean.
Environment Version
17.0.2
Environment OS
Linux 4.18.0
Environment Web server
LiteSpeed 8.1
Environment PHP
8.1.18
Environment Database
MariaDB 10.5.19
Environment URL(s)
No response
Expected and actual behavior
No response
Steps to reproduce the behavior
No response
Attached files
No response
The text was updated successfully, but these errors were encountered:
Bug
Sorry for my english.
Error when using MySQL Dump on some hosting provider.
Issue is from the argument "--protocol=tcp".
In /htdocs/core/class/utils.class.php line 298, the condition "if (!empty($dolibarr_main_db_port))" will never be empty.
If no value is put in conf.php for $dolibarr_main_db_port, it'll be set to 3306 by default so the condition in /htdocs/core/class/utils.class.php line 298 will never be empty.
Only option for now is to manually remove "--protocol=tcp" from line 299 in /htdocs/core/class/utils.class.php.
That resolve the issue but it's not clean.
Environment Version
17.0.2
Environment OS
Linux 4.18.0
Environment Web server
LiteSpeed 8.1
Environment PHP
8.1.18
Environment Database
MariaDB 10.5.19
Environment URL(s)
No response
Expected and actual behavior
No response
Steps to reproduce the behavior
No response
Attached files
No response
The text was updated successfully, but these errors were encountered: