These settings are no longer required as they are guaranteed through
other coding standard tools.
Signed-off-by: Maurício Meneghini Fauth <mauricio@fauth.dev>
* Navigation menu automatically expands database if there is only one record
* Added a new configuration for auto-expanding navigation tree for single database
Signed-off-by: Eduard Karpiel <eduard@karpiel.sk>
Makes 'enable_drag_drop_import' as a separate configuration directive, removes it from group of $cfg['IMPORT'] directives.
Signed-Off-By: Lakshay arora <arora.lakshya123@gmail.com>
This commit-
Adds a configuration directive to toggle drag drop Import feature as requested in #13155
TODO:
1. Test it on multiple servers.
2. Disable javascript handlers for drag drop
Signed-Off-By: Lakshay arora <arora.lakshya123@gmail.com>
We can reuse and better cache locally the operations to avoid additional
roundtrip to server when changing settings.
Issue #13466
Issue #11688
Signed-off-by: Michal Čihař <michal@cihar.com>
The authentication logging is now configurable and can be set to log
into file.
Hopefully this will prevent DirectAdmin guys producing patches which
generate tons of warnings.
Fixes#13391
Signed-off-by: Michal Čihař <michal@cihar.com>
Share one directory for Twig cache, SHP import and file uploads.
The code now also validates the cache directory and creates it on the
fly, so it properly detects if the directory can not be used.
Also the documentation has been improved to document securing this
directory.
Fixes#13225Fixes#13226
Signed-off-by: Michal Čihař <michal@cihar.com>
This is getting more and more problematic these days as most of Linux
distributions ship MariaDB libraries, while many people run MySQL
servers. As MariaDB claims the protocol compatibility should stay, we
should not warn in this case.
Of course there is option to add this exception to the warning (so far
the exception is there only other way - when using MySQL libraries to
connect to MariaDB server), but we would be ignoring most cases already
and I think complete removal is better than adding exceptions.
Overall I don't think this warning is doing any good these days.
Signed-off-by: Michal Čihař <michal@cihar.com>
It is really not necessary as MySQL decides connection type rather based
on hostname than on anything else.
Signed-off-by: Michal Čihař <michal@cihar.com>
* the user set collation is now honored
* default value has been changed to utf8mb4
* it is downgraded to utf8 if server does not support it
Fixes#12826
Signed-off-by: Michal Čihař <michal@cihar.com>
