All configurable data is placed in config.inc.php
in phpMyAdmin’s
toplevel directory. If this file does not exist, please refer to the
Installation section to create one. This file only needs to contain the
parameters you want to change from their corresponding default value in
libraries/config.default.php
(this file is not intended for changes).
See also
Examples for examples of configurations
If a directive is missing from your file, you can just add another line with
the file. This file is for over-writing the defaults; if you wish to use the
default value there’s no need to add a line here.
The parameters which relate to design (like colors) are placed in
themes/themename/scss/_variables.scss
. You might also want to create
config.footer.inc.php
and config.header.inc.php
files to add
your site specific code to be included on start and end of each page.
Note
Some distributions (eg. Debian or Ubuntu) store config.inc.php
in
/etc/phpmyadmin
instead of within phpMyAdmin sources.
Basic settings¶
-
$cfg['PmaAbsoluteUri']
¶ -
Type: string Default value: ''
Changed in version 4.6.5: This setting was not available in phpMyAdmin 4.6.0 — 4.6.4.
Sets here the complete URL (with full path) to your phpMyAdmin
installation’s directory. E.g.
https://www.example.net/path_to_your_phpMyAdmin_directory/
. Note also
that the URL on most of web servers are case sensitive (even on
Windows). Don’t forget the trailing slash at the end.Starting with version 2.3.0, it is advisable to try leaving this blank. In
most cases phpMyAdmin automatically detects the proper setting. Users of
port forwarding or complex reverse proxy setup might need to set this.A good test is to browse a table, edit a row and save it. There should be
an error message if phpMyAdmin is having trouble auto–detecting the correct
value. If you get an error that this must be set or if the autodetect code
fails to detect your path, please post a bug report on our bug tracker so
we can improve the code.
-
$cfg['PmaNoRelation_DisableWarning']
¶ -
Type: boolean Default value: false Starting with version 2.3.0 phpMyAdmin offers a lot of features to
work with master / foreign – tables (see$cfg['Servers'][$i]['pmadb']
).If you tried to set this
up and it does not work for you, have a look on the Structure page
of one database where you would like to use it. You will find a link
that will analyze why those features have been disabled.If you do not want to use those features set this variable to
true
to
stop this message from appearing.
-
$cfg['AuthLog']
¶ -
Type: string Default value: 'auto'
New in version 4.8.0: This is supported since phpMyAdmin 4.8.0.
Configure authentication logging destination. Failed (or all, depending on
$cfg['AuthLogSuccess']
) authentication attempts will be
logged according to this directive:auto
- Let phpMyAdmin automatically choose between
syslog
andphp
. syslog
- Log using syslog, using AUTH facility, on most systems this ends up
in/var/log/auth.log
. php
- Log into PHP error log.
sapi
- Log into PHP SAPI logging.
/path/to/file
- Any other value is treated as a filename and log entries are written there.
Note
When logging to a file, make sure its permissions are correctly set
for a web server user, the setup should closely match instructions
described in$cfg['TempDir']
:
-
$cfg['AuthLogSuccess']
¶ -
Type: boolean Default value: false New in version 4.8.0: This is supported since phpMyAdmin 4.8.0.
Whether to log successful authentication attempts into
$cfg['AuthLog']
.
-
$cfg['SuhosinDisableWarning']
¶ -
Type: boolean Default value: false A warning is displayed on the main page if Suhosin is detected.
You can set this parameter to
true
to stop this message from appearing.
-
$cfg['LoginCookieValidityDisableWarning']
¶ -
Type: boolean Default value: false A warning is displayed on the main page if the PHP parameter
session.gc_maxlifetime is lower than cookie validity configured in phpMyAdmin.You can set this parameter to
true
to stop this message from appearing.
-
$cfg['ServerLibraryDifference_DisableWarning']
¶ -
Type: boolean Default value: false Deprecated since version 4.7.0: This setting was removed as the warning has been removed as well.
A warning is displayed on the main page if there is a difference
between the MySQL library and server version.You can set this parameter to
true
to stop this message from appearing.
-
$cfg['ReservedWordDisableWarning']
¶ -
Type: boolean Default value: false This warning is displayed on the Structure page of a table if one or more
column names match with words which are MySQL reserved.If you want to turn off this warning, you can set it to
true
and
warning will no longer be displayed.
-
$cfg['TranslationWarningThreshold']
¶ -
Type: integer Default value: 80 Show warning about incomplete translations on certain threshold.
-
$cfg['SendErrorReports']
¶ -
Type: string Default value: 'ask'
Valid values are:
ask
always
never
Sets the default behavior for JavaScript error reporting.
Whenever an error is detected in the JavaScript execution, an error report
may be sent to the phpMyAdmin team if the user agrees.The default setting of
'ask'
will ask the user everytime there is a new
error report. However you can set this parameter to'always'
to send error
reports without asking for confirmation or you can set it to'never'
to
never send error reports.This directive is available both in the configuration file and in users
preferences. If the person in charge of a multi-user installation prefers
to disable this feature for all users, a value of'never'
should be
set, and the$cfg['UserprefsDisallow']
directive should
contain'SendErrorReports'
in one of its array values.
-
$cfg['ConsoleEnterExecutes']
¶ -
Type: boolean Default value: false Setting this to
true
allows the user to execute queries by pressing Enter
instead of Ctrl+Enter. A new line can be inserted by pressing Shift + Enter.The behaviour of the console can be temporarily changed using console’s
settings interface.
-
$cfg['AllowThirdPartyFraming']
¶ -
Type: boolean|string Default value: false Setting this to
true
allows phpMyAdmin to be included inside a frame,
and is a potential security hole allowing cross-frame scripting attacks or
clickjacking. Setting this to ‘sameorigin’ prevents phpMyAdmin to be
included from another document in a frame, unless that document belongs
to the same domain.
Server connection settings¶
-
$cfg['Servers']
¶ -
Type: array Default value: one server array with settings listed below Since version 1.4.2, phpMyAdmin supports the administration of multiple
MySQL servers. Therefore, a$cfg['Servers']
-array has been
added which contains the login information for the different servers. The
first$cfg['Servers'][$i]['host']
contains the hostname of
the first server, the second$cfg['Servers'][$i]['host']
the hostname of the second server, etc. In
libraries/config.default.php
, there is only one section for server
definition, however you can put as many as you need in
config.inc.php
, copy that block or needed parts (you don’t have to
define all settings, just those you need to change).Note
The
$cfg['Servers']
array starts with
$cfg[‘Servers’][1]. Do not use $cfg[‘Servers’][0]. If you want more
than one server, just copy following section (including $i
increment) several times. There is no need to define full server
array, just define values you need to change.
-
$cfg['Servers'][$i]['host']
¶ -
Type: string Default value: 'localhost'
The hostname or IP address of your $i-th MySQL-server. E.g.
localhost
.Possible values are:
- hostname, e.g.,
'localhost'
or'mydb.example.org'
- IP address, e.g.,
'127.0.0.1'
or'192.168.10.1'
- IPv6 address, e.g.
2001:cdba:0000:0000:0000:0000:3257:9652
- dot —
'.'
, i.e., use named pipes on windows systems - empty —
''
, disables this server
Note
The hostname
localhost
is handled specially by MySQL and it uses
the socket based connection protocol. To use TCP/IP networking, use an
IP address or hostname such as127.0.0.1
ordb.example.com
. You
can configure the path to the socket with
$cfg['Servers'][$i]['socket']
. - hostname, e.g.,
-
$cfg['Servers'][$i]['port']
¶ -
Type: string Default value: ''
The port-number of your $i-th MySQL-server. Default is 3306 (leave
blank).Note
If you use
localhost
as the hostname, MySQL ignores this port number
and connects with the socket, so if you want to connect to a port
different from the default port, use127.0.0.1
or the real hostname
in$cfg['Servers'][$i]['host']
.
-
$cfg['Servers'][$i]['socket']
¶ -
Type: string Default value: ''
The path to the socket to use. Leave blank for default. To determine
the correct socket, check your MySQL configuration or, using the
mysql command–line client, issue thestatus
command. Among the
resulting information displayed will be the socket used.Note
This takes effect only if
$cfg['Servers'][$i]['host']
is set
tolocalhost
.
-
$cfg['Servers'][$i]['ssl']
¶ -
Type: boolean Default value: false Whether to enable SSL for the connection between phpMyAdmin and the MySQL
server to secure the connection.When using the
'mysql'
extension,
none of the remaining'ssl...'
configuration options apply.We strongly recommend the
'mysqli'
extension when using this option.
-
$cfg['Servers'][$i]['ssl_key']
¶ -
Type: string Default value: NULL Path to the client key file when using SSL for connecting to the MySQL
server. This is used to authenticate the client to the server.For example:
$cfg['Servers'][$i]['ssl_key'] = '/etc/mysql/server-key.pem';
-
$cfg['Servers'][$i]['ssl_cert']
¶ -
Type: string Default value: NULL Path to the client certificate file when using SSL for connecting to the
MySQL server. This is used to authenticate the client to the server.
-
$cfg['Servers'][$i]['ssl_ca']
¶ -
Type: string Default value: NULL Path to the CA file when using SSL for connecting to the MySQL server.
-
$cfg['Servers'][$i]['ssl_ca_path']
¶ -
Type: string Default value: NULL Directory containing trusted SSL CA certificates in PEM format.
-
$cfg['Servers'][$i]['ssl_ciphers']
¶ -
Type: string Default value: NULL List of allowable ciphers for SSL connections to the MySQL server.
-
$cfg['Servers'][$i]['ssl_verify']
¶ -
Type: boolean Default value: true New in version 4.6.0: This is supported since phpMyAdmin 4.6.0.
If your PHP install uses the MySQL Native Driver (mysqlnd), your
MySQL server is 5.6 or later, and your SSL certificate is self-signed,
there is a chance your SSL connection will fail due to validation.
Setting this tofalse
will disable the validation check.Since PHP 5.6.0 it also verifies whether server name matches CN of its
certificate. There is currently no way to disable just this check without
disabling complete SSL verification.Warning
Disabling the certificate verification defeats purpose of using SSL.
This will make the connection vulnerable to man in the middle attacks.Note
This flag only works with PHP 5.6.16 or later.
-
$cfg['Servers'][$i]['connect_type']
¶ -
Type: string Default value: 'tcp'
Deprecated since version 4.7.0: This setting is no longer used as of 4.7.0, since MySQL decides the
connection type based on host, so it could lead to unexpected results.
Please set$cfg['Servers'][$i]['host']
accordingly
instead.What type connection to use with the MySQL server. Your options are
'socket'
and'tcp'
. It defaults to tcp as that is nearly guaranteed
to be available on all MySQL servers, while sockets are not supported on
some platforms. To use the socket mode, your MySQL server must be on the
same machine as the Web server.
-
$cfg['Servers'][$i]['compress']
¶ -
Type: boolean Default value: false Whether to use a compressed protocol for the MySQL server connection
or not (experimental).
-
$cfg['Servers'][$i]['controlhost']
¶ -
Type: string Default value: ''
Permits to use an alternate host to hold the configuration storage
data.
-
$cfg['Servers'][$i]['controlport']
¶ -
Type: string Default value: ''
Permits to use an alternate port to connect to the host that
holds the configuration storage.
-
$cfg['Servers'][$i]['controluser']
¶ -
Type: string Default value: ''
-
$cfg['Servers'][$i]['controlpass']
¶ -
Type: string Default value: ''
This special account is used to access phpMyAdmin configuration storage.
You don’t need it in single user case, but if phpMyAdmin is shared it
is recommended to give access to phpMyAdmin configuration storage only to this user
and configure phpMyAdmin to use it. All users will then be able to use
the features without need to have direct access to phpMyAdmin configuration storage.Changed in version 2.2.5: those were called
stduser
andstdpass
-
$cfg['Servers'][$i]['control_*']
¶ -
Type: mixed New in version 4.7.0.
You can change any MySQL connection setting for control link (used to
access phpMyAdmin configuration storage) using configuration prefixed withcontrol_
.This can be used to change any aspect of the control connection, which by
default uses same parameters as the user one.For example you can configure SSL for the control connection:
// Enable SSL $cfg['Servers'][$i]['control_ssl'] = true; // Client secret key $cfg['Servers'][$i]['control_ssl_key'] = '../client-key.pem'; // Client certificate $cfg['Servers'][$i]['control_ssl_cert'] = '../client-cert.pem'; // Server certification authority $cfg['Servers'][$i]['control_ssl_ca'] = '../server-ca.pem';
-
$cfg['Servers'][$i]['auth_type']
¶ -
Type: string Default value: 'cookie'
Whether config or cookie or HTTP or signon authentication should be
used for this server.- ‘config’ authentication (
$auth_type = 'config'
) is the plain old
way: username and password are stored inconfig.inc.php
. - ‘cookie’ authentication mode (
$auth_type = 'cookie'
) allows you to
log in as any valid MySQL user with the help of cookies. - ‘http’ authentication allows you to log in as any
valid MySQL user via HTTP-Auth. - ‘signon’ authentication mode (
$auth_type = 'signon'
) allows you to
log in from prepared PHP session data or using supplied PHP script.
- ‘config’ authentication (
-
$cfg['Servers'][$i]['auth_http_realm']
¶ -
Type: string Default value: ''
When using auth_type =
http
, this field allows to define a custom
HTTP Basic Auth Realm which will be displayed to the user. If not
explicitly specified in your configuration, a string combined of
“phpMyAdmin ” and either$cfg['Servers'][$i]['verbose']
or
$cfg['Servers'][$i]['host']
will be used.
-
$cfg['Servers'][$i]['auth_swekey_config']
¶ -
Type: string Default value: ''
New in version 3.0.0.0: This setting was named $cfg[‘Servers’][$i][‘auth_feebee_config’] and was renamed before the 3.0.0.0 release.
Deprecated since version 4.6.4: This setting was removed because their servers are no longer working and it was not working correctly.
Deprecated since version 4.0.10.17: This setting was removed in a maintenance release because their servers are no longer working and it was not working correctly.
The name of the file containing swekey ids and login names for hardware
authentication. Leave empty to deactivate this feature.
-
$cfg['Servers'][$i]['user']
¶ -
Type: string Default value: 'root'
-
$cfg['Servers'][$i]['password']
¶ -
Type: string Default value: ''
When using
$cfg['Servers'][$i]['auth_type']
set to
‘config’, this is the user/password-pair which phpMyAdmin will use to
connect to the MySQL server. This user/password pair is not needed when
HTTP or cookie authentication is used
and should be empty.
-
$cfg['Servers'][$i]['nopassword']
¶ -
Type: boolean Default value: false Deprecated since version 4.7.0: This setting was removed as it can produce unexpected results.
Allow attempt to log in without password when a login with password
fails. This can be used together with http authentication, when
authentication is done some other way and phpMyAdmin gets user name
from auth and uses empty password for connecting to MySQL. Password
login is still tried first, but as fallback, no password method is
tried.
-
$cfg['Servers'][$i]['only_db']
¶ -
Type: string or array Default value: ''
If set to a (an array of) database name(s), only this (these)
database(s) will be shown to the user. Since phpMyAdmin 2.2.1,
this/these database(s) name(s) may contain MySQL wildcards characters
(“_” and “%”): if you want to use literal instances of these
characters, escape them (I.E. use'my_db'
and not'my_db'
).This setting is an efficient way to lower the server load since the
latter does not need to send MySQL requests to build the available
database list. But it does not replace the privileges rules of the
MySQL database server. If set, it just means only these databases
will be displayed but not that all other databases can’t be used.An example of using more that one database:
$cfg['Servers'][$i]['only_db'] = array('db1', 'db2');
Changed in version 4.0.0: Previous versions permitted to specify the display order of
the database names via this directive.
-
$cfg['Servers'][$i]['hide_db']
¶ -
Type: string Default value: ''
Regular expression for hiding some databases from unprivileged users.
This only hides them from listing, but a user is still able to access
them (using, for example, the SQL query area). To limit access, use
the MySQL privilege system. For example, to hide all databases
starting with the letter “a”, use$cfg['Servers'][$i]['hide_db'] = '^a';
and to hide both “db1” and “db2” use
$cfg['Servers'][$i]['hide_db'] = '^(db1|db2)$';
More information on regular expressions can be found in the PCRE
pattern syntax portion
of the PHP reference manual.
-
$cfg['Servers'][$i]['verbose']
¶ -
Type: string Default value: ''
Only useful when using phpMyAdmin with multiple server entries. If
set, this string will be displayed instead of the hostname in the
pull-down menu on the main page. This can be useful if you want to
show only certain databases on your system, for example. For HTTP
auth, all non-US-ASCII characters will be stripped.
-
$cfg['Servers'][$i]['extension']
¶ -
Type: string Default value: 'mysqli'
Deprecated since version 4.2.0: This setting was removed. The
mysql
extension will only be used when
themysqli
extension is not available. As of 5.0.0, only the
mysqli
extension can be used.The PHP MySQL extension to use (
mysql
ormysqli
).It is recommended to use
mysqli
in all installations.
-
$cfg['Servers'][$i]['pmadb']
¶ -
Type: string Default value: ''
The name of the database containing the phpMyAdmin configuration
storage.See the phpMyAdmin configuration storage section in this document to see the benefits of
this feature, and for a quick way of creating this database and the needed
tables.If you are the only user of this phpMyAdmin installation, you can use your
current database to store those special tables; in this case, just put your
current database name in$cfg['Servers'][$i]['pmadb']
. For a
multi-user installation, set this parameter to the name of your central
database containing the phpMyAdmin configuration storage.
-
$cfg['Servers'][$i]['bookmarktable']
¶ -
Type: string or false Default value: ''
New in version 2.2.0.
Since release 2.2.0 phpMyAdmin allows users to bookmark queries. This
can be useful for queries you often run. To allow the usage of this
functionality:- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - enter the table name in
$cfg['Servers'][$i]['bookmarktable']
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['relation']
¶ -
Type: string or false Default value: ''
New in version 2.2.4.
Since release 2.2.4 you can describe, in a special ‘relation’ table,
which column is a key in another table (a foreign key). phpMyAdmin
currently uses this to:- make clickable, when you browse the master table, the data values that
point to the foreign table; - display in an optional tool-tip the “display column” when browsing the
master table, if you move the mouse to a column containing a foreign
key (use also the ‘table_info’ table); (see 6.7 How can I use the “display column” feature?) - in edit/insert mode, display a drop-down list of possible foreign keys
(key value and “display column” are shown) (see 6.21 In edit/insert mode, how can I see a list of possible values for a column, based on some foreign table?) - display links on the table properties page, to check referential
integrity (display missing foreign keys) for each described key; - in query-by-example, create automatic joins (see 6.6 How can I use the relation table in Query-by-example?)
- enable you to get a PDF schema of
your database (also uses the table_coords table).
The keys can be numeric or character.
To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the relation table name in
$cfg['Servers'][$i]['relation']
- now as normal user open phpMyAdmin and for each one of your tables
where you want to use this feature, click Structure/Relation view/
and choose foreign columns.
This feature can be disabled by setting the configuration to
false
.Note
In the current version,
master_db
must be the same asforeign_db
.
Those columns have been put in future development of the cross-db
relations. - make clickable, when you browse the master table, the data values that
-
$cfg['Servers'][$i]['table_info']
¶ -
Type: string or false Default value: ''
New in version 2.3.0.
Since release 2.3.0 you can describe, in a special ‘table_info’
table, which column is to be displayed as a tool-tip when moving the
cursor over the corresponding key. This configuration variable will
hold the name of this special table. To allow the usage of this
functionality:- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['table_info']
(e.g.
pma__table_info
) - then for each table where you want to use this feature, click
“Structure/Relation view/Choose column to display” to choose the
column.
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['table_coords']
¶ -
Type: string or false Default value: ''
The designer feature can save your page layout; by pressing the “Save page” or “Save page as”
button in the expanding designer menu, you can customize the layout and have it loaded the next
time you use the designer. That layout is stored in this table. Furthermore, this table is also
required for using the PDF relation export feature, see
$cfg['Servers'][$i]['pdf_pages']
for additional details.
-
$cfg['Servers'][$i]['pdf_pages']
¶ -
Type: string or false Default value: ''
New in version 2.3.0.
Since release 2.3.0 you can have phpMyAdmin create PDF pages
showing the relations between your tables. Further, the designer interface
permits visually managing the relations. To do this it needs two tables
“pdf_pages” (storing information about the available PDF pages)
and “table_coords” (storing coordinates where each table will be placed on
a PDF schema output). You must be using the “relation” feature.To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the correct table names in
$cfg['Servers'][$i]['table_coords']
and
$cfg['Servers'][$i]['pdf_pages']
This feature can be disabled by setting either of the configurations to
false
. - set up
-
$cfg['Servers'][$i]['designer_coords']
¶ -
Type: string Default value: ''
New in version 2.10.0: Since release 2.10.0 a Designer interface is available; it permits to
visually manage the relations.Deprecated since version 4.3.0: This setting was removed and the Designer table positioning data is now stored into
$cfg['Servers'][$i]['table_coords']
.Note
You can now delete the table pma__designer_coords from your phpMyAdmin configuration storage database and remove
$cfg['Servers'][$i]['designer_coords']
from your configuration file.
-
$cfg['Servers'][$i]['column_info']
¶ -
Type: string or false Default value: ''
New in version 2.3.0.
This part requires a content update! Since release 2.3.0 you can
store comments to describe each column for each table. These will then
be shown on the “printview”.Starting with release 2.5.0, comments are consequently used on the table
property pages and table browse view, showing up as tool-tips above the
column name (properties page) or embedded within the header of table in
browse view. They can also be shown in a table dump. Please see the
relevant configuration directives later on.Also new in release 2.5.0 is a MIME- transformation system which is also
based on the following table structure. See Transformations for
further information. To use the MIME- transformation system, your
column_info table has to have the three new columns ‘mimetype’,
‘transformation’, ‘transformation_options’.Starting with release 4.3.0, a new input-oriented transformation system
has been introduced. Also, backward compatibility code used in the old
transformations system was removed. As a result, an update to column_info
table is necessary for previous transformations and the new input-oriented
transformation system to work. phpMyAdmin will upgrade it automatically
for you by analyzing your current column_info table structure.
However, if something goes wrong with the auto-upgrade then you can
use the SQL script found in./sql/upgrade_column_info_4_3_0+.sql
to upgrade it manually.To allow the usage of this functionality:
-
set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage -
put the table name in
$cfg['Servers'][$i]['column_info']
(e.g.
pma__column_info
) -
to update your PRE-2.5.0 Column_comments table use this: and
remember that the Variable inconfig.inc.php
has been renamed from
$cfg['Servers'][$i]['column_comments']
to
$cfg['Servers'][$i]['column_info']
ALTER TABLE `pma__column_comments` ADD `mimetype` VARCHAR( 255 ) NOT NULL, ADD `transformation` VARCHAR( 255 ) NOT NULL, ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
-
to update your PRE-4.3.0 Column_info table manually use this
./sql/upgrade_column_info_4_3_0+.sql
SQL script.
This feature can be disabled by setting the configuration to
false
.Note
For auto-upgrade functionality to work, your
$cfg['Servers'][$i]['controluser']
must have ALTER privilege on
phpmyadmin
database. See the MySQL documentation for GRANT on how to
GRANT
privileges to a user. -
-
$cfg['Servers'][$i]['history']
¶ -
Type: string or false Default value: ''
New in version 2.5.0.
Since release 2.5.0 you can store your SQL history, which means all
queries you entered manually into the phpMyAdmin interface. If you don’t
want to use a table-based history, you can use the JavaScript-based
history.Using that, all your history items are deleted when closing the window.
Using$cfg['QueryHistoryMax']
you can specify an amount of
history items you want to have on hold. On every login, this list gets cut
to the maximum amount.The query history is only available if JavaScript is enabled in
your browser.To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['history']
(e.g.
pma__history
)
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['recent']
¶ -
Type: string or false Default value: ''
New in version 3.5.0.
Since release 3.5.0 you can show recently used tables in the
navigation panel. It helps you to jump across table directly, without
the need to select the database, and then select the table. Using
$cfg['NumRecentTables']
you can configure the maximum number
of recent tables shown. When you select a table from the list, it will jump to
the page specified in$cfg['NavigationTreeDefaultTabTable']
.Without configuring the storage, you can still access the recently used tables,
but it will disappear after you logout.To allow the usage of this functionality persistently:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['recent']
(e.g.
pma__recent
)
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['favorite']
¶ -
Type: string or false Default value: ''
New in version 4.2.0.
Since release 4.2.0 you can show a list of selected tables in the
navigation panel. It helps you to jump to the table directly, without
the need to select the database, and then select the table. When you
select a table from the list, it will jump to the page specified in
$cfg['NavigationTreeDefaultTabTable']
.You can add tables to this list or remove tables from it in database
structure page by clicking on the star icons next to table names. Using
$cfg['NumFavoriteTables']
you can configure the maximum
number of favorite tables shown.Without configuring the storage, you can still access the favorite tables,
but it will disappear after you logout.To allow the usage of this functionality persistently:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['favorite']
(e.g.
pma__favorite
)
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['table_uiprefs']
¶ -
Type: string or false Default value: ''
New in version 3.5.0.
Since release 3.5.0 phpMyAdmin can be configured to remember several
things (sorted column$cfg['RememberSorting']
, column order,
and column visibility from a database table) for browsing tables. Without
configuring the storage, these features still can be used, but the values will
disappear after you logout.To allow the usage of these functionality persistently:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['table_uiprefs']
(e.g.
pma__table_uiprefs
)
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['users']
¶ -
Type: string or false Default value: ''
The table used by phpMyAdmin to store user name information for associating with user groups.
See the next entry on$cfg['Servers'][$i]['usergroups']
for more details
and the suggested settings.
-
$cfg['Servers'][$i]['usergroups']
¶ -
Type: string or false Default value: ''
New in version 4.1.0.
Since release 4.1.0 you can create different user groups with menu items
attached to them. Users can be assigned to these groups and the logged in
user would only see menu items configured to the usergroup they are assigned to.
To do this it needs two tables “usergroups” (storing allowed menu items for each
user group) and “users” (storing users and their assignments to user groups).To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the correct table names in
$cfg['Servers'][$i]['users']
(e.g.pma__users
) and
$cfg['Servers'][$i]['usergroups']
(e.g.pma__usergroups
)
This feature can be disabled by setting either of the configurations to
false
. - set up
-
$cfg['Servers'][$i]['navigationhiding']
¶ -
Type: string or false Default value: ''
New in version 4.1.0.
Since release 4.1.0 you can hide/show items in the navigation tree.
To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['navigationhiding']
(e.g.
pma__navigationhiding
)
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['central_columns']
¶ -
Type: string or false Default value: ''
New in version 4.3.0.
Since release 4.3.0 you can have a central list of columns per database.
You can add/remove columns to the list as per your requirement. These columns
in the central list will be available to use while you create a new column for
a table or create a table itself. You can select a column from central list
while creating a new column, it will save you from writing the same column definition
over again or from writing different names for similar column.To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['central_columns']
(e.g.
pma__central_columns
)
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['designer_settings']
¶ -
Type: string or false Default value: ''
New in version 4.5.0.
Since release 4.5.0 your designer settings can be remembered.
Your choice regarding ‘Angular/Direct Links’, ‘Snap to Grid’, ‘Toggle Relation Lines’,
‘Small/Big All’, ‘Move Menu’ and ‘Pin Text’ can be remembered persistently.To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['designer_settings']
(e.g.
pma__designer_settings
)
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['savedsearches']
¶ -
Type: string or false Default value: ''
New in version 4.2.0.
Since release 4.2.0 you can save and load query-by-example searches from the Database > Query panel.
To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['savedsearches']
(e.g.
pma__savedsearches
)
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['export_templates']
¶ -
Type: string or false Default value: ''
New in version 4.5.0.
Since release 4.5.0 you can save and load export templates.
To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['export_templates']
(e.g.
pma__export_templates
)
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['tracking']
¶ -
Type: string or false Default value: ''
New in version 3.3.x.
Since release 3.3.x a tracking mechanism is available. It helps you to
track every SQL command which is
executed by phpMyAdmin. The mechanism supports logging of data
manipulation and data definition statements. After enabling it you can
create versions of tables.The creation of a version has two effects:
- phpMyAdmin saves a snapshot of the table, including structure and
indexes. - phpMyAdmin logs all commands which change the structure and/or data of
the table and links these commands with the version number.
Of course you can view the tracked changes. On the Tracking
page a complete report is available for every version. For the report you
can use filters, for example you can get a list of statements within a date
range. When you want to filter usernames you can enter * for all names or
you enter a list of names separated by ‘,’. In addition you can export the
(filtered) report to a file or to a temporary database.To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['tracking']
(e.g.
pma__tracking
)
This feature can be disabled by setting the configuration to
false
. - phpMyAdmin saves a snapshot of the table, including structure and
-
$cfg['Servers'][$i]['tracking_version_auto_create']
¶ -
Type: boolean Default value: false Whether the tracking mechanism creates versions for tables and views
automatically.If this is set to true and you create a table or view with
- CREATE TABLE …
- CREATE VIEW …
and no version exists for it, the mechanism will create a version for
you automatically.
-
$cfg['Servers'][$i]['tracking_default_statements']
¶ -
Type: string Default value: 'CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,CREATE INDEX,DROP INDEX,INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,CREATE VIEW,ALTER VIEW,DROP VIEW,CREATE DATABASE,ALTER DATABASE,DROP DATABASE'
Defines the list of statements the auto-creation uses for new
versions.
-
$cfg['Servers'][$i]['tracking_add_drop_view']
¶ -
Type: boolean Default value: true Whether a DROP VIEW IF EXISTS statement will be added as first line to
the log when creating a view.
-
$cfg['Servers'][$i]['tracking_add_drop_table']
¶ -
Type: boolean Default value: true Whether a DROP TABLE IF EXISTS statement will be added as first line
to the log when creating a table.
-
$cfg['Servers'][$i]['tracking_add_drop_database']
¶ -
Type: boolean Default value: true Whether a DROP DATABASE IF EXISTS statement will be added as first
line to the log when creating a database.
-
$cfg['Servers'][$i]['userconfig']
¶ -
Type: string or false Default value: ''
New in version 3.4.x.
Since release 3.4.x phpMyAdmin allows users to set most preferences by
themselves and store them in the database.If you don’t allow for storing preferences in
$cfg['Servers'][$i]['pmadb']
, users can still personalize
phpMyAdmin, but settings will be saved in browser’s local storage, or, it
is is unavailable, until the end of session.To allow the usage of this functionality:
- set up
$cfg['Servers'][$i]['pmadb']
and the phpMyAdmin configuration storage - put the table name in
$cfg['Servers'][$i]['userconfig']
This feature can be disabled by setting the configuration to
false
. - set up
-
$cfg['Servers'][$i]['MaxTableUiprefs']
¶ -
Type: integer Default value: 100 Maximum number of rows saved in
$cfg['Servers'][$i]['table_uiprefs']
table.When tables are dropped or renamed,
$cfg['Servers'][$i]['table_uiprefs']
may contain invalid data
(referring to tables which no longer exist). We only keep this number of newest
rows in$cfg['Servers'][$i]['table_uiprefs']
and automatically
delete older rows.
-
$cfg['Servers'][$i]['SessionTimeZone']
¶ -
Type: string Default value: ''
Sets the time zone used by phpMyAdmin. Leave blank to use the time zone of your
database server. Possible values are explained at
https://dev.mysql.com/doc/refman/8.0/en/time-zone-support.htmlThis is useful when your database server uses a time zone which is different from the
time zone you want to use in phpMyAdmin.
-
$cfg['Servers'][$i]['AllowRoot']
¶ -
Type: boolean Default value: true Whether to allow root access. This is just a shortcut for the
$cfg['Servers'][$i]['AllowDeny']['rules']
below.
-
$cfg['Servers'][$i]['AllowNoPassword']
¶ -
Type: boolean Default value: false Whether to allow logins without a password. The default value of
false
for this parameter prevents unintended access to a MySQL
server with was left with an empty password for root or on which an
anonymous (blank) user is defined.
-
$cfg['Servers'][$i]['AllowDeny']['order']
¶ -
Type: string Default value: ''
If your rule order is empty, then IP
authorization is disabled.If your rule order is set to
'deny,allow'
then the system applies all deny rules followed by
allow rules. Access is allowed by default. Any client which does not
match a Deny command or does match an Allow command will be allowed
access to the server.If your rule order is set to
'allow,deny'
then the system applies all allow rules followed by deny rules. Access
is denied by default. Any client which does not match an Allow
directive or does match a Deny directive will be denied access to the
server.If your rule order is set to
'explicit'
, authorization is
performed in a similar fashion to rule order ‘deny,allow’, with the
added restriction that your host/username combination must be
listed in the allow rules, and not listed in the deny rules. This
is the most secure means of using Allow/Deny rules, and was
available in Apache by specifying allow and deny rules without setting
any order.Please also see
$cfg['TrustedProxies']
for
detecting IP address behind proxies.
-
$cfg['Servers'][$i]['AllowDeny']['rules']
¶ -
Type: array of strings Default value: array() The general format for the rules is as such:
<'allow' | 'deny'> <username> [from] <ipmask>
If you wish to match all users, it is possible to use a
'%'
as a
wildcard in the username field.There are a few shortcuts you can
use in the ipmask field as well (please note that those containing
SERVER_ADDRESS might not be available on all webservers):'all' -> 0.0.0.0/0 'localhost' -> 127.0.0.1/8 'localnetA' -> SERVER_ADDRESS/8 'localnetB' -> SERVER_ADDRESS/16 'localnetC' -> SERVER_ADDRESS/24
Having an empty rule list is equivalent to either using
'allow %
if your rule order is set to
from all''deny,allow'
or'deny %
if your rule order is set to
from all''allow,deny'
or
'explicit'
.For the IP Address matching
system, the following work:xxx.xxx.xxx.xxx
(an exact IP Address)xxx.xxx.xxx.[yyy-zzz]
(an IP Address range)xxx.xxx.xxx.xxx/nn
(CIDR, Classless Inter-Domain Routing type IP addresses)
But the following does not work:
xxx.xxx.xxx.xx[yyy-zzz]
(partial IP address range)
For IPv6 addresses, the following work:
xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
(an exact IPv6 address)xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:[yyyy-zzzz]
(an IPv6 address range)xxxx:xxxx:xxxx:xxxx/nn
(CIDR, Classless Inter-Domain Routing type IPv6 addresses)
But the following does not work:
xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xx[yyy-zzz]
(partial IPv6 address range)
Examples:
$cfg['Servers'][$i]['AllowDeny']['order'] = 'allow,deny'; $cfg['Servers'][$i]['AllowDeny']['rules'] = array('allow bob from all'); // Allow only 'bob' to connect from any host $cfg['Servers'][$i]['AllowDeny']['order'] = 'allow,deny'; $cfg['Servers'][$i]['AllowDeny']['rules'] = array('allow mary from 192.168.100.[50-100]'); // Allow only 'mary' to connect from host 192.168.100.50 through 192.168.100.100 $cfg['Servers'][$i]['AllowDeny']['order'] = 'allow,deny'; $cfg['Servers'][$i]['AllowDeny']['rules'] = array('allow % from 192.168.[5-6].10'); // Allow any user to connect from host 192.168.5.10 or 192.168.6.10 $cfg['Servers'][$i]['AllowDeny']['order'] = 'allow,deny'; $cfg['Servers'][$i]['AllowDeny']['rules'] = array('allow root from 192.168.5.50','allow % from 192.168.6.10'); // Allow any user to connect from 192.168.6.10, and additionally allow root to connect from 192.168.5.50
-
$cfg['Servers'][$i]['DisableIS']
¶ -
Type: boolean Default value: false Disable using
INFORMATION_SCHEMA
to retrieve information (use
SHOW
commands instead), because of speed issues when many
databases are present.Note
Enabling this option might give you a big performance boost on older
MySQL servers.
-
$cfg['Servers'][$i]['SignonScript']
¶ -
Type: string Default value: ''
New in version 3.5.0.
Name of PHP script to be sourced and executed to obtain login
credentials. This is alternative approach to session based single
signon. The script has to provide a function called
get_login_credentials
which returns list of username and
password, accepting single parameter of existing username (can be
empty). Seeexamples/signon-script.php
for an example:<?php /** * Single signon for phpMyAdmin * * This is just example how to use script based single signon with * phpMyAdmin, it is not intended to be perfect code and look, only * shows how you can integrate this functionality in your application. */ declare(strict_types=1); // phpcs:disable Squiz.Functions.GlobalFunction /** * This function returns username and password. * * It can optionally use configured username as parameter. * * @param string $user User name * * @return array */ function get_login_credentials($user) { /* Optionally we can use passed username */ if (! empty($user)) { return [ $user, 'password', ]; } /* Here we would retrieve the credentials */ return [ 'root', '', ]; }
-
$cfg['Servers'][$i]['SignonSession']
¶ -
Type: string Default value: ''
Name of session which will be used for signon authentication method.
You should use something different thanphpMyAdmin
, because this
is session which phpMyAdmin uses internally. Takes effect only if
$cfg['Servers'][$i]['SignonScript']
is not configured.
-
$cfg['Servers'][$i]['SignonCookieParams']
¶ -
Type: array Default value: array()
New in version 4.7.0.
An associative array of session cookie parameters of other authentication system.
It is not needed if the other system doesn’t use session_set_cookie_params().
Keys should include ‘lifetime’, ‘path’, ‘domain’, ‘secure’ or ‘httponly’.
Valid values are mentioned in session_get_cookie_params, they should be set to same values as the
other application uses. Takes effect only if
$cfg['Servers'][$i]['SignonScript']
is not configured.
-
$cfg['Servers'][$i]['SignonURL']
¶ -
Type: string Default value: ''
URL where user will be redirected
to log in for signon authentication method. Should be absolute
including protocol.
-
$cfg['Servers'][$i]['LogoutURL']
¶ -
Type: string Default value: ''
URL where user will be redirected
after logout (doesn’t affect config authentication method). Should be
absolute including protocol.
-
$cfg['Servers'][$i]['hide_connection_errors']
¶ -
Type: boolean Default value: false New in version 4.9.8.
Whether to show or hide detailed MySQL/MariaDB connection errors on the login page.
Note
This error message can contain the target database server hostname or IP address,
which may reveal information about your network to an attacker.
Generic settings¶
-
$cfg['DisableShortcutKeys']
¶ -
Type: boolean Default value: false You can disable phpMyAdmin shortcut keys by setting
$cfg['DisableShortcutKeys']
to false.
-
$cfg['ServerDefault']
¶ -
Type: integer Default value: 1 If you have more than one server configured, you can set
$cfg['ServerDefault']
to any one of them to autoconnect to that
server when phpMyAdmin is started, or set it to 0 to be given a list
of servers without logging in.If you have only one server configured,
$cfg['ServerDefault']
MUST be set to that server.
-
$cfg['VersionCheck']
¶ -
Type: boolean Default value: true Enables check for latest versions using JavaScript on the main phpMyAdmin
page or by directly accessing index.php?route=/version-check.Note
This setting can be adjusted by your vendor.
-
$cfg['ProxyUrl']
¶ -
Type: string Default value: ''
The url of the proxy to be used when phpmyadmin needs to access the outside
internet such as when retrieving the latest version info or submitting error
reports. You need this if the server where phpMyAdmin is installed does not
have direct access to the internet.
The format is: “hostname:portnumber”
-
$cfg['ProxyUser']
¶ -
Type: string Default value: ''
The username for authenticating with the proxy. By default, no
authentication is performed. If a username is supplied, Basic
Authentication will be performed. No other types of authentication
are currently supported.
-
$cfg['ProxyPass']
¶ -
Type: string Default value: ''
The password for authenticating with the proxy.
-
$cfg['MaxDbList']
¶ -
Type: integer Default value: 100 The maximum number of database names to be displayed in the main panel’s
database list.
-
$cfg['MaxTableList']
¶ -
Type: integer Default value: 250 The maximum number of table names to be displayed in the main panel’s
list (except on the Export page).
-
$cfg['ShowHint']
¶ -
Type: boolean Default value: true Whether or not to show hints (for example, hints when hovering over
table headers).
-
$cfg['MaxCharactersInDisplayedSQL']
¶ -
Type: integer Default value: 1000 The maximum number of characters when a SQL query is displayed. The
default limit of 1000 should be correct to avoid the display of tons of
hexadecimal codes that represent BLOBs, but some users have real
SQL queries that are longer than 1000 characters. Also, if a
query’s length exceeds this limit, this query is not saved in the history.
-
$cfg['PersistentConnections']
¶ -
Type: boolean Default value: false Whether persistent connections should be used or not.
-
$cfg['ForceSSL']
¶ -
Type: boolean Default value: false Deprecated since version 4.6.0: This setting is no longer available since phpMyAdmin 4.6.0. Please
adjust your webserver instead.Whether to force using https while accessing phpMyAdmin. In a reverse
proxy setup, setting this totrue
is not supported.Note
In some setups (like separate SSL proxy or load balancer) you might
have to set$cfg['PmaAbsoluteUri']
for correct
redirection.
-
$cfg['MysqlSslWarningSafeHosts']
¶ -
Type: array Default value: ['127.0.0.1', 'localhost']
This search is case-sensitive and will match the exact string only.
If your setup does not use SSL but is safe because you are using a
local connection or private network, you can add your hostname or IP to the list.
You can also remove the default entries to only include yours.This check uses the value of
$cfg['Servers'][$i]['host']
.New in version 5.1.0.
Example configuration
$cfg['MysqlSslWarningSafeHosts'] = ['127.0.0.1', 'localhost', 'mariadb.local'];
-
$cfg['ExecTimeLimit']
¶ -
Type: integer [number of seconds] Default value: 300 Set the number of seconds a script is allowed to run. If seconds is
set to zero, no time limit is imposed. This setting is used while
importing/exporting dump files but has
no effect when PHP is running in safe mode.
-
$cfg['SessionSavePath']
¶ -
Type: string Default value: ''
Path for storing session data (session_save_path PHP parameter).
Warning
This folder should not be publicly accessible through the webserver,
otherwise you risk leaking private data from your session.
-
$cfg['MemoryLimit']
¶ -
Type: string [number of bytes] Default value: '-1'
Set the number of bytes a script is allowed to allocate. If set to
'-1'
, no limit is imposed. If set to'0'
, no change of the
memory limit is attempted and thephp.ini
memory_limit
is
used.This setting is used while importing/exporting dump files
so you definitely don’t want to put here a too low
value. It has no effect when PHP is running in safe mode.You can also use any string as in
php.ini
, eg. ‘16M’. Ensure you
don’t omit the suffix (16 means 16 bytes!)
-
$cfg['SkipLockedTables']
¶ -
Type: boolean Default value: false Mark used tables and make it possible to show databases with locked
tables (since MySQL 3.23.30).
-
$cfg['ShowSQL']
¶ -
Type: boolean Default value: true Defines whether SQL queries
generated by phpMyAdmin should be displayed or not.
-
$cfg['RetainQueryBox']
¶ -
Type: boolean Default value: false Defines whether the SQL query box
should be kept displayed after its submission.
-
$cfg['CodemirrorEnable']
¶ -
Type: boolean Default value: true Defines whether to use a Javascript code editor for SQL query boxes.
CodeMirror provides syntax highlighting and line numbers. However,
middle-clicking for pasting the clipboard contents in some Linux
distributions (such as Ubuntu) is not supported by all browsers.
-
$cfg['DefaultForeignKeyChecks']
¶ -
Type: string Default value: 'default'
Default value of the checkbox for foreign key checks, to disable/enable
foreign key checks for certain queries. The possible values are'default'
,
'enable'
or'disable'
. If set to'default'
, the value of the
MySQL variableFOREIGN_KEY_CHECKS
is used.
-
$cfg['AllowUserDropDatabase']
¶ -
Type: boolean Default value: false Warning
This is not a security measure as there will be always ways to
circumvent this. If you want to prohibit users from dropping databases,
revoke their corresponding DROP privilege.Defines whether normal users (non-administrator) are allowed to delete
their own database or not. If set as false, the link Drop
Database will not be shown, and even aDROP DATABASE mydatabase
will
be rejected. Quite practical for ISP ‘s with many customers.This limitation of SQL queries is not as strict as when using MySQL
privileges. This is due to nature of SQL queries which might be
quite complicated. So this choice should be viewed as help to avoid
accidental dropping rather than strict privilege limitation.
-
$cfg['Confirm']
¶ -
Type: boolean Default value: true Whether a warning (“Are your really sure…”) should be displayed when
you’re about to lose data.
-
$cfg['UseDbSearch']
¶ -
Type: boolean Default value: true Define whether the “search string inside database” is enabled or not.
-
$cfg['IgnoreMultiSubmitErrors']
¶ -
Type: boolean Default value: false Define whether phpMyAdmin will continue executing a multi-query
statement if one of the queries fails. Default is to abort execution.
-
$cfg['enable_drag_drop_import']
¶ -
Type: boolean Default value: true Whether or not the drag and drop import feature is enabled.
When enabled, a user can drag a file in to their browser and phpMyAdmin will
attempt to import the file.
-
$cfg['URLQueryEncryption']
¶ -
Type: boolean Default value: false New in version 4.9.8.
Define whether phpMyAdmin will encrypt sensitive data (like database name
and table name) from the URL query string. Default is to not encrypt the URL
query string.
-
$cfg['URLQueryEncryptionSecretKey']
¶ -
Type: string Default value: ''
New in version 4.9.8.
A secret key used to encrypt/decrypt the URL query string.
Should be 32 bytes long.
Cookie authentication options¶
-
$cfg['blowfish_secret']
¶ -
Type: string Default value: ''
The “cookie” auth_type uses AES algorithm to encrypt the password. If you
are using the “cookie” auth_type, enter here a random passphrase of your
choice. It will be used internally by the AES algorithm: you won’t be
prompted for this passphrase.The secret should be 32 characters long. Using shorter will lead to weaker security
of encrypted cookies, using longer will cause no harm.Note
The configuration is called blowfish_secret for historical reasons as
Blowfish algorithm was originally used to do the encryption.Changed in version 3.1.0: Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
makes a bit weaker security as this generated secret is stored in
session and furthermore it makes impossible to recall user name from
cookie.
-
$cfg['CookieSameSite']
¶ -
Type: string Default value: 'Strict'
New in version 5.1.0.
It sets SameSite attribute of the Set-Cookie HTTP response header.
Valid values are:Lax
Strict
None
-
$cfg['LoginCookieRecall']
¶ -
Type: boolean Default value: true Define whether the previous login should be recalled or not in cookie
authentication mode.This is automatically disabled if you do not have
configured$cfg['blowfish_secret']
.
-
$cfg['LoginCookieValidity']
¶ -
Type: integer [number of seconds] Default value: 1440 Define how long a login cookie is valid. Please note that php
configuration option session.gc_maxlifetime might limit session validity and if the session is lost,
the login cookie is also invalidated. So it is a good idea to set
session.gc_maxlifetime
at least to the same value of
$cfg['LoginCookieValidity']
.
-
$cfg['LoginCookieStore']
¶ -
Type: integer [number of seconds] Default value: 0 Define how long login cookie should be stored in browser. Default 0
means that it will be kept for existing session. This is recommended
for not trusted environments.
-
$cfg['LoginCookieDeleteAll']
¶ -
Type: boolean Default value: true If enabled (default), logout deletes cookies for all servers,
otherwise only for current one. Setting this to false makes it easy to
forget to log out from other server, when you are using more of them.
-
$cfg['AllowArbitraryServer']
¶ -
Type: boolean Default value: false If enabled, allows you to log in to arbitrary servers using cookie
authentication.Note
Please use this carefully, as this may allow users access to MySQL servers
behind the firewall where your HTTP server is placed.
See also$cfg['ArbitraryServerRegexp']
.
-
$cfg['ArbitraryServerRegexp']
¶ -
Type: string Default value: ''
Restricts the MySQL servers to which the user can log in when
$cfg['AllowArbitraryServer']
is enabled by
matching the IP or the hostname of the MySQL server
to the given regular expression. The regular expression must be enclosed
with a delimiter character.It is recommended to include start and end symbols in the regular
expression, so that you can avoid partial matches on the string.Examples:
// Allow connection to three listed servers: $cfg['ArbitraryServerRegexp'] = '/^(server|another|yetdifferent)$/'; // Allow connection to range of IP addresses: $cfg['ArbitraryServerRegexp'] = '@^192.168.0.[0-9]{1,}$@'; // Allow connection to server name ending with -mysql: $cfg['ArbitraryServerRegexp'] = '@^[^:]-mysql$@';
Note
The whole server name is matched, it can include port as well. Due to
way MySQL is permissive in connection parameters, it is possible to use
connection strings as`server:3306-mysql`
. This can be used to
bypass regular expression by the suffix, while connecting to another
server.
-
$cfg['CaptchaMethod']
¶ -
Type: string Default value: 'invisible'
Valid values are:
'invisible'
Use an invisible captcha checking method;'checkbox'
Use a checkbox to confirm the user is not a robot.
New in version 5.0.3.
-
$cfg['CaptchaApi']
¶ -
Type: string Default value: 'https://www.google.com/recaptcha/api.js'
New in version 5.1.0.
The URL for the reCaptcha v2 service’s API, either Google’s or a compatible one.
-
$cfg['CaptchaCsp']
¶ -
Type: string Default value: 'https://apis.google.com https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ https://ssl.gstatic.com/'
New in version 5.1.0.
The Content-Security-Policy snippet (URLs from which to allow embedded content)
for the reCaptcha v2 service, either Google’s or a compatible one.
-
$cfg['CaptchaRequestParam']
¶ -
Type: string Default value: 'g-recaptcha'
New in version 5.1.0.
The request parameter used for the reCaptcha v2 service.
-
$cfg['CaptchaResponseParam']
¶ -
Type: string Default value: 'g-recaptcha-response'
New in version 5.1.0.
The response parameter used for the reCaptcha v2 service.
-
$cfg['CaptchaLoginPublicKey']
¶ -
Type: string Default value: ''
The public key for the reCaptcha service that can be obtained from the
“Admin Console” on https://www.google.com/recaptcha/about/.reCaptcha will be then used in Cookie authentication mode.
New in version 4.1.0.
-
$cfg['CaptchaLoginPrivateKey']
¶ -
Type: string Default value: ''
The private key for the reCaptcha service that can be obtained from the
“Admin Console” on https://www.google.com/recaptcha/about/.reCaptcha will be then used in Cookie authentication mode.
New in version 4.1.0.
-
$cfg['CaptchaSiteVerifyURL']
¶ -
Type: string Default value: ''
The URL for the reCaptcha service to do siteverify action.
reCaptcha will be then used in Cookie authentication mode.
New in version 5.1.0.
Navigation panel setup¶
-
$cfg['ShowDatabasesNavigationAsTree']
¶ -
Type: boolean Default value: true In the navigation panel, replaces the database tree with a selector
-
$cfg['FirstLevelNavigationItems']
¶ -
Type: integer Default value: 100 The number of first level databases that can be displayed on each page
of navigation tree.
-
$cfg['MaxNavigationItems']
¶ -
Type: integer Default value: 50 The number of items (tables, columns, indexes) that can be displayed on each
page of the navigation tree.
-
$cfg['NavigationTreeEnableGrouping']
¶ -
Type: boolean Default value: true Defines whether to group the databases based on a common prefix
in their name$cfg['NavigationTreeDbSeparator']
.
-
$cfg['NavigationTreeDbSeparator']
¶ -
Type: string Default value: '_'
The string used to separate the parts of the database name when
showing them in a tree.
-
$cfg['NavigationTreeTableSeparator']
¶ -
Type: string or array Default value: '__'
Defines a string to be used to nest table spaces. This means if you have
tables likefirst__second__third
this will be shown as a three-level
hierarchy like: first > second > third. If set to false or empty, the
feature is disabled. NOTE: You should not use this separator at the
beginning or end of a table name or multiple times after another without
any other characters in between.
-
$cfg['NavigationTreeTableLevel']
¶ -
Type: integer Default value: 1 Defines how many sublevels should be displayed when splitting up
tables by the above separator.
-
$cfg['NumRecentTables']
¶ -
Type: integer Default value: 10 The maximum number of recently used tables shown in the navigation
panel. Set this to 0 (zero) to disable the listing of recent tables.
-
$cfg['NumFavoriteTables']
¶ -
Type: integer Default value: 10 The maximum number of favorite tables shown in the navigation
panel. Set this to 0 (zero) to disable the listing of favorite tables.
-
$cfg['ZeroConf']
¶ -
Type: boolean Default value: true Enables Zero Configuration mode in which the user will be offered a choice to
create phpMyAdmin configuration storage in the current database
or use the existing one, if already present.This setting has no effect if the phpMyAdmin configuration storage database
is properly created and the related configuration directives (such as
$cfg['Servers'][$i]['pmadb']
and so on) are configured.
-
$cfg['NavigationLinkWithMainPanel']
¶ -
Type: boolean Default value: true Defines whether or not to link with main panel by highlighting
the current database or table.
-
$cfg['NavigationDisplayLogo']
¶ -
Type: boolean Default value: true Defines whether or not to display the phpMyAdmin logo at the top of
the navigation panel.
-
$cfg['NavigationLogoLink']
¶ -
Type: string Default value: 'index.php'
Enter the URL where the logo in the navigation panel will point to.
For use especially with self made theme which changes this.
For relative/internal URLs, you need to have leading « ./ « or trailing characters « ? « such as'./index.php?route=/server/sql?'
.
For external URLs, you should include URL protocol schemes (http
orhttps
) with absolute URLs.You may want to make the link open in a new browser tab, for that you need to use
$cfg['NavigationLogoLinkWindow']
-
$cfg['NavigationLogoLinkWindow']
¶ -
Type: string Default value: 'main'
Whether to open the linked page in the main window (
main
) or in a
new one (new
). Note: usenew
if you are linking to
phpmyadmin.net
.To open the link in the main window you will need to add the value of
$cfg['NavigationLogoLink']
to$cfg['CSPAllow']
because of the Content Security Policy header.
-
$cfg['NavigationTreeDisplayItemFilterMinimum']
¶ -
Type: integer Default value: 30 Defines the minimum number of items (tables, views, routines and
events) to display a JavaScript filter box above the list of items in
the navigation tree.To disable the filter completely some high number can be used (e.g. 9999)
-
$cfg['NavigationTreeDisplayDbFilterMinimum']
¶ -
Type: integer Default value: 30 Defines the minimum number of databases to display a JavaScript filter
box above the list of databases in the navigation tree.To disable the filter completely some high number can be used
(e.g. 9999)
-
$cfg['NavigationDisplayServers']
¶ -
Type: boolean Default value: true Defines whether or not to display a server choice at the top of the
navigation panel.
-
$cfg['DisplayServersList']
¶ -
Type: boolean Default value: false Defines whether to display this server choice as links instead of in a
drop-down.
-
$cfg['NavigationTreeDefaultTabTable']
¶ -
Type: string Default value: 'structure'
Defines the tab displayed by default when clicking the small icon next
to each table name in the navigation panel. The possible values are the
localized equivalent of:structure
sql
search
insert
browse
-
$cfg['NavigationTreeDefaultTabTable2']
¶ -
Type: string Default value: null Defines the tab displayed by default when clicking the second small icon next
to each table name in the navigation panel. The possible values are the
localized equivalent of:(empty)
structure
sql
search
insert
browse
-
$cfg['NavigationTreeEnableExpansion']
¶ -
Type: boolean Default value: true Whether to offer the possibility of tree expansion in the navigation panel.
-
$cfg['NavigationTreeShowTables']
¶ -
Type: boolean Default value: true Whether to show tables under database in the navigation panel.
-
$cfg['NavigationTreeShowViews']
¶ -
Type: boolean Default value: true Whether to show views under database in the navigation panel.
-
$cfg['NavigationTreeShowFunctions']
¶ -
Type: boolean Default value: true Whether to show functions under database in the navigation panel.
-
$cfg['NavigationTreeShowProcedures']
¶ -
Type: boolean Default value: true Whether to show procedures under database in the navigation panel.
-
$cfg['NavigationTreeShowEvents']
¶ -
Type: boolean Default value: true Whether to show events under database in the navigation panel.
-
$cfg['NavigationWidth']
¶ -
Type: integer Default value: 240 Navigation panel width, set to 0 to collapse it by default.
Main panel¶
-
$cfg['ShowStats']
¶ -
Type: boolean Default value: true Defines whether or not to display space usage and statistics about
databases and tables. Note that statistics requires at least MySQL
3.23.3 and that, at this date, MySQL doesn’t return such information
for Berkeley DB tables.
-
$cfg['ShowServerInfo']
¶ -
Type: boolean Default value: true Defines whether to display detailed server information on main page.
You can additionally hide more information by using
$cfg['Servers'][$i]['verbose']
.
-
$cfg['ShowPhpInfo']
¶ -
Type: boolean Default value: false Defines whether to display the PHP information or not at
the starting main (right) frame.Please note that to block the usage of
phpinfo()
in scripts, you have to
put this in yourphp.ini
:disable_functions = phpinfo()
Warning
Enabling phpinfo page will leak quite a lot of information about server
setup. Is it not recommended to enable this on shared installations.This might also make easier some remote attacks on your installations,
so enable this only when needed.
-
$cfg['ShowChgPassword']
¶ -
Type: boolean Default value: true Defines whether to display the Change password link or not at
the starting main (right) frame. This setting does not check MySQL commands
entered directly.Please note that enabling the Change password link has no effect
with config authentication mode: because of the hard coded password value
in the configuration file, end users can’t be allowed to change their
passwords.
-
$cfg['ShowCreateDb']
¶ -
Type: boolean Default value: true Defines whether to display the form for creating database or not at the
starting main (right) frame. This setting does not check MySQL commands
entered directly.
-
$cfg['ShowGitRevision']
¶ -
Type: boolean Default value: true Defines whether to display information about the current Git revision (if
applicable) on the main panel.
-
$cfg['MysqlMinVersion']
¶ -
Type: array Defines the minimum supported MySQL version. The default is chosen
by the phpMyAdmin team; however this directive was asked by a developer
of the Plesk control panel to ease integration with older MySQL servers
(where most of the phpMyAdmin features work).
Database structure¶
-
$cfg['ShowDbStructureCreation']
¶ -
Type: boolean Default value: false Defines whether the database structure page (tables list) has a
“Creation” column that displays when each table was created.
-
$cfg['ShowDbStructureLastUpdate']
¶ -
Type: boolean Default value: false Defines whether the database structure page (tables list) has a “Last
update” column that displays when each table was last updated.
-
$cfg['ShowDbStructureLastCheck']
¶ -
Type: boolean Default value: false Defines whether the database structure page (tables list) has a “Last
check” column that displays when each table was last checked.
-
$cfg['HideStructureActions']
¶ -
Type: boolean Default value: true Defines whether the table structure actions are hidden under a “More”
drop-down.
-
$cfg['ShowColumnComments']
¶ -
Type: boolean Default value: true Defines whether to show column comments as a column in the table structure view.
Browse mode¶
-
$cfg['TableNavigationLinksMode']
¶ -
Type: string Default value: 'icons'
Defines whether the table navigation links contain
'icons'
,'text'
or'both'
.
-
$cfg['ActionLinksMode']
¶ -
Type: string Default value: 'both'
If set to
icons
, will display icons instead of text for db and table
properties links (like Browse, Select,
Insert, …). Can be set to'both'
if you want icons AND text. When set totext
, will only show text.
-
$cfg['RowActionType']
¶ -
Type: string Default value: 'both'
Whether to display icons or text or both icons and text in table row action
segment. Value can be either of'icons'
,'text'
or'both'
.
-
$cfg['ShowAll']
¶ -
Type: boolean Default value: false Defines whether a user should be displayed a “Show all” button in browse
mode or not in all cases. By default it is shown only on small tables (less
than 500 rows) to avoid performance issues while getting too many rows.
-
$cfg['MaxRows']
¶ -
Type: integer Default value: 25 Number of rows displayed when browsing a result set and no LIMIT
clause is used. If the result set contains more rows, “Previous” and
“Next” links will be shown. Possible values: 25,50,100,250,500.
-
$cfg['Order']
¶ -
Type: string Default value: 'SMART'
Defines whether columns are displayed in ascending (
ASC
) order, in
descending (DESC
) order or in a “smart” (SMART
) order — I.E.
descending order for columns of type TIME, DATE, DATETIME and
TIMESTAMP, ascending order else- by default.Changed in version 3.4.0: Since phpMyAdmin 3.4.0 the default value is
'SMART'
.
-
$cfg['GridEditing']
¶ -
Type: string Default value: 'double-click'
Defines which action (
double-click
orclick
) triggers grid
editing. Can be deactivated with thedisabled
value.
-
$cfg['RelationalDisplay']
¶ -
Type: string Default value: 'K'
Defines the initial behavior for Options > Relational.
K
, which
is the default, displays the key whileD
shows the display column.
-
$cfg['SaveCellsAtOnce']
¶ -
Type: boolean Default value: false Defines whether or not to save all edited cells at once for grid
editing.
Editing mode¶
-
$cfg['ProtectBinary']
¶ -
Type: boolean or string Default value: 'blob'
Defines whether
BLOB
orBINARY
columns are protected from
editing when browsing a table’s content. Valid values are:false
to allow editing of all columns;'blob'
to allow editing of all columns exceptBLOBS
;'noblob'
to disallow editing of all columns exceptBLOBS
(the
opposite of'blob'
);'all'
to disallow editing of allBINARY
orBLOB
columns.
-
$cfg['ShowFunctionFields']
¶ -
Type: boolean Default value: true Defines whether or not MySQL functions fields should be initially
displayed in edit/insert mode. Since version 2.10, the user can toggle
this setting from the interface.
-
$cfg['ShowFieldTypesInDataEditView']
¶ -
Type: boolean Default value: true Defines whether or not type fields should be initially displayed in
edit/insert mode. The user can toggle this setting from the interface.
-
$cfg['InsertRows']
¶ -
Type: integer Default value: 2 Defines the default number of rows to be entered from the Insert page.
Users can manually change this from the bottom of that page to add or remove
blank rows.
-
$cfg['ForeignKeyMaxLimit']
¶ -
Type: integer Default value: 100 If there are fewer items than this in the set of foreign keys, then a
drop-down box of foreign keys is presented, in the style described by
the$cfg['ForeignKeyDropdownOrder']
setting.
-
$cfg['ForeignKeyDropdownOrder']
¶ -
Type: array Default value: array(‘content-id’, ‘id-content’) For the foreign key drop-down fields, there are several methods of
display, offering both the key and value data. The contents of the
array should be one or both of the following strings:content-id
,
id-content
.
Export and import settings¶
-
$cfg['ZipDump']
¶ -
Type: boolean Default value: true
-
$cfg['GZipDump']
¶ -
Type: boolean Default value: true
-
$cfg['BZipDump']
¶ -
Type: boolean Default value: true Defines whether to allow the use of zip/GZip/BZip2 compression when
creating a dump file
-
$cfg['CompressOnFly']
¶ -
Type: boolean Default value: true Defines whether to allow on the fly compression for GZip/BZip2
compressed exports. This doesn’t affect smaller dumps and allows users
to create larger dumps that won’t otherwise fit in memory due to php
memory limit. Produced files contain more GZip/BZip2 headers, but all
normal programs handle this correctly.
-
$cfg['Export']
¶ -
Type: array Default value: array(…) In this array are defined default parameters for export, names of
items are similar to texts seen on export page, so you can easily
identify what they mean.
-
$cfg['Export']['format']
¶ -
Type: string Default value: 'sql'
Default export format.
-
$cfg['Export']['method']
¶ -
Type: string Default value: 'quick'
Defines how the export form is displayed when it loads. Valid values
are:quick
to display the minimum number of options to configurecustom
to display every available option to configurecustom-no-form
same ascustom
but does not display the option
of using quick export
-
$cfg['Export']['charset']
¶ -
Type: string Default value: ''
Defines charset for generated export. By default no charset conversion is
done assuming UTF-8.
-
$cfg['Export']['file_template_table']
¶ -
Type: string Default value: '@TABLE@'
Default filename template for table exports.
-
$cfg['Export']['file_template_database']
¶ -
Type: string Default value: '@DATABASE@'
Default filename template for database exports.
-
$cfg['Export']['file_template_server']
¶ -
Type: string Default value: '@SERVER@'
Default filename template for server exports.
-
$cfg['Import']
¶ -
Type: array Default value: array(…) In this array are defined default parameters for import, names of
items are similar to texts seen on import page, so you can easily
identify what they mean.
-
$cfg['Import']['charset']
¶ -
Type: string Default value: ''
Defines charset for import. By default no charset conversion is done
assuming UTF-8.
Tabs display settings¶
-
$cfg['TabsMode']
¶ -
Type: string Default value: 'both'
Defines whether the menu tabs contain
'icons'
,'text'
or'both'
.
-
$cfg['PropertiesNumColumns']
¶ -
Type: integer Default value: 1 How many columns will be utilized to display the tables on the database
property view? When setting this to a value larger than 1, the type of the
database will be omitted for more display space.
-
$cfg['DefaultTabServer']
¶ -
Type: string Default value: 'welcome'
Defines the tab displayed by default on server view. The possible values
are the localized equivalent of:welcome
(recommended for multi-user setups)databases
,status
variables
privileges
-
$cfg['DefaultTabDatabase']
¶ -
Type: string Default value: 'structure'
Defines the tab displayed by default on database view. The possible values
are the localized equivalent of:structure
sql
search
operations
-
$cfg['DefaultTabTable']
¶ -
Type: string Default value: 'browse'
Defines the tab displayed by default on table view. The possible values
are the localized equivalent of:structure
sql
search
insert
browse
PDF Options¶
-
$cfg['PDFPageSizes']
¶ -
Type: array Default value: array('A3', 'A4', 'A5', 'letter', 'legal')
Array of possible paper sizes for creating PDF pages.
You should never need to change this.
-
$cfg['PDFDefaultPageSize']
¶ -
Type: string Default value: 'A4'
Default page size to use when creating PDF pages. Valid values are any
listed in$cfg['PDFPageSizes']
.
Languages¶
-
$cfg['DefaultLang']
¶ -
Type: string Default value: 'en'
Defines the default language to use, if not browser-defined or user-
defined. The corresponding language file needs to be in
locale/code/LC_MESSAGES/phpmyadmin.mo.
-
$cfg['DefaultConnectionCollation']
¶ -
Type: string Default value: 'utf8mb4_general_ci'
Defines the default connection collation to use, if not user-defined.
See the MySQL documentation for charsets
for list of possible values.
-
$cfg['Lang']
¶ -
Type: string Default value: not set Force language to use. The corresponding language file needs to be in
locale/code/LC_MESSAGES/phpmyadmin.mo.
-
$cfg['FilterLanguages']
¶ -
Type: string Default value: ''
Limit list of available languages to those matching the given regular
expression. For example if you want only Czech and English, you should
set filter to'^(cs|en)'
.
-
$cfg['RecodingEngine']
¶ -
Type: string Default value: 'auto'
You can select here which functions will be used for character set
conversion. Possible values are:- auto — automatically use available one (first is tested iconv, then
recode) - iconv — use iconv or libiconv functions
- recode — use recode_string function
- mb — use mbstring extension
- none — disable encoding conversion
Enabled charset conversion activates a pull-down menu in the Export
and Import pages, to choose the character set when exporting a file.
The default value in this menu comes from
$cfg['Export']['charset']
and$cfg['Import']['charset']
. - auto — automatically use available one (first is tested iconv, then
-
Type: string Default value: '//TRANSLIT'
Specify some parameters for iconv used in charset conversion. See
iconv documentation for details. By default
//TRANSLIT
is used, so that invalid characters will be
transliterated.
-
$cfg['AvailableCharsets']
¶ -
Type: array Default value: array(…) Available character sets for MySQL conversion. You can add your own
(any of supported by recode/iconv) or remove these which you don’t
use. Character sets will be shown in same order as here listed, so if
you frequently use some of these move them to the top.
Web server settings¶
-
$cfg['OBGzip']
¶ -
Type: string/boolean Default value: 'auto'
Defines whether to use GZip output buffering for increased speed in
HTTP transfers. Set to
true/false for enabling/disabling. When set to ‘auto’ (string),
phpMyAdmin tries to enable output buffering and will automatically
disable it if your browser has some problems with buffering. IE6 with
a certain patch is known to cause data corruption when having enabled
buffering.
-
$cfg['TrustedProxies']
¶ -
Type: array Default value: array() Lists proxies and HTTP headers which are trusted for
$cfg['Servers'][$i]['AllowDeny']['order']
. This list is by
default empty, you need to fill in some trusted proxy servers if you
want to use rules for IP addresses behind proxy.The following example specifies that phpMyAdmin should trust a
HTTP_X_FORWARDED_FOR (X-Forwarded-For
) header coming from the proxy
1.2.3.4:$cfg['TrustedProxies'] = array('1.2.3.4' => 'HTTP_X_FORWARDED_FOR');
The
$cfg['Servers'][$i]['AllowDeny']['rules']
directive uses the
client’s IP address as usual.
-
$cfg['GD2Available']
¶ -
Type: string Default value: 'auto'
Specifies whether GD >= 2 is available. If yes it can be used for MIME
transformations. Possible values are:- auto — automatically detect
- yes — GD 2 functions can be used
- no — GD 2 function cannot be used
-
$cfg['CheckConfigurationPermissions']
¶ -
Type: boolean Default value: true We normally check the permissions on the configuration file to ensure
it’s not world writable. However, phpMyAdmin could be installed on a
NTFS filesystem mounted on a non-Windows server, in which case the
permissions seems wrong but in fact cannot be detected. In this case a
sysadmin would set this parameter tofalse
.
-
$cfg['LinkLengthLimit']
¶ -
Type: integer Default value: 1000 Limit for length of URL in links. When length would be above this
limit, it is replaced by form with button. This is required as some web
servers (IIS) have problems with long URL .
-
$cfg['CSPAllow']
¶ -
Type: string Default value: ''
Additional string to include in allowed script and image sources in Content
Security Policy header.This can be useful when you want to include some external JavaScript files
inconfig.footer.inc.php
orconfig.header.inc.php
, which
would be normally not allowed by Content Security Policy.To allow some sites, just list them within the string:
$cfg['CSPAllow'] = 'example.com example.net';
New in version 4.0.4.
-
$cfg['DisableMultiTableMaintenance']
¶ -
Type: boolean Default value: false In the database Structure page, it’s possible to mark some tables then
choose an operation like optimizing for many tables. This can slow
down a server; therefore, setting this totrue
prevents this kind
of multiple maintenance operation.
Theme settings¶
Please directly modify
themes/themename/scss/_variables.scss
, although
your changes will be overwritten with the next update.
Design customization¶
-
$cfg['NavigationTreePointerEnable']
¶ -
Type: boolean Default value: true When set to true, hovering over an item in the navigation panel causes that item to be marked
(the background is highlighted).
-
$cfg['BrowsePointerEnable']
¶ -
Type: boolean Default value: true When set to true, hovering over a row in the Browse page causes that row to be marked (the background
is highlighted).
-
$cfg['BrowseMarkerEnable']
¶ -
Type: boolean Default value: true When set to true, a data row is marked (the background is highlighted) when the row is selected
with the checkbox.
-
$cfg['LimitChars']
¶ -
Type: integer Default value: 50 Maximum number of characters shown in any non-numeric field on browse
view. Can be turned off by a toggle button on the browse page.
-
$cfg['RowActionLinks']
¶ -
Type: string Default value: 'left'
Defines the place where table row links (Edit, Copy, Delete) would be
put when tables contents are displayed (you may have them displayed at
the left side, right side, both sides or nowhere).
-
$cfg['RowActionLinksWithoutUnique']
¶ -
Type: boolean Default value: false Defines whether to show row links (Edit, Copy, Delete) and checkboxes
for multiple row operations even when the selection does not have a unique key.
Using row actions in the absence of a unique key may result in different/more
rows being affected since there is no guaranteed way to select the exact row(s).
-
$cfg['RememberSorting']
¶ -
Type: boolean Default value: true If enabled, remember the sorting of each table when browsing them.
-
$cfg['TablePrimaryKeyOrder']
¶ -
Type: string Default value: 'NONE'
This defines the default sort order for the tables, having a primary key,
when there is no sort order defines externally.
Acceptable values : [‘NONE’, ‘ASC’, ‘DESC’]
-
Type: boolean Default value: true
-
Type: boolean Default value: true By setting the corresponding variable to
true
you can enable the
display of column comments in Browse or Property display. In browse
mode, the comments are shown inside the header. In property mode,
comments are displayed using a CSS-formatted dashed-line below the
name of the column. The comment is shown as a tool-tip for that
column.
-
$cfg['FirstDayOfCalendar']
¶ -
Type: integer Default value: 0 This will define the first day of week in the calendar. The number
can be set from 0 to 6, which represents the seven days of the week,
Sunday to Saturday respectively. This value can also be configured by the user
in Settings -> Features -> General -> First day of calendar field.
Text fields¶
-
$cfg['CharEditing']
¶ -
Type: string Default value: 'input'
Defines which type of editing controls should be used for CHAR and
VARCHAR columns. Applies to data editing and also to the default values
in structure editing. Possible values are:- input — this allows to limit size of text to size of columns in MySQL,
but has problems with newlines in columns - textarea — no problems with newlines in columns, but also no length
limitations
- input — this allows to limit size of text to size of columns in MySQL,
-
$cfg['MinSizeForInputField']
¶ -
Type: integer Default value: 4 Defines the minimum size for input fields generated for CHAR and
VARCHAR columns.
-
$cfg['MaxSizeForInputField']
¶ -
Type: integer Default value: 60 Defines the maximum size for input fields generated for CHAR and
VARCHAR columns.
-
$cfg['TextareaCols']
¶ -
Type: integer Default value: 40
-
$cfg['TextareaRows']
¶ -
Type: integer Default value: 15
-
$cfg['CharTextareaCols']
¶ -
Type: integer Default value: 40
-
$cfg['CharTextareaRows']
¶ -
Type: integer Default value: 7 Number of columns and rows for the textareas. This value will be
emphasized (*2) for SQL query
textareas and (*1.25) for SQL
textareas inside the query window.The Char* values are used for CHAR
and VARCHAR editing (if configured via$cfg['CharEditing']
).Changed in version 5.0.0: The default value was changed from 2 to 7.
-
$cfg['LongtextDoubleTextarea']
¶ -
Type: boolean Default value: true Defines whether textarea for LONGTEXT columns should have double size.
-
$cfg['TextareaAutoSelect']
¶ -
Type: boolean Default value: false Defines if the whole textarea of the query box will be selected on
click.
-
$cfg['EnableAutocompleteForTablesAndColumns']
¶ -
Type: boolean Default value: true Whether to enable autocomplete for table and column names in any
SQL query box.
SQL query box settings¶
-
$cfg['SQLQuery']['Edit']
¶ -
Type: boolean Default value: true Whether to display an edit link to change a query in any SQL Query
box.
-
$cfg['SQLQuery']['Explain']
¶ -
Type: boolean Default value: true Whether to display a link to explain a SELECT query in any SQL Query
box.
-
$cfg['SQLQuery']['ShowAsPHP']
¶ -
Type: boolean Default value: true Whether to display a link to wrap a query in PHP code in any SQL Query
box.
-
$cfg['SQLQuery']['Refresh']
¶ -
Type: boolean Default value: true Whether to display a link to refresh a query in any SQL Query box.
Web server upload/save/import directories¶
If PHP is running in safe mode, all directories must be owned by the same user
as the owner of the phpMyAdmin scripts.
If the directory where phpMyAdmin is installed is subject to an
open_basedir
restriction, you need to create a temporary directory in some
directory accessible by the PHP interpreter.
For security reasons, all directories should be outside the tree published by
webserver. If you cannot avoid having this directory published by webserver,
limit access to it either by web server configuration (for example using
.htaccess or web.config files) or place at least an empty index.html
file there, so that directory listing is not possible. However as long as the
directory is accessible by web server, an attacker can guess filenames to download
the files.
-
$cfg['UploadDir']
¶ -
Type: string Default value: ''
The name of the directory where SQL files have been uploaded by
other means than phpMyAdmin (for example, FTP). Those files are available
under a drop-down box when you click the database or table name, then the
Import tab.If
you want different directory for each user, %u will be replaced with
username.Please note that the file names must have the suffix “.sql”
(or “.sql.bz2” or “.sql.gz” if support for compressed formats is
enabled).This feature is useful when your file is too big to be
uploaded via HTTP, or when file
uploads are disabled in PHP.Warning
Please see top of this chapter (Web server upload/save/import directories) for instructions how
to setup this directory and how to make its usage secure.
-
$cfg['SaveDir']
¶ -
Type: string Default value: ''
The name of the webserver directory where exported files can be saved.
If you want a different directory for each user, %u will be replaced with the
username.Please note that the directory must exist and has to be writable for
the user running webserver.Warning
Please see top of this chapter (Web server upload/save/import directories) for instructions how
to setup this directory and how to make its usage secure.
-
$cfg['TempDir']
¶ -
Type: string Default value: './tmp/'
The name of the directory where temporary files can be stored. It is used
for several purposes, currently:- The templates cache which speeds up page loading.
- ESRI Shapefiles import, see 6.30 Import: How can I import ESRI Shapefiles?.
- To work around limitations of
open_basedir
for uploaded files, see
1.11 I get an ‘open_basedir restriction’ while uploading a file from the import tab..
This directory should have as strict permissions as possible as the only
user required to access this directory is the one who runs the webserver.
If you have root privileges, simply make this user owner of this directory
and make it accessible only by it:chown www-data:www-data tmp chmod 700 tmp
If you cannot change owner of the directory, you can achieve a similar
setup using ACL:chmod 700 tmp setfacl -m "g:www-data:rwx" tmp setfacl -d -m "g:www-data:rwx" tmp
If neither of above works for you, you can still make the directory
chmod 777, but it might impose risk of other users on system
reading and writing data in this directory.Warning
Please see top of this chapter (Web server upload/save/import directories) for instructions how
to setup this directory and how to make its usage secure.
Various display setting¶
-
$cfg['RepeatCells']
¶ -
Type: integer Default value: 100 Repeat the headers every X cells, or 0 to deactivate.
-
$cfg['QueryHistoryDB']
¶ -
Type: boolean Default value: false
-
$cfg['QueryHistoryMax']
¶ -
Type: integer Default value: 25 If
$cfg['QueryHistoryDB']
is set totrue
, all your
Queries are logged to a table, which has to be created by you (see
$cfg['Servers'][$i]['history']
). If set to false, all your
queries will be appended to the form, but only as long as your window is
opened they remain saved.When using the JavaScript based query window, it will always get updated
when you click on a new table/db to browse and will focus if you click on
Edit SQL after using a query. You can suppress updating the
query window by checking the box Do not overwrite this query
from outside the window below the query textarea. Then you can browse
tables/databases in the background without losing the contents of the
textarea, so this is especially useful when composing a query with tables
you first have to look in. The checkbox will get automatically checked
whenever you change the contents of the textarea. Please uncheck the button
whenever you definitely want the query window to get updated even though
you have made alterations.If
$cfg['QueryHistoryDB']
is set totrue
you can
specify the amount of saved history items using
$cfg['QueryHistoryMax']
.
-
$cfg['BrowseMIME']
¶ -
Type: boolean Default value: true Enable Transformations.
-
$cfg['MaxExactCount']
¶ -
Type: integer Default value: 50000 For InnoDB tables, determines for how large tables phpMyAdmin should
get the exact row count usingSELECT COUNT
. If the approximate row
count as returned bySHOW TABLE STATUS
is smaller than this value,
SELECT COUNT
will be used, otherwise the approximate count will be
used.Changed in version 4.8.0: The default value was lowered to 50000 for performance reasons.
Changed in version 4.2.6: The default value was changed to 500000.
-
$cfg['MaxExactCountViews']
¶ -
Type: integer Default value: 0 For VIEWs, since obtaining the exact count could have an impact on
performance, this value is the maximum to be displayed, using a
SELECT COUNT ... LIMIT
. Setting this to 0 bypasses any row
counting.
-
$cfg['NaturalOrder']
¶ -
Type: boolean Default value: true Sorts database and table names according to natural order (for
example, t1, t2, t10). Currently implemented in the navigation panel
and in Database view, for the table list.
-
Type: string Default value: 'closed'
If set to
'closed'
, the visual sliders are initially in a closed
state. A value of'open'
does the reverse. To completely disable
all visual sliders, use'disabled'
.
-
$cfg['UserprefsDisallow']
¶ -
Type: array Default value: array() Contains names of configuration options (keys in
$cfg
array) that
users can’t set through user preferences. For possible values, refer
to classes underlibraries/classes/Config/Forms/User/
.
-
$cfg['UserprefsDeveloperTab']
¶ -
Type: boolean Default value: false New in version 3.4.0.
Activates in the user preferences a tab containing options for
developers of phpMyAdmin.
Page titles¶
-
$cfg['TitleTable']
¶ -
Type: string Default value: '@HTTP_HOST@ / @VSERVER@ / @DATABASE@ / @TABLE@ | @PHPMYADMIN@'
-
$cfg['TitleDatabase']
¶ -
Type: string Default value: '@HTTP_HOST@ / @VSERVER@ / @DATABASE@ | @PHPMYADMIN@'
-
$cfg['TitleServer']
¶ -
Type: string Default value: '@HTTP_HOST@ / @VSERVER@ | @PHPMYADMIN@'
-
$cfg['TitleDefault']
¶ -
Type: string Default value: '@HTTP_HOST@ | @PHPMYADMIN@'
Allows you to specify window’s title bar. You can use 6.27 What format strings can I use?.
Theme manager settings¶
-
$cfg['ThemeManager']
¶ -
Type: boolean Default value: true Enables user-selectable themes. See 2.7 Using and creating themes.
-
$cfg['ThemeDefault']
¶ -
Type: string Default value: 'pmahomme'
The default theme (a subdirectory under
./themes/
).
-
$cfg['ThemePerServer']
¶ -
Type: boolean Default value: false Whether to allow different theme for each server.
-
$cfg['FontSize']
¶ -
Type: string Default value: ‘82%’ Deprecated since version 5.0.0: This setting was removed as the browser is more efficient,
thus no need of this option.Font size to use, is applied in CSS.
Default queries¶
-
$cfg['DefaultQueryTable']
¶ -
Type: string Default value: 'SELECT * FROM @TABLE@ WHERE 1'
-
$cfg['DefaultQueryDatabase']
¶ -
Type: string Default value: ''
Default queries that will be displayed in query boxes when user didn’t
specify any. You can use standard 6.27 What format strings can I use?.
MySQL settings¶
-
$cfg['DefaultFunctions']
¶ -
Type: array Default value: array('FUNC_CHAR' => '', 'FUNC_DATE' => '', 'FUNC_NUMBER' => '', 'FUNC_SPATIAL' => 'GeomFromText', 'FUNC_UUID' => 'UUID', 'first_timestamp' => 'NOW')
Functions selected by default when inserting/changing row, Functions
are defined for meta types as (FUNC_NUMBER
,FUNC_DATE
,FUNC_CHAR
,
FUNC_SPATIAL
,FUNC_UUID
) and forfirst_timestamp
, which is used
for first timestamp column in table.Example configuration
$cfg['DefaultFunctions'] = [ 'FUNC_CHAR' => '', 'FUNC_DATE' => '', 'FUNC_NUMBER' => '', 'FUNC_SPATIAL' => 'ST_GeomFromText', 'FUNC_UUID' => 'UUID', 'first_timestamp' => 'UTC_TIMESTAMP', ];
Default options for Transformations¶
-
$cfg['DefaultTransformations']
¶ -
Type: array Default value: An array with below listed key-values
-
$cfg['DefaultTransformations']['Substring']
¶ -
Type: array Default value: array(0, ‘all’, ‘…’)
-
$cfg['DefaultTransformations']['Bool2Text']
¶ -
Type: array Default value: array(‘T’, ‘F’)
-
$cfg['DefaultTransformations']['External']
¶ -
Type: array Default value: array(0, ‘-f /dev/null -i -wrap -q’, 1, 1)
-
$cfg['DefaultTransformations']['PreApPend']
¶ -
Type: array Default value: array(‘’, ‘’)
-
$cfg['DefaultTransformations']['Hex']
¶ -
Type: array Default value: array(‘2’)
-
$cfg['DefaultTransformations']['DateFormat']
¶ -
Type: array Default value: array(0, ‘’, ‘local’)
-
$cfg['DefaultTransformations']['Inline']
¶ -
Type: array Default value: array(‘100’, 100)
-
$cfg['DefaultTransformations']['TextImageLink']
¶ -
Type: array Default value: array(‘’, 100, 50)
-
$cfg['DefaultTransformations']['TextLink']
¶ -
Type: array Default value: array(‘’, ‘’, ‘’)
Console settings¶
Note
These settings are mostly meant to be changed by user.
-
$cfg['Console']['StartHistory']
¶ -
Type: boolean Default value: false Show query history at start
-
$cfg['Console']['AlwaysExpand']
¶ -
Type: boolean Default value: false Always expand query messages
-
$cfg['Console']['CurrentQuery']
¶ -
Type: boolean Default value: true Show current browsing query
-
$cfg['Console']['EnterExecutes']
¶ -
Type: boolean Default value: false Execute queries on Enter and insert new line with Shift + Enter
-
$cfg['Console']['DarkTheme']
¶ -
Type: boolean Default value: false Switch to dark theme
-
$cfg['Console']['Mode']
¶ -
Type: string Default value: ‘info’ Console mode
-
$cfg['Console']['Height']
¶ -
Type: integer Default value: 92 Console height
Developer¶
Warning
These settings might have huge effect on performance or security.
-
$cfg['environment']
¶ -
Type: string Default value: 'production'
Sets the working environment.
This only needs to be changed when you are developing phpMyAdmin itself.
Thedevelopment
mode may display debug information in some places.Possible values are
'production'
or'development'
.
-
$cfg['DBG']
¶ -
Type: array Default value: array(…)
-
$cfg['DBG']['sql']
¶ -
Type: boolean Default value: false Enable logging queries and execution times to be
displayed in the console’s Debug SQL tab.
-
$cfg['DBG']['sqllog']
¶ -
Type: boolean Default value: false Enable logging of queries and execution times to the syslog.
Requires$cfg['DBG']['sql']
to be enabled.
-
$cfg['DBG']['demo']
¶ -
Type: boolean Default value: false Enable to let server present itself as demo server.
This is used for phpMyAdmin demo server.It currently changes following behavior:
- There is welcome message on the main page.
- There is footer information about demo server and used Git revision.
- The setup script is enabled even with existing configuration.
- The setup does not try to connect to the MySQL server.
-
$cfg['DBG']['simple2fa']
¶ -
Type: boolean Default value: false Can be used for testing two-factor authentication using Simple two-factor authentication.
Examples¶
See following configuration snippets for typical setups of phpMyAdmin.
Basic example¶
Example configuration file, which can be copied to config.inc.php
to
get some core configuration layout; it is distributed with phpMyAdmin as
config.sample.inc.php
. Please note that it does not contain all
configuration options, only the most frequently used ones.
<?php /** * phpMyAdmin sample configuration, you can use it as base for * manual configuration. For easier setup you can use setup/ * * All directives are explained in documentation in the doc/ folder * or at <https://docs.phpmyadmin.net/>. */ declare(strict_types=1); /** * This is needed for cookie based authentication to encrypt password in * cookie. Needs to be 32 chars long. */ $cfg['blowfish_secret'] = ''; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */ /** * Servers configuration */ $i = 0; /** * First server */ $i++; /* Authentication type */ $cfg['Servers'][$i]['auth_type'] = 'cookie'; /* Server parameters */ $cfg['Servers'][$i]['host'] = 'localhost'; $cfg['Servers'][$i]['compress'] = false; $cfg['Servers'][$i]['AllowNoPassword'] = false; /** * phpMyAdmin configuration storage settings. */ /* User used to manipulate with storage */ // $cfg['Servers'][$i]['controlhost'] = ''; // $cfg['Servers'][$i]['controlport'] = ''; // $cfg['Servers'][$i]['controluser'] = 'pma'; // $cfg['Servers'][$i]['controlpass'] = 'pmapass'; /* Storage database and tables */ // $cfg['Servers'][$i]['pmadb'] = 'phpmyadmin'; // $cfg['Servers'][$i]['bookmarktable'] = 'pma__bookmark'; // $cfg['Servers'][$i]['relation'] = 'pma__relation'; // $cfg['Servers'][$i]['table_info'] = 'pma__table_info'; // $cfg['Servers'][$i]['table_coords'] = 'pma__table_coords'; // $cfg['Servers'][$i]['pdf_pages'] = 'pma__pdf_pages'; // $cfg['Servers'][$i]['column_info'] = 'pma__column_info'; // $cfg['Servers'][$i]['history'] = 'pma__history'; // $cfg['Servers'][$i]['table_uiprefs'] = 'pma__table_uiprefs'; // $cfg['Servers'][$i]['tracking'] = 'pma__tracking'; // $cfg['Servers'][$i]['userconfig'] = 'pma__userconfig'; // $cfg['Servers'][$i]['recent'] = 'pma__recent'; // $cfg['Servers'][$i]['favorite'] = 'pma__favorite'; // $cfg['Servers'][$i]['users'] = 'pma__users'; // $cfg['Servers'][$i]['usergroups'] = 'pma__usergroups'; // $cfg['Servers'][$i]['navigationhiding'] = 'pma__navigationhiding'; // $cfg['Servers'][$i]['savedsearches'] = 'pma__savedsearches'; // $cfg['Servers'][$i]['central_columns'] = 'pma__central_columns'; // $cfg['Servers'][$i]['designer_settings'] = 'pma__designer_settings'; // $cfg['Servers'][$i]['export_templates'] = 'pma__export_templates'; /** * End of servers configuration */ /** * Directories for saving/loading files from server */ $cfg['UploadDir'] = ''; $cfg['SaveDir'] = ''; /** * Whether to display icons or text or both icons and text in table row * action segment. Value can be either of 'icons', 'text' or 'both'. * default = 'both' */ //$cfg['RowActionType'] = 'icons'; /** * Defines whether a user should be displayed a "show all (records)" * button in browse mode or not. * default = false */ //$cfg['ShowAll'] = true; /** * Number of rows displayed when browsing a result set. If the result * set contains more rows, "Previous" and "Next". * Possible values: 25, 50, 100, 250, 500 * default = 25 */ //$cfg['MaxRows'] = 50; /** * Disallow editing of binary fields * valid values are: * false allow editing * 'blob' allow editing except for BLOB fields * 'noblob' disallow editing except for BLOB fields * 'all' disallow editing * default = 'blob' */ //$cfg['ProtectBinary'] = false; /** * Default language to use, if not browser-defined or user-defined * (you find all languages in the locale folder) * uncomment the desired line: * default = 'en' */ //$cfg['DefaultLang'] = 'en'; //$cfg['DefaultLang'] = 'de'; /** * How many columns should be used for table display of a database? * (a value larger than 1 results in some information being hidden) * default = 1 */ //$cfg['PropertiesNumColumns'] = 2; /** * Set to true if you want DB-based query history.If false, this utilizes * JS-routines to display query history (lost by window close) * * This requires configuration storage enabled, see above. * default = false */ //$cfg['QueryHistoryDB'] = true; /** * When using DB-based query history, how many entries should be kept? * default = 25 */ //$cfg['QueryHistoryMax'] = 100; /** * Whether or not to query the user before sending the error report to * the phpMyAdmin team when a JavaScript error occurs * * Available options * ('ask' | 'always' | 'never') * default = 'ask' */ //$cfg['SendErrorReports'] = 'always'; /** * 'URLQueryEncryption' defines whether phpMyAdmin will encrypt sensitive data from the URL query string. * 'URLQueryEncryptionSecretKey' is a 32 bytes long secret key used to encrypt/decrypt the URL query string. */ //$cfg['URLQueryEncryption'] = true; //$cfg['URLQueryEncryptionSecretKey'] = ''; /** * You can find more configuration options in the documentation * in the doc/ folder or at <https://docs.phpmyadmin.net/>. */
Warning
Don’t use the controluser ‘pma’ if it does not yet exist and don’t use ‘pmapass’
as password.
Example for signon authentication¶
This example uses examples/signon.php
to demonstrate usage of Signon authentication mode:
<?php $i = 0; $i++; $cfg['Servers'][$i]['auth_type'] = 'signon'; $cfg['Servers'][$i]['SignonSession'] = 'SignonSession'; $cfg['Servers'][$i]['SignonURL'] = 'examples/signon.php';
Example for IP address limited autologin¶
If you want to automatically login when accessing phpMyAdmin locally while asking
for a password when accessing remotely, you can achieve it using following snippet:
if ($_SERVER['REMOTE_ADDR'] === '127.0.0.1') { $cfg['Servers'][$i]['auth_type'] = 'config'; $cfg['Servers'][$i]['user'] = 'root'; $cfg['Servers'][$i]['password'] = 'yourpassword'; } else { $cfg['Servers'][$i]['auth_type'] = 'cookie'; }
Note
Filtering based on IP addresses isn’t reliable over the internet, use it
only for local address.
Example for using multiple MySQL servers¶
You can configure any number of servers using $cfg['Servers']
,
following example shows two of them:
<?php $cfg['blowfish_secret'] = 'multiServerExample70518'; // any string of your choice $i = 0; $i++; // server 1 : $cfg['Servers'][$i]['auth_type'] = 'cookie'; $cfg['Servers'][$i]['verbose'] = 'no1'; $cfg['Servers'][$i]['host'] = 'localhost'; // more options for #1 ... $i++; // server 2 : $cfg['Servers'][$i]['auth_type'] = 'cookie'; $cfg['Servers'][$i]['verbose'] = 'no2'; $cfg['Servers'][$i]['host'] = 'remote.host.addr';//or ip:'10.9.8.1' // this server must allow remote clients, e.g., host 10.9.8.% // not only in mysql.host but also in the startup configuration // more options for #2 ... // end of server sections $cfg['ServerDefault'] = 0; // to choose the server on startup // further general options ...
Google Cloud SQL with SSL¶
To connect to Google Could SQL, you currently need to disable certificate
verification. This is caused by the certificate being issued for CN matching
your instance name, but you connect to an IP address and PHP tries to match
these two. With verification you end up with error message like:
Peer certificate CN=`api-project-851612429544:pmatest' did not match expected CN=`8.8.8.8'
Warning
With disabled verification your traffic is encrypted, but you’re open to
man in the middle attacks.
To connect phpMyAdmin to Google Cloud SQL using SSL download the client and
server certificates and tell phpMyAdmin to use them:
// IP address of your instance $cfg['Servers'][$i]['host'] = '8.8.8.8'; // Use SSL for connection $cfg['Servers'][$i]['ssl'] = true; // Client secret key $cfg['Servers'][$i]['ssl_key'] = '../client-key.pem'; // Client certificate $cfg['Servers'][$i]['ssl_cert'] = '../client-cert.pem'; // Server certification authority $cfg['Servers'][$i]['ssl_ca'] = '../server-ca.pem'; // Disable SSL verification (see above note) $cfg['Servers'][$i]['ssl_verify'] = false;
reCaptcha using hCaptcha¶
$cfg['CaptchaApi'] = 'https://www.hcaptcha.com/1/api.js'; $cfg['CaptchaCsp'] = 'https://hcaptcha.com https://*.hcaptcha.com'; $cfg['CaptchaRequestParam'] = 'h-captcha'; $cfg['CaptchaResponseParam'] = 'h-captcha-response'; $cfg['CaptchaSiteVerifyURL'] = 'https://hcaptcha.com/siteverify'; // This is the secret key from hCaptcha dashboard $cfg['CaptchaLoginPrivateKey'] = '0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'; // This is the site key from hCaptcha dashboard $cfg['CaptchaLoginPublicKey'] = 'xxx-xxx-xxx-xxx-xxxx';
Open up [web_root]/libraries/Config.class.php
add these lines to the beginning of the method load
:
var_dump( $this->default_source);
var_dump( CONFIG_FILE);
die;
Open phpmyadmin. This is the order of config files loaded, they make a variable $cfg
which is the config of PMA, for me the output was:
'[mywebroot]./libraries/config.default.php'
'/etc/phpmyadmin/config.inc.php'
Make sure the last file, which is for local changes, exist and have correct permissions. Then get rid of the added lines.
More info
PMA loads it’s global configuration in the file libraries/common.inc.php:306
.
$GLOBALS['PMA_Config'] = new PMA_Config(CONFIG_FILE);
The global is an instance of PMA_Config
whose constructor calls the load
method. In load method, the parameter passed to the constructor, CONFIG_FILE
is used to load the configuration.
Предупреждение для пользователей Mac: PHP по-видимому не любит Mac символы переноса строки («r»). Таким образом, выбирайте в вашем текстовом редакторе опцию, позволяющую использовать *nix-овый перенос строки («n»), перед сохранением модифицированного скрипта.
Примечание: Почти все конфигурируемые данные находятся в файле config.inc.php. Параметры, которые относятся к дизайну (цвета, например) находятся в файле themes/themename/layout.inc.php. Для изменения шапки и основания страниц необходимо откорректировать файлы config.footer.inc.php и config.header.inc.php.
$cfg[‘PmaAbsoluteUri’] строка
Установите здесь полный URL директории где установлен phpMyAdmin. Например, http://www.your_web.net/path_to_your_phpMyAdmin_directory/.
Начиная с версии 2.3.0, можно проигнорировать эту переменную и поставить в этой строке пробел — в большинстве случаев phpMyAdmin автоматически определяет правильный параметр. Подробнее читайте в конфигурационном файле.
Не забудьте поставить слэш в конце указанного Вами URL. URL должен содержать только допустимые символы, и помните, что на некоторых серверах путь регистрозависим.
Если Вы получаете ошибку при автоопределении пути, пожалуйста отправьте сообщение об ошибке с помощью bug tracker, чтобы разработчики могли исправить код.
$cfg[‘PmaNoRelation_DisableWarning’] булево выражение
Начиная с версии 2.3.0 phpMyAdmin предлагает множество возможностей для работы с головной / подчиненными (master / foreign) таблицами (см. $cfg[‘Servers’][$i][‘pmadb’]).
Если у Вас не получается настроить работу с головной и подчиненными таблицами, посмотрите страницу «Структура» («Structure») вашей базы. Здесь Вы найдете ссылку, которая проанализирует почему эта опция недоступна. Если Вы не хотите использовать эту опцию установите значение TRUE чтобы предотвратить появление подобных сообщений.
$cfg[‘blowfish_secret’] строка
Начиная с версии 2.5.2, ‘cookie’ auth_type (cookie-аутентификация) использует алгоритм blowfish для шифрования пароля.
Если вы используете ‘cookie’ auth_type, введите здесь случайную идентификационную фразу, которая будет использоваться в работе алгоритма ‘blowfish’. Максимальный размер фразы 46 символов.
$cfg[‘Servers’] массив
Начиная с версии 1.4.2, phpMyAdmin поддерживает администрирование нескольких MySQL серверов. Поэтому, был добавлен массив $cfg[‘Servers’], который содержит информацию об учетных записях для серверов. Первый $cfg[‘Servers’][$i][‘host’] содержит имя хоста первого сервера, второй $cfg[‘Servers’][$i][‘host’] — имя хоста второго сервера, и т.д. Если вы администрируете только один сервер, просто оставьте пустыми остальные $cfg[‘Server’]-записи.
$cfg[‘Servers’][$i][‘host’] строка
Имя хоста или IP адрес $i-го MySQL-сервера. Например, localhost.
$cfg[‘Servers’][$i][‘port’] строка
Номер порта $i-го MySQL-сервера. По умолчанию (если специально не указывается) поддставляется значение 3306. Если Вы используете «localhost» в качестве имени хоста, MySQL игнорирует номер этого порта и соединяется с сокетом, так что если Вы хотите соединиться с портом отличным от предлагаемого по умолчанию, используйте «127.0.0.1» или реальное имя хоста в $cfg[‘Servers’][$i][‘host’].
$cfg[‘Servers’][$i][‘socket’] строка
Путь к сокету. По умолчанию запись не заполнена.
$cfg[‘Servers’][$i][‘ssl’] булево выражение
Определяет использовать ли SSL для соединения с MySQL-сервером. По умолчанию FALSE
$cfg[‘Servers’][$i][‘connect_type’] строка
Определяет тип соединения с MySQL сервером. Возможные варианты ‘socket’ и ‘tcp’. По умолчанию ставится ‘tcp’ т.к. таким образом, гарантируется работоспособность практически на всех MySQL-серверах, в то время как сокеты не поддерживаются некоторыми платформами.
Чтобы использовать режим сокетов, ваш MySQL сервер должен быть на той же самой машине, что и сам веб-сервер.
$cfg[‘Servers’][$i][‘extension’] строка
Какое php MySQL-расширение использовать для соединения. Корректные варианты:
mysql : классическое MySQL расширение, является рекомендованным и устанавливается по умолчанию.
mysqli : усовершенствованное расширение MySQL. Это расширение стало доступно с php 5.0.0 и рекомендуется для соединения с сервером, на котором запущен MySQL 4.1.x
$cfg[‘Servers’][$i][‘compress’] булево выражение
Определяет использовать ли сжатый протокол для соединения MySQL сервера или нет. Эта опция требует чтобы версия PHP >= 4.3.0.
$cfg[‘Servers’][$i][‘controluser’] строка
$cfg[‘Servers’][$i][‘controlpass’] строка
Заметка: начиная с phpMyAdmin 2.6.1, конфигурирование controluser для разрешения HTTP и cookie аутентификации возможно только для MySQL серверов старше чем 4.1.2.
Этот специальный аккаунт используется для 2 различных целей: реализовать реляционные возможности (см. $cfg[‘Servers’][$i][‘pmadb’]) и, для MySQL сервера >= 4.1.2, чтобы допустить многопользовательскую установку (режим http или cookie-аутентификации).
При использовании режима HTTP или cookie-аутентификации (либо config-аутентификации, начиная с phpMyAdmin версии 2.2.1), необходимо предоставить подробности об MySQL аккаунте, который имеет привилегию SELECT для таблиц mysql.user (все столбцы за исключением «Password»), mysql.db (все столбцы) и mysql.tables_priv (все столбцы за исключением «Grantor» & «Timestamp»). Этот аккаунт используется для задания базы данных которую пользователь увидит при идентификации.
Ознакомьтесь с разделом «Использование режимов аутентификации» для получения дополнительной информации.
Обратите внимание, что если вы пытаетесь начать сеанс с phpMyAdmin как «controluser», Вы можете получить ряд ошибок, в зависимости от того какие привилегии вы дали «controluser». phpMyAdmin не поддерживает напрямую учетную запись для «controluser». В phpMyAdmin до версии 2.2.5, он назывался «stduser/stdpass».
$cfg[‘Servers’][$i][‘auth_type’] строка [‘http’|’cookie’|’config’|’signon’]
Для сервера может быть использована http-, cookie-, config- или signon-аутентификация.
Ознакомьтесь с разделом «Использование режимов аутентификации» для получения дополнительной информации.
$cfg[‘Servers’][$i][‘user’] строка
$cfg[‘Servers’][$i][‘password’] строка
Пара user/password, которую phpMyAdmin использует для соединения с MySQL-сервером. Эта пара user/password не нужна, если используется HTTP или cookie-аутентификация — в этом случае она должна быть пустой.
$cfg[‘Servers’][$i][‘nopassword’] булево выражение
Разрешает попытку авторизироваться без пароля, в случае неудачной авторизации с использованием пароля. Эта опция может использоваться совместно с http-аутентификацией, когда phpMyAdmin использует имя пользователя из ‘user’, а пароль для соединения с MySQL пустой. Сначала осуществляется попытка авторизации с использованием пароля, если она завершается неудачно — осуществляется попытка подключения к MySQL-серверу без пароля.
$cfg[‘Servers’][$i][‘only_db’] строка или массив
Если задать (если несколько — массив) имя/имена базы данных, то пользователю будут доступны только эта/эти база/бызы данных. Начиная с phpMyAdmin 2.2.1, имена баз данных могут содержать символы обобщения MySQL («_» и «%»): если вы хотите использовать эти символы предварите их слешем (например, надо писать так: ‘my_db’, а так писать не надо: ‘my_db’).
Эта настройка — эффективный способ снизить нагрузку на сервер, так как последнему не придется послать запросы на получение списка доступных баз данных. Но он не заменяет правила привилегий к MySQL-серверу баз данных. Если задан, это означает, что только эти базы данных будут отображаться, но не означает, что все остальные базы данных не будут использоваться.
Пример использования более чем одной базы данных: $cfg[‘Servers’][$i][‘only_db’] = array(‘db1’, ‘db2’);
Что касается phpMyAdmin 2.5.5 порядок внутри массива используется для сортировки баз данных в левом фрейме, таким образом, вы можете самостоятельно задавать порядок сортировки ваших баз данных.
Если Вы хотите увидеть определенную базу данных вверху, но не хотите трогать остальные — вам не нужно определять все остальные базы данных. Используйте: $cfg[‘Servers’][$i][‘only_db’] = array(‘db3’, ‘db4’, ‘*’); в этом случае phpMyAdmin отобразит базы данных db3 и db4 на верху, а остальные будут упорядочены в алфавитном порядке.
$cfg[‘Servers’][$i][‘hide_db’] строка
Регулярное выражение, определяющее сокрытие отдельных баз данных. Важно иметь ввиду, что скрываются они только от листинга, но, тем не менее, пользователи имеют доступ к ним (используя, например, область SQL запроса). Чтобы запретить доступ пользователям, используйте механизм MySQL привилегий. Например, чтобы скрыть все базы данных, начинающиеся с символа «a», используйте следующее регулярное выражение:
$cfg[‘Servers’][$i][‘hide_db’] = ‘^a’; чтобы скрыть одновременно и базу данных «db1», и «db2» используйте:
$cfg[‘Servers’][$i][‘hide_db’] = ‘(db1|db2)’; Для получения дополнительной информации см. мануал PHP по регулярным выражениям в формате PCRE.
$cfg[‘Servers’][$i][‘verbose’] строка
Полезна только в том случае, если phpMyAdmin используется с несколькими серверами. Если установлена, эта строка будет отображаться вместо имени хоста в выпадающем меню на главной странице. Это может быть полезным если необходимо показать только определенные базы данных.
$cfg[‘Servers’][$i][‘pmadb’] строка
Имя базы данных, содержащей информацию о связях таблиц.
Прочитайте также подраздел данного FAQ «Инфраструктура связанных таблиц», чтобы ознакомиться с преимуществами использования данной инфраструктуры, а также для быстрого создания этой базы данных и необходимых таблиц.
Если Вы единственный пользователь phpMyAdmin, то можете использовать текущую базу данных, для хранения специальных таблиц; в этом случае, вставьте текущее название базы данных в $cfg [‘Серверы’] [$i] [‘pmadb’]. В случае многопользовательского режима, задайте в качестве значения этого параметра имя вашей центральной базы данных, содержащей инфраструктуру связанных таблиц.
$cfg[‘Servers’][$i][‘bookmarktable’] строка
Начиная с релиза 2.2.0, phpMyAdmin позволяет закладывать запросы, что может быть удобно для регулярно выполняемых запросов. Чтобы использовать эту опцию:
$cfg[‘Servers’][$i][‘relation’] строка
Начиная с релиза 2.2.4 появилась возможность указания в специальной таблице, какое поле является ключом в другой таблице (внешний ключ — foreign key). phpMyAdmin в настоящее время для этого:
Ключи могут быть числовые или символьные.
Чтобы использовать эту опцию:
Помните, что текущая версия master_db должна быть такой же, как и foreign_db. Именно на основе их полей будут строиться связи базы данных.
$cfg[‘Servers’][$i][‘table_info’] строка
Начиная с релиза 2.3.0, появилась возможность указания в специальной таблице (‘table_info’), какие поля будут отображаться через всплывающие подсказки при наведении на курсора на соответствующий ключ.
Эта конфигурационная переменная будет хранить имя этой специальной таблицы. Чтобы использовать эту опцию:
Дополнительно: см. FAQ 6.7.
$cfg[‘Servers’][$i][‘table_coords’] строка
$cfg[‘Servers’][$i][‘pdf_pages’] строка
Начиная с релиза 2.3.0 phpMyAdmin позволяет создавать PDF страницы, наглядно показывающие связи между таблицами базы данных. Для использования этой опции необходимы две таблицы: «pdf_pages» (хранит информацию о доступных PDF страницах) и «table_coords» (хранит координаты размещения на схеме каждой таблицы).
Вы должны использовать опцию «relation» (связи).
Чтобы использовать эту опцию:
Дополнительно: см. FAQ 6.8.
$cfg[‘Servers’][$i][‘column_info’] строка
Начиная с релиза 2.3.0, Вы можете хранить комментарии, описывающие каждый столбец для каждой таблицы, которые затем будут отображаться в «Версии для печати» («printview»).
Начиная с релиза 2.5.0, комментарии к столбцам таблицы на странице «Структура таблицы» отображаются в виде всплывающей подсказки (сам столбец для которого создан комментарий подчеркивается пунктирной линией), на странице «Browse» (просмотр) комментарии врезаны в шапку таблицы под заголовками столбцов, на странице «Print View» (версия для печати) комментарии полей расположены в специальном столбце. Комментарии будут также отображаются в дампе таблиц.
Также нововведением в релизе 2.5.0 стал механизм MIME-преобразований, который тоже базируется на нижеприведенной табличной структуре. Смотри «Преобразования» для дополнительной информации. Для использования механизма MIME-преобразований, таблица column_info имеет три новых поля: ‘mimetype’, ‘transformation’, ‘transformation_options’.
Чтобы использовать эту опцию:
$cfg[‘Servers’][$i][‘history’] строка
Начиная с релиза 2.5.0 возможно сохранение SQL-истории, под которой подразумевается вся совокупность запросов, которые вводятся вручную через интерфейс phpMyAdmin. Если Вы не хотите использовать историю, которая сохраняется в таблице, можете использовать JavaScript-базируемую историю, но в последнем случае, вся история будет удалена при закрытии окна.
Используя $cfg[‘QueryHistoryMax’] можно задавать количество элементов истории, которые необходимо сохранить. При начале каждого нового сеанса этот список будет урезан до максимально допустимого значения.
История запросов также доступна, если Вы используете JavaScript-базируемое окно запросов, смотрите $cfg[‘QueryFrame’].
Чтобы использовать эту опцию:
$cfg[‘Servers’][$i][‘designer_coords’] строка
Начиная с релиза 2.10.0 доступен Designer — интерфейс, который позволяет визуально управлять связями.
Чтоб разрешить использование данной возможности:
- установите pmadb и настройте инфраструктуру связанных таблиц
- укажите название таблицы в конфигурационной переменной $cfg[‘Servers’][$i][‘designer_coords’]
$cfg[‘Servers’][$i][‘verbose_check’] булево выражение
Так как релиз 2.5.0 включил поддержку MIME-преобразований, таблица column_info была дополнена тремя новыми полями. Если вышеупомянутая переменная имеет значение TRUE (по умолчанию) phpMyAdmin будет проверять, доступна ли последняя структура таблицы. Если нет, то он выдаст предупреждение суперпользователю.
Вы можете отключить эту проверку, установив значение переменной как false, что может способствовать росту производительности.
Рекомендуется устанавливать как FALSE, когда Вы уверены, что структура вашей таблицы актуальна и не нуждается в обновлении.
$cfg[‘Servers’][$i][‘AllowRoot’] булево выражение
Определяет, разрешен ли доступ к корню, и является всего лишь упрощенным вариантом нижеописанного правила.
$cfg[‘Servers’][$i][‘AllowDeny’][‘order’] строка
Команда ‘Order’ управляет последовательностью обработки остальных команд управления доступом. Если ‘order’ — не задана (пустая), тогда недоступна IP-аутентификация.
Если установить порядок ‘deny,allow’, обработка команд происходит в обратном порядке, т.е. сначала обрабатываются команды запрещения доступа, потом команды разрешения доступа. Доступ разрешен по умолчанию. Любому клиенту, который не соответствует команде запрещения доступа или действительно соответствует команде разрешения доступа, будет разрешен доступ к серверу.
Если установлен порядок ‘allow,deny’ — первыми проверяются команды разрешения доступа (список этих команд начинается со слова ‘Allow’). Если какая-либо команда отработала успешно, процесс прерывается и пользователю разрешается выполнение ftp-команд, перечисленных в первой строке секции. Иначе обрабатываются команды запрещения доступа (их список начинается со слова ‘Deny’). Если какая-либо команда отработала успешно, выполнение ftp-команд запрещается. Доступ запрещен по умолчанию. Любому клиенту, который не соответствует команде разрешения доступа или соответствует команде запрещения доступа, будет отказано в доступе к серверу.
Если порядок установлен как ‘explicit’, аутентификация выполняется аналогично порядку ‘deny,allow’, с добавлением ограничения, что комбинация вашего host/username должна быть записана в списке команд разрешения (allow rules), и отсутствовать в списке команд запрещения (deny rules). Это наиболее безопасный способ использования команд Allow/Deny rules, который был доступен в Апаче через спецификацию команд разрешения и запрещения без установки других команд. См. также $cfg[‘TrustedProxies’] для определения IP-адреса, находящегося за прокси-сервером.
$cfg[‘Servers’][$i][‘AllowDeny’][‘rules’] массив или строка
Общий формат для правил:
<‘allow’ | ‘deny’> <username> [from] <ipmask>
Если Вы желаете указать всех пользователей, можно использовать ‘%’ как групповой символ в поле «username».
Есть несколько шаблонов, которые Вы также можете использовать в поле ipmask:
‘all’ -> 0.0.0.0/0
‘localhost’ -> 127.0.0.1/8
Наличие пустого списка правила эквивалентно использованию ‘allow % from all’, если ваши правила доступа обозначены как ‘deny,allow’ или ‘deny % from all’, если ваши права доступа обозначены как ‘allow,deny’ или ‘explicit’.
Для IP согласования системы, необходимо:
xxx.xxx.xxx.xxx (точный IP адрес)
xxx.xxx.xxx.[yyy-zzz] (диапазон IP адресов)
xxx.xxx.xxx.xxx/nn (CIDR, Classless Inter-Domain Routing (безклассовую внутридоменную маршрутизацию) тип IP адреса)
Но следующий пример будет нерабочим:
xxx.xxx.xxx.xx[yyy-zzz] (частичный диапазон IP адреса)
$cfg[‘Servers’][$i][‘SignonSession’]строка
Имя сессии которая будет использоваться для ‘signon’-аутентификации.
$cfg[‘Servers’][$i][‘SignonURL’]строка
URL куда пользователь будет перенаправлен при входе в phpMyAdmin, в случае использования метода ‘signon’-аутентификации. Путь должен быть полным, т.е. включать в себя протокол, домен, порт и путь относительно корня к странице (каталогу).
$cfg[‘Servers’][$i][‘LogoutURL’]строка
URL куда пользователь будет перенаправлен после завершения сеанса работы в phpMyAdmin (не распространяется на метод ‘config’-аутентификации. Путь должен быть полным (включать в себя протокол).
$cfg[‘ServerDefault’] число
Если перед вами стоит задача конфигурирования более одного сервера. Вы можете установить $cfg[‘ServerDefault’] для любого из них, чтобы обеспечить автосоединение с сервером при запуске phpMyAdmin, или выставить для данной переменной значение 0 чтобы выдавать список серверов без входа в систему.
Если Вы конфигурируете только один сервер, $cfg[‘ServerDefault’] ДОЛЖНА быть установлена для этого сервера.
$cfg[‘OBGzip’] строка/булево выражение
Определяет, использовать ли GZip буферизацию на выходе для повышенной скорости в http передачах. Установка true/false соответственно разрешает/запрещает буферизацию. Когда установлено в ‘auto’ (строка), phpMyAdmin пробует разрешить буферизацию на выходе и автоматически запрещает её, если ваш браузер имеет какие-либо проблемы с буферизацией. IE6 с определенным патчем, как известно, вызывает порчу данных при использовании буферизации.
$cfg[‘PersistentConnections’] булево выражение
Определяет разрешать использование постоянного соединения или нет (mysql_connect или mysql_pconnect).
$cfg[‘ForceSSL’] булево выражение
Усилено ли использование https на протяжении сеанса phpMyAdmin.
$cfg[‘ExecTimeLimit’] число [число секунд]
Задает временное ограничение (в секундах) для выполнения скрипта. Если значение выставлено в 0, то никакого ограничения по времени наложено не будет.
Эта настройка используется при импорте/экспорте дампа, но не имеет смысла, когда PHP запущен в безопасном режиме.
$cfg[‘MemoryLimit’] число [количество байтов]
Определяет количество байтов памяти, которые может использовать скрипт. Если количество равно 0, то не накладывается никаких ограничений. Данная настройка используется при импорте/экспорте дампов, но бесполезна при работе с PHP, запущенном в безопасном режиме. Вы также можете использовать другие строки в php.ini, например, ’16M’.
Эта настройка используется при импорте/экспорте дампа, но не имеет смысла, когда PHP запущен в безопасном режиме.
$cfg[‘SkipLockedTables’] булево выражение
Помечает используемые таблицы, и делает возможным просмотр баз данных с заблокированными таблицами (с 3.23.30).
$cfg[‘ShowSQL’] булево выражение
Определяет будут ли отображаться SQL-запросы, сгенерированные phpMyAdmin или нет.
$cfg[‘AllowUserDropDatabase’] булево выражение
Определяет разрешено ли обычному пользователю (не администратору) удалять собственные базы данных или нет. Если установлено значение FALSE, ссылка «Drop Database» не будет отображаться, и даже команда «DROP DATABASE mydatabase» будет отклонена. Весьма практично для ISP’S со множеством клиентов. Обратите внимание, что это всего лишь ограничение на уровне SQL-запросов, не такое жесткое, как при использовании MySQL привилегий. Это объясняется сущностью SQL-запросов, поэтому этот вариант не подменяет администрирования привилегий и должен рассматриваться как вспомогательный для предотвращения случайного удаления баз данных.
$cfg[‘Confirm’] булево выражение
Должно ли отображаться предупреждение («Are your really sure…»), при удалении данных.
$cfg[‘LoginCookieRecall’] булево выражение
Определяет, должен ли предыдущий логин быть использован в cookie-аутентификации или нет.
$cfg[LoginCookieValidity] число [количество секунд]
Определяет как долго может длиться идентификация куки.
$cfg[LoginCookieStore] число [количество секунд]
Определяет как долго хранится идентификационная кука в браузере. По умолчанию — 0, это означает, что она будет храниться на продолжение текущей сессии. Такое значение рекомендуется при работе в потенциально ненадежных средах.
$cfg[LoginCookieDeleteAll] булево выражение
Если разрешено (по умолчанию), при завершении сеанса удаляются куки для всех серверов, за исключением текущего. Если запрещено — можно обходиться без завершения сеанса при работе с несколькими серверами.
$cfg[‘UseDbSearch’] булево выражение
Определяет, разрешен ли «поиск строки внутри базы данных» или нет.
$cfg[‘IgnoreMultiSubmitErrors’] булево выражение
Определяет, продолжит ли phpMyAdmin выполнять мильтизапрос, если один из подзапросов не выполняется. По умолчанию phpMyAdmin прерывает выполнение мультизапроса.
$cfg[‘VerboseMultiSubmit’] булево выражение
Определяет, будет ли phpMyAdmin выводить результаты каждого подзапроса мультизапросного выражения, вложенного в вывод SQL как внутренний комментарий. По умолчанию TRUE.
$cfg[‘AllowArbitraryServer’] булево выражение
Если TRUE — разрешено начинать сеанс с произвольным сервером, используя cookie-авторизацию. Внимание: используйте эту настройку осторожно, т.к. тем самым Вы можете разрешить доступ к MySQL серверу, в обход брандмауэра.
$cfg[‘LeftFrameLight’] булево выражение
Определяет, использовать ли выпадающее меню и показывать только текущие таблицы в левом фрейме. Только в Non-Lightmode Вы можете показать вложенное использование папок $cfg[‘LeftFrameTableSeparator’]
$cfg[‘LeftFrameDBTree’] булево выражение
В облегченном режиме, определяет, показывать ли названия баз данных (в селекторе) в виде дерева, смотри также $cfg [‘LeftFrameDBSeparator’].
$cfg[‘LeftFrameDBSeparator’] строка
Для разделения названий баз данных в древовидной структуре будет использоваться указанная строка.
$cfg[‘LeftFrameTableSeparator’] строка
Определяет строку, которая будет определять родительские отношения. По умолчанию ‘__’. Это означает, что если Вы имеете таблицы, например, ‘first__second__third’, то они будут отображаться в виде трехуровневой иерархии: first > second > third. Если установлено False, или пустая строка, то опция недоступна. ПРИМЕЧАНИЕ: Вы не должны использовать этот сепаратор в начале или конце названия таблицы или многократно повторять его друг за другом, не вставляя других символов меду ними.
$cfg[‘LeftFrameTableLevel’] строка
Определяет, сколько подуровней должно быть показано, при разбиении таблиц вышеупомянутым сепаратором.
$cfg[‘ShowTooltip’] булево выражение
Определяет, показать ли комментарий к таблице в левом фрейме в виде всплывающего меню или нет.
$cfg[‘ShowTooltipAliasDB’] булево выражение
Если всплывающие подсказки разрешены, и установлены комментарии к базе данных, то реальное название будет заменено комментарием. Это означает, если Вы имеете таблицу, которая называется ‘user0001’ и добавите комментарий ‘MyName’ в неё, то в левом фрейме Вы будете видеть название ‘MyName’, а всплывающая подсказка будет показывать реальное имя таблицы.
$cfg[‘ShowTooltipAliasTB’] булево выражение/строка
Аналогично $cfg [‘ShowTooltipAliasDB’], за исключением того, что это работает для таблиц. Когда установлено значение ‘nested’, псевдоним таблицы используется только для разделения/вкладывания таблиц согласно директиве $cfg[‘LeftFrameTableSeparator’]. Таким образом, псевдонимом называется только папка, название самой таблицы остается реальным.
$cfg[‘LeftDisplayLogo’] булево выражение
Определяет отображать логотип phpMyAdmin в верхней части левого фрейма или нет. По умолчанию TRUE.
$cfg[‘LeftLogoLink’] строка
Введите URL для ссылки с логотипа в левом фрейме. Особенно актуально для собственных тем, которые изменяют значение данной переменной.
$cfg[‘LeftLogoLinkWindow’] строка
Определяет где открывать страницу при переходе с логотипа: в главном окне (main) или в новом отдельном (new).
$cfg[‘LeftDisplayServers’] булево выражение
Определяет, показывать ли выбранный сервер в верхней части левого фрейма или нет. По умолчанию FALSE.
$cfg[‘DisplayServersList’] булево выражение
Определяет, как показывать выбираемые сервера: в виде списка ссылок или в виде выпадающего списка. По умолчанию FALSE (выпадающий список).
$cfg[‘DisplayDatabasesList’] булево выражение
Определяет, способ отображения списка баз данных в навигационном фрейме: в виде списка ссылок, или в виде выпадающего списка. По умолчанию — FALSE (выпадающий список).
$cfg[‘ShowStats’] булево выражение
Определяет, показывать ли используемое пространство и статистику по базе данных или нет. Помните, что статистика требует, по крайней мере, MySQL 3.23.3 и что, MySQL не возвращает такую информацию для таблиц Berkeley DB.
$cfg[‘ShowServerInfo’] булево выражение
Определяет, отображать ли подробную информацию о MySQL-сервере на главной странице. Кроме этого, Вы можете скрыть больше информации, используя $cfg[‘Servers’][$i][‘verbose’].
$cfg[‘ShowPhpInfo’] булево выражение
$cfg[‘ShowChgPassword’] булево выражение
$cfg[‘ShowCreateDb’] булево выражение
Определяет, показывать ли ссылки «PHP information» (PHP информация) и «Change password» (изменить пароль) в стартовом главном фрейме или нет. Эта настройка не проверяет MySQL команды, введенные непосредственно.
Помните, что блокируя использование phpinfo() в скрипте, в php.ini необходимо указать следующее:
disable_functions = phpinfo()
Также имейте в виду, что разрешение ссылки «Change password » не имеет никакого эффекта при использовании режима «config»-аутентификации: из-за жестко закодированного значения пароля в файле конфигурации, конечным пользователям нельзя разрешить изменить их пароли.
$cfg[‘SuggestDBName’] булево выражение
Определяет, предложить ли подсказку названия базы данных в форме «Create Database» или оставить текстовое поле пустым.
$cfg[‘ShowBlob’] булево выражение
Определяет, отображаются ли поля BLOB, при просмотре таблиц или нет.
$cfg[‘NavigationBarIconic’] строка
Определяет, содержат ли кнопки навигационного меню и верхнее меню правого фрейма текст или только символы. Значение TRUE отображает иконки, FALSE отображает текст, а ‘both’ отображает и иконки, и текст.
$cfg[‘ShowAll’] булево выражение
Определяет, будет ли пользователю показана кнопка «show all (records)» (показать все записи) в режиме просмотра или нет.
$cfg[‘MaxRows’] число
Число строк, отображаемых при просмотре результатов запроса. Если результат запроса содержит большее количество строк, появятся ссылки Previous/Next
$cfg[‘Order’] строка [DESC|ASC|SMART]
Определяет будут ли поля отображаться по возрастанию (ascending (ASC)), по убыванию (descending (DESC)) или в интеллектуальном порядке (SMART) — например, поля типов TIME, DATE, DATETIME & TIMESTAMP упорядочиваются по убыванию, остальные по умолчанию — по возрастанию.
$cfg[‘ProtectBinary’] булево выражение или строка
Определяет будут ли поля BLOB или BINARY защищены от редактирования при просмотре таблиц или нет. Приемлемые значения:
$cfg[‘ShowFunctionFields’] булево выражение
Определяет будут ли изначально отображаться поля MySQL функций в режиме редактирования/вставки или нет. Начиная с версии 2.10, пользователь может переключать эту настройку через интерфейс.
$cfg[‘CharEditing’] строка
Определяет тип управляющего элемента редактирования, который будет использоваться для полей CHAR и VARCHAR полей.
Возможные варианты:
По умолчанию — старый вариант input.
$cfg[‘InsertRows’] число
Определяет максимальное число одновременно выводящихся блоков для вставки записей для страницы Insert (Вставка).
$cfg[‘ForeignKeyMaxLimit’] число
Если в списке меньшее количество внешних ключей, то выпадающий блок внешних ключей представлен, в стиле, описанном в конфигурационной переменной $cfg [‘ForeignKeyDropdownOrder’]
$cfg[‘ForeignKeyDropdownOrder’] массив
Для выпадающего поля «внешний ключ» (foreign key), существует несколько способов отображения, предлагающих значения ключа и данных. Содержимое массива должно включать один или оба предложенных ниже варианта: ‘content-id’, ‘id-content’.
$cfg[‘ZipDump’] булево выражение
$cfg[‘GZipDump’] булево выражение
$cfg[‘BZipDump’] булево выражение
Определяет разрешать использование of zip/GZip/BZip2 компрессии при создании дампа или нет.
$cfg[‘CompressOnFly’] булево выражение
Определяет разрешать компрессию GZip/BZip2 на лету (при сжатом экспорте) или нет. Это позволит отказаться от необходимости создавать малые дампы и позволит создавать дампы большого размера, которые в противном случае невозможно создавать из-за php ограничения памяти. Созданные файлы содержат больше заголовков GZip/BZip2, но абсолютной большинство программ обрабатывают это корректно.
$cfg[‘LightTabs’] булево выражение
Если установлено True, используются менее интенсивные графические элементы в верхней части главного фрейма (вкладки заменяются квадратными скобками). По умолчанию FALSE (графические вкладки)
$cfg[‘PropertiesIconic’] строка
Если установлено TRUE, вместо текста отображаются иконки (таких как ‘Browse’, ‘Select’, ‘Insert’, …) для баз данных, таблиц.
Можно выставить ‘both’ если Вы хотите чтобы отображались как иконки, так и текст.
Когда выставлено False, отображается только текст
$cfg[‘PropertiesNumColumns’] число
Сколько колонок используется для отображения таблиц в окне свойств базы данных. По умолчанию — 1 колонка. Если значение больше 1, то тип базы данных не указывается с целью экономии места.
$cfg[‘DefaultTabServer’] строка
Определяет вкладку, отображаемую открытой по умолчанию на представлении сервера. Возможные значения: «main.php» (рекомендуется при многопользовательской установке), «server_databases.php», «server_status.php», «server_variables.php», «server_privileges.php» или «server_processlist.php».
$cfg[‘DefaultTabDatabase’] строка
Определяет вкладку, отображаемую по умолчанию при просмотре базы данных. Допустимые значения: «db_structure.php», «db_sql.php» или «db_search.php».
$cfg[‘DefaultTabTable’] строка
Определяет вкладку, отображаемую по умолчанию при просмотре таблицы. Возможные варианты значений: «tbl_structure.php», «tbl_sql.php», «tbl_select.php», «tbl_change.php» или «sql.php».
$cfg[‘MySQLManualBase’] строка
Задает URL, который используется при генерировании отдельных ссылок помощи на документацию по MySQL (тип определяется в $cfg[‘MySQLManualType’]).
$cfg[‘MySQLManualType’] строка
Типы MySQL документации:
$cfg[‘DefaultLang’] строка
Определяет язык, используемый по умолчанию, если не определяется браузером или пользователем. См. скрипт select_lang.lib.php чтобы узнать возможные значения для этой переменной.
$cfg[‘Lang’] строка
Усиление: всегда использовать этот язык (должен быть определен в скрипте select_lang.lib.php).
$cfg[‘DefaultCharset’] строка
Набор символов, используемых по умолчанию для записи MySQL запросов. Он должен быть разрешен и описан в данной переменной.
$cfg[‘AllowAnywhereRecoding’].
Вы можете задать здесь любые символы из массива $cfg[‘AvailableCharsets’], чтобы пользователь в последствии мог выбрать любые из них.
$cfg[‘AllowAnywhereRecoding’] булево выражение
Разрешить кодировку, используемую для написания MySQL запросов. Вам необходима поддержка recode или iconv (скомпилированный или в виде модуля) в PHP для разрешения записи MySQL запросов и использования языкового файла (по умолчанию используется Юникод, во избежание потери некоторых символов).
Если значение TRUE — также активирует выпадающее меню в странице «Export» (Экспорт), чтобы выбрать набор символов, при экспорте файла.
$cfg[‘RecodingEngine’] строка
Здесь Вы можете задать функцию, которая будет заниматься перекодировкой. Возможные значения:
По умолчанию — auto.
$cfg[‘IconvExtraParams’] строка
Определяет некоторые параметры для iconv, которая используется в преобразовывании кодировки. Для получения дополнительной информации см. документацию. По умолчанию используется //TRANSLIT, что приводит к тому, что неверные символы транслитерируются (заменяются на символы другого языка).
$cfg[‘AvailableCharsets’] массив
Доступные кодировки для MySQL. Вы можете добавлять свои (из тех, что поддерживаются recode/iconv) или удалить те, которые не собираетесь использовать. Кодировки будут отображены в том порядке, как они записаны: таким образом, имеет смысл указывать наиболее часто используемые в самом начале.
$cfg[‘TrustedProxies’] массив
Список прокси и HTTP-заголовков, которые являются доверенными для IP Allow/Deny. Этот список по умолчанию пустой, Вам необходимо заполнить его доверенными прокси-серверами, если Вы хотите использовать правила для IP-адресов, находящихся за прокси-сервером.
Ниже приведен пример, в котором phpMyAdmin предписано доверять заголовку HTTP_X_FORWARDED_FOR (X-Forwarded-For) полученному от прокси 1.2.3.4:
$cfg[‘TrustedProxies’] =
array(‘1.2.3.4’ => ‘HTTP_X_FORWARDED_FOR’);
Директива $cfg[‘Servers’][$i][‘AllowDeny’][‘rules’] обычно использует клиентские IP-адреса.
$cfg[‘GD2Available’] строка
Определяет доступна ли GD >= 2. Если да, она может быть использована для MIME-преобразований. Возможные значения:
По умолчанию — auto.
$cfg[‘NaviWidth’] число
Ширина навигационного фрейма в пикселях. Смотрите themes/themename/layout.inc.php.
$cfg[‘NaviBackground’] строка [валидный css код для фона]
$cfg[‘MainBackground’] строка [валидный css код для фона]
Стили фона используемые для обоих фреймов. Смотрите themes/themename/layout.inc.php.
$cfg[‘NaviPointerBackground’] строка [валидный css код для фона]
$cfg[‘NaviPointerColor’] строка [валидный css цвет]
Стиль, используемый для указателей навигационного фрейма. Смотрите themes/themename/layout.inc.php.
$cfg[‘LeftPointerEnable’] булево выражение
Значение TRUE активирует навигационные указатели (когда LeftFrameLight — FALSE).
$cfg[‘Border’] число
Размер границы таблицы. Смотрите themes/themename/layout.inc.php.
$cfg[‘ThBackground’] строка [валидный css код для фона]
$cfg[‘ThColor’] строка [валидный css цвет]
Стиль, используемый для заголовков таблиц. Смотрите themes/themename/layout.inc.php.
$cfg[‘BgOne’] строка [HTML color]
Цвет (HTML) #1 для нечетных строк таблицы. Смотрите themes/themename/layout.inc.php.
$cfg[‘BgTwo’] строка [HTML color]
Цвет (HTML) #2 для четных строк таблицы. Смотрите themes/themename/layout.inc.php.
$cfg[‘BrowsePointerBackground’] строка [HTML color]
$cfg[‘BrowsePointerColor’] строка [HTML color]
$cfg[‘BrowseMarkerBackground’] строка [HTML color]
$cfg[‘BrowseMarkerColor’] строка [HTML color]
Цвета (HTML) используемые для указателей и маркеров в режиме просмотра.
Скрипт подсвечивает строки, над которыми проходит курсор, дает возможность отмечать/снимать выделение с записей с помощью щелчка мышью. Смотрите themes/themename/layout.inc.php.
$cfg[‘FontFamily’] строка
Здесь указывается валидное значение семейства шрифта (font family): например, arial, sans-serif.
См. themes/themename/layout.inc.php.
$cfg[‘FontFamilyFixed’] строка
Здесь указывается валидное значение семейства шрифта (font family): например, monospace. Переменная определяет шрифт в textarea.
См. themes/themename/layout.inc.php.
$cfg[‘BrowsePointerEnable’] булево выражение
Активировать указатель просмотра или нет.
$cfg[‘BrowseMarkerEnable’] булево выражение
Активировать маркер просмотра или нет.
$cfg[‘TextareaCols’] число
$cfg[‘TextareaRows’] число
$cfg[‘CharTextareaCols’] число
$cfg[‘CharTextareaRows’] число
Число столбцов и строк для многострочного поля текстового ввода («textarea»).
Это значение будет увеличено в (*2) для полей текстового ввода SQL запросов и в (*1.25) для полей текстового ввода SQL запросов внутри окна запросов.
Значения Char* используются для полей CHAR или VARCHAR в окне редактирования (если сконфигурировано с помощью $cfg[‘CharEditing’]).
$cfg[‘LongtextDoubleTextarea’] булево выражение
Определяет, будет ли textarea для полей типа LONGTEXT иметь двойной размер
$cfg[‘TextareaAutoSelect’] булево выражение
Определяет, будет ли выделяться содержимое текстовой области в блоке запроса целиком при клике.
$cfg[‘CtrlArrowsMoving’] булево выражение
Разрешает перемещение между полями при редактировании с помощью Ctrl+Arrows (Option+Arrows in Safari).
$cfg[‘LimitChars’] число
Максимальное кол-во символов, отображаемых в разных нечисловых полях при предварительном просмотре.
$cfg[‘ModifyDeleteAtLeft’] булево выражение
$cfg[‘ModifyDeleteAtRight’] булево выражение
Определяет место, где будут размещаться ссылки правки и удаления при отображении содержимого таблицы (вы можете задать размещение их обеих справа или слева). «Left» и «right» соответствуют размещению ссылок «top» и «bottom» соответственно при вертикальном режиме просмотра.
$cfg[‘DefaultDisplay’] строка
$cfg[‘HeaderFlipType’] строка
Здесь возможны 3 режима отображения: horizontal, horizontalflipped и vertical. Определяет, какой режим будет выбран по умолчанию. Первый режим отображает каждую запись на горизонтальной линии, второй режим поворачивает заголовки на 90 градусов, таким образом можно использовать развернутые заголовки для полей, содержащих данные небольших размеров, данный режим удобен для вывода на печать. Вертикальный режим выводит каждую запись в виде отдельного столбца.
HeaderFlipType может быть установлено в ‘css’ или ‘fake’. При использовании ‘css’ поворот заголовков при втором режиме осуществляется с помощью CSS. Если установлено ‘fake’ трансформация осуществляется с помощью PHP, но, разумеется, результат не такой изящный как CSS.
$cfg[‘DefaultPropDisplay’] строка или число
При редактировании/создании новых столбцов в таблице все поля обычно размещаются в одну линию (по умолчанию: ‘horizontal’). Если вы устанавливаете ‘vertical’ все поля располагаются вертикально друг под другом. Задавая тот или иной режим можно оптимально использовать пространство браузера и избежать полосы прокрутки.
Если Вы задаете в качестве значения число, тогда при редактировании в случае меньшего количества столбцов будет использован режим ‘vertical’, в случае большего количества — режим ‘horizontal’.
$cfg[‘ShowBrowseComments’] булево выражение
$cfg[‘ShowPropertyComments’] булево выражение
Устанавливая соответствующую переменную в значение TRUE разрешается отображение комментариев столбцов в режиме предварительного просмотра или просмотре свойств таблицы. В режиме просмотра, комментарии — отображаются в заголовке. В режиме просмотра свойств, комментарии отображаются, с помощью CSS-форматированной прерывистой линии под названием поля. Комментарий отображается в виде всплывающей подсказки при наведении курсора.
$cfg[‘UploadDir’] строка
Имя директории,будут загружены SQL файлы. Эти файлы доступны из выпадающего блока, который появляется при щелчке на имени базы данных.
Если Вы хотите задать различные директории для каждого пользователя, %u будет заменяться именем пользователя.
Пожалуйста, помните, что имена файлов должны иметь суффикс «.sql» (или «.sql.bz2» или «.sql.gz» если разрешена поддержка форматов сжатия).
Эта опция полезна, когда файл слишком велик, чтобы быть загруженным с помощью HTTP, или когда загрузка файла отображаются в PHP.
Помните, что если PHP запущен в безопасном режиме (safe mode), данная директория должна принадлежать тому же пользователю, которому принадлежит и phpMyAdmin.
Для получения дополнительной информации см. FAQ 1.16.
$cfg[‘SaveDir’] строка
Имя директории куда будут сохраняться дампы.
Если необходимо задать различные директории для каждого пользователя, %u будет заменяться именем пользователя. Обратите внимание, что директория должна быть доступна для записи для пользователей запускающих веб-сервер.
Также следует иметь ввиду, что если PHP запущен в безопасном режиме (safe mode), данная директория должна принадлежать тому же пользователю, которому принадлежит и phpMyAdmin.
$cfg[‘TempDir’] строка
Имя директории, где хранятся временные файлы.
Эта опция необходима для MS Excel экспорта, см. FAQ 6.23
$cfg[‘Export’] массив
В данном массиве задаются параметры для экспорта по умолчанию, названия пунктов соответствуют записям на странице экспорта, таким образом, трудностей с определением их значения возникнуть не должно.
$cfg[‘Import’] массив
В данном массиве задаются параметры для импорта по умолчанию, названия пунктов соответствуют записям на странице импорта, таким образом, трудностей с определением их значения возникнуть не должно.
$cfg[‘RepeatCells’] число
Повторяет заголовки каждые X ячеек, или 0 для дезактивации.
$cfg[‘QueryFrame’] булево выражение
$cfg[‘QueryFrameJS’] булево выражение
$cfg[‘QueryWindowWidth’] число
$cfg[‘QueryWindowHeight’] число
$cfg[‘QueryHistoryDB’] булево выражение
$cfg[‘QueryWindowDefTab’] строка
$cfg[‘QueryHistoryMax’] число
Все эти переменные связаны с окном запроса. Когда $cfg[‘QueryFrame’] установлено true, ссылка или иконка отображается на левой панели. Щелчок на ней открывает блок запроса, a прямой интерфейс для ввода SQL-запроса.
Когда $cfg[‘QueryFrameJS’] установлено true, щелчок на этой ссылке открывает блок запроса в новом окне, размеры которого можно задавать ($cfg[‘QueryWindowWidth’], $cfg[‘QueryWindowHeight’] — возможные значения — числа, определяющие размер в пикселях). Также, щелчок на [Edit] с результирующей страницы (в секции «Showing Rows») открывает блок запроса и помещает текущий запрос внутрь него. Если установлено false, щелчок по ссылке только открывает окно ввода SQL-запроса в главном фрейме.
Использование JavaScript окна запроса рекомендовано, если браузер разрешает использование JavaScript. Основные функции написаны таким образом, что большинство браузеров с 4-го поколения поддерживают эту опцию. В настоящее время протестирован на браузерах Internet Explorer 6 и Mozilla 1.x.
Если $cfg[‘QueryHistoryDB’] установлено TRUE, все Ваши запросы будут записываться в таблицу, которая была создана вами (см. $cfg[‘Servers’][$i][‘history’]). Если установлено FALSE, все ваши запросы будут присоединяться к форме, но только на то время, пока открыто окно запроса.
Когда используется JavaScript-основанное окно запросов, оно будет всегда обновляться при щелчке на просмотр таблиц/баз данных и всегда будет в фокусе, при щелчке на «Edit SQL» после использования запроса. Вы можете запретить обновление окна запросов, отмечая чекбокс «Do not overwrite this query from outside the window» ниже текстовой области ввода запроса. После этого Вы сможете просматривать таблицы/базы данных в фоне без потери содержимого текстовой области, таким образом, это особенно удобно, когда составляется запрос из нескольких таблиц, и прежде нужно посмотреть их. Чекбокс выставляется автоматически всякий раз, когда изменяется содержимое текстового поля ввода. Снимайте чекбокс всякий раз, когда необходимо, чтобы окно запроса обновилось даже в том случае, если были сделаны изменения.
Если $cfg[‘QueryHistoryDB’] установлено TRUE Вы можете определять объем сохраняемой истории с помощью указания значений для конфигурационной переменной $cfg[‘QueryHistoryMax’].
Окно запросов снабжено закладками, для группировки опций. Используя переменную $cfg[‘QueryWindowDefTab’] Вы можете задавать вкладки по умолчанию, которые будут использованы при открытии окна запросов. Даная переменная может принимать следующие значения: ‘sql’, ‘files’, ‘history’ или ‘full’.
$cfg[‘BrowseMIME’] булево выражение
Разрешает MIME-трансформации (MIME-transformations).
$cfg[‘MaxExactCount’] число
Для InnoDB таблиц, определяет максимальное число записей таблиц, при котором phpMyAdmin отображает количество строк в таблице с помощью SELECT COUNT. Если количество строк меньше чем это значение, то будет использоваться SELECT COUNT, если больше — значение будет только возвращено через SHOW TABLE STATUS.
$cfg[‘MaxExactCountViews’] число
Для представлений, это значение будет максимумом строк, при которых количество строк будет выведено запросом SELECT COUNT … LIMIT. По умолчанию выставляется значение 0, которое блокирует подсчет записей, т.к. при работе с таблицами очень больших размеров, получение точного числа записей может крайне негативно сказаться на производительности.
$cfg[‘WYSIWYG-PDF’] булево выражение
Использует WYSIWYG редактирование для большего удобства размещения элементов PDF страницы. Кликая на кнопке ‘toggle scratchboard’ на странице, где вы правите x/y координаты этих элементов вы можете активировать scratchboard куда помещены все ваши элементы. Кликая по элементу, Вы можете перемещать его и координаты будут изменяться автоматически. Аналогично, вводя новые координаты в область входа, элементы принимают новое положение после того, как курсор оставляет область ввода.
Для сохранения новых позиций, необходимо кликнуть по кнопке ‘OK’, что расположена ниже таблицы. Если необходимо добавить новый элемент — нужно сначала добавить его в таблицу элементов, после этого можно перемещать новый объект. Можно изменять размер и ориентацию бумаги с помощью нижерасположенного выпадающего меню — размер изменится автоматически, без изменения текущего расположения элементов.
Если даже какой-нибудь элемент выйдет за пределы указанного диапазона, можно либо увеличить размер бумаги, либо нажать кнопку ‘reset’, чтобы разместить все элементы друг под другом.
ОБРАТИТЕ ВНИМАНИЕ: чтобы воспользоваться этими средствами управления, необходимо пользоваться последними версиями браузеров IE6 или Mozilla.
$cfg[‘NaturalOrder’] булево выражение
Сортировка названий баз данных и таблиц в обычном порядке (например, t1, t2, t10). Сортировка применяется в левой панели (Light mode) и при просмотре баз данных (Database view), для списка таблиц.
$cfg[‘TitleTable’] строка
$cfg[‘TitleDatabase’] строка
$cfg[‘TitleServer’] строка
$cfg[‘TitleDefault’] строка
Данная группа переменных позволяет Вам определять строки заголовков окон. Ниже описаны выражения, которые могут быть использованы для получения специфичных значений: @HTTP_HOST@ — HTTP хост на котором запущен phpMyAdmin @SERVER@ — имя MySQL-сервера @VERBOSE@ — имя MySQL-сервера заданное в конфигурации сервера @VSERVER@ — имя MySQL-сервера если задано, в противном случае — обычное @DATABASE@ — текущая открытая база данных @TABLE@ — текущая открытая таблица @PHPMYADMIN@ — версия phpMyAdmin
$cfg[‘ShowHttpHostTitle’] булево выражение
Показывает HTTP host name в строке заголовка окна.
$cfg[‘SetHttpHostTitle’] строка
Если $cfg[‘ShowHttpHostTitle’] установлено TRUE, она показывает настоящий HTTP host name, если здесь не указано альтернативное название.
$cfg[‘ErrorIconic’] булево выражение
Использование иконок для предупреждений, ошибок и сообщений.
$cfg[‘MainPageIconic’] булево выражение
Использование иконок на главной странице в списках и вкладках меню.
$cfg[‘ReplaceHelpImg’] булево выражение
Показывает кнопку помощи вместо сообщения «Документация» («Documentation»).
$cfg[‘ThemePath’] string
Если менеджер тем активизирован, эту переменную следует использовать как путь к поддиректории, содержащей все темы.
$cfg[‘ThemeManager’] boolean
Разрешает использование тем, выбираемых пользователем. См. FAQ 2.7.
$cfg[‘ThemeDefault’] string
Тема по умолчанию (поддиректория cfg[‘ThemePath’]).
$cfg[‘ThemePerServer’] boolean
Разрешать ли разные темы для каждого сервера.
$cfg[‘DefaultQueryTable’] строка
$cfg[‘DefaultQueryDatabase’] строка
Запросы по умолчанию, что будут отображаться в блоках запросов, когда пользователь не будет их специально задавать. Используйте %d для имени базы данных, %t для названия таблицы и %f для списка названий полей, разделенных запятыми. Помните, что %t и %f применимы только к $cfg[‘DefaultQueryTable’].
$cfg[‘SQP’][‘fmtType’] строка [html|none]
Основное использование нового SQL-парсера для вывода SQL-запросов. По умолчанию используется HTML, для форматирования запроса, но возможно запрещение подобного форматирования, установив эту переменную в ‘none’.
$cfg[‘SQP’][‘fmtInd’] число с плавающей точкой
$cfg[‘SQP’][‘fmtIndUnit’] строка [em|px|pt|ex]
Для более эстетичного вида при выводе SQL-запроса, в некоторых случаях часть запроса внутри скобки имеет отступ. С помощью изменения $cfg[‘SQP’][‘fmtInd’] Вы можете изменять величину этого отступа.
С предыдущей связана конфигурационная переменная $cfg[‘SQP’][‘fmtIndUnit’] которая определяет единицы, в которых задается величина отступа. Единицы определяются с помощью таблиц стилей.
$cfg[‘SQP’][‘fmtColor’] массив из строк кортежей (tuples)
Этот массив используется для определения цветов для каждого типа элементов выводимых SQL-запросов. Формат «кортежей» следующий: class => [HTML colour code | empty string]
Если Вы зададите, пустую строку для цвета класса, он будет проигнорирован при создании таблицы стилей. Вы не можете менять названия классов, только цвета.
Ключи — имена классов:
$cfg[‘SQLValidator’][‘use’] булево выражение
phpMyAdmin теперь поддерживает использование сервиса Mimer SQL Validator, который в оригинале опубликован на Slashdot.
Для получения помощи при настройке системы для использования этого сервиса, см. FAQ 6.14.
$cfg[‘SQLValidator’][‘username’] строка
$cfg[‘SQLValidator’][‘password’] строка
Сервис SOAP позволяет пользователю регистрироваться без логина и пароля, такой подход используется по умолчанию. Вместо этого, если Вы имеете аккаунт, вы можете указать свой логин и пароль здесь, и он будет использоваться вместо умолчальных пустых логина и пароля.
$cfg[‘DBG’][‘enable’] булево выражение
ДЛЯ РАЗРАБОТЧИКОВ!
Разрешает расширение DBG для отладки phpMyAdmin. Необходим для анализа кода. Для получения помощи при настройке системы для его использования, см. раздел FAQ «Информация для разработчиков».
$cfg[‘DBG’][‘profile’][‘enable’] булево выражение
ДЛЯ РАЗРАБОТЧИКОВ!
Разрешить поддержку профилирования для phpMyAdmin. Эта опция добавляет блок данных в конец каждой страницы, отображаемой в главном окне со статистикой профилирования для этой страницы.
Вполне вероятно, что придется увеличить максимальное время выполнения (maximum execution time) для успешного профилирования. Профилирование было удалено из кода версии 2.9.0 из-за проблем лицензирования.
$cfg[‘DBG’][‘profile’][‘threshold’] число с плавающей точкой (единицы в миллисекундах)
ДЛЯ РАЗРАБОТЧИКОВ!
Когда данные профилирования отображаются, эта переменная определяет границу отображения данных профилирования, основанную на среднем времени выполнения. Если время выше порога данные отображаются, если нет — не отображаются.
Значение задается в миллисекундах. В большинстве случаев нет необходимости специально редактировать данную переменную.
$cfg[‘ColumnTypes’] массив
Все возможные типы MySQL-столбцов. В большинстве случаев нет необходимости специально редактировать данную переменную.
$cfg[‘AttributeTypes’] массив
Возможные атрибуты для полей. В большинстве случаев нет необходимости в её редактировании.
$cfg[‘Functions’] массив
Список поддерживаемых функций MySQL. В большинстве случаев нет необходимости специально редактировать данную переменную.
$cfg[‘RestrictColumnTypes’] массив
Соответствие типов столбцов meta-типам, используемым для предпочтительного отображения функций. В большинстве случаев нет необходимости специально редактировать данную переменную.
$cfg[‘RestrictFunctions’] массив
Предпочтительные функции для столбцов мета-типов определяются в $cfg[‘RestrictColumnTypes’]. В большинстве случаев нет необходимости специально редактировать данную переменную.
$cfg[‘DefaultFunctions’] массив
Функции, выбираемые по умолчанию при вставке/редактировании строк, функции определяются для мета-типов для переменной $cfg[‘RestrictColumnTypes’] и для first_timestamp, которая используется для столбца first_timestamp в таблице.
$cfg[‘NumOperators’] массив
Операторы доступные для операций поиска в числовых (numeric) и бинарных (date) полях.
$cfg[‘TextOperators’] массив
Операторы доступные для операций поиска в символьных (character) полях. Помните, что используется LIKE вместо LIKE %…%, чтобы избежать проблем в работе с таблицами очень больших размеров.
$cfg[‘EnumOperators’] массив
Операторы доступные для операций поиска в полях типа enum.
$cfg[‘NullOperators’] массив
Дополнительные операторы доступные для операций поиска, когда поля могут принимать значения null.
.. index:: config.inc.php
Configuration
All configurable data is placed in :file:`config.inc.php` in phpMyAdmin’s
toplevel directory. If this file does not exist, please refer to the
:ref:`setup` section to create one. This file only needs to contain the
parameters you want to change from their corresponding default value.
.. seealso:: :ref:`config-examples` for examples of configurations
If a directive is missing from your file, you can just add another line with
the file. This file is for over-writing the defaults; if you wish to use the
default value there’s no need to add a line here.
The parameters which relate to design (like colors) are placed in
:file:`themes/themename/scss/_variables.scss`. You might also want to create
:file:`config.footer.inc.php` and :file:`config.header.inc.php` files to add
your site specific code to be included on start and end of each page.
Note
Some distributions (eg. Debian or Ubuntu) store :file:`config.inc.php` in
/etc/phpmyadmin
instead of within phpMyAdmin sources.
Basic settings
.. config:option:: $cfg['PmaAbsoluteUri'] :type: string :default: ``''`` .. versionchanged:: 4.6.5 This setting was not available in phpMyAdmin 4.6.0 - 4.6.4. Sets here the complete :term:`URL` (with full path) to your phpMyAdmin installation's directory. E.g. ``https://www.example.net/path_to_your_phpMyAdmin_directory/``. Note also that the :term:`URL` on most of web servers are case sensitive (even on Windows). Don’t forget the trailing slash at the end. Starting with version 2.3.0, it is advisable to try leaving this blank. In most cases phpMyAdmin automatically detects the proper setting. Users of port forwarding or complex reverse proxy setup might need to set this. A good test is to browse a table, edit a row and save it. There should be an error message if phpMyAdmin is having trouble auto–detecting the correct value. If you get an error that this must be set or if the autodetect code fails to detect your path, please post a bug report on our bug tracker so we can improve the code. .. seealso:: :ref:`faq1_40`, :ref:`faq2_5`, :ref:`faq4_7`, :ref:`faq5_16`
.. config:option:: $cfg['PmaNoRelation_DisableWarning'] :type: boolean :default: false Starting with version 2.3.0 phpMyAdmin offers a lot of features to work with master / foreign – tables (see :config:option:`$cfg['Servers'][$i]['pmadb']`). If you tried to set this up and it does not work for you, have a look on the :guilabel:`Structure` page of one database where you would like to use it. You will find a link that will analyze why those features have been disabled. If you do not want to use those features set this variable to ``true`` to stop this message from appearing.
.. config:option:: $cfg['AuthLog'] :type: string :default: ``'auto'`` .. versionadded:: 4.8.0 This is supported since phpMyAdmin 4.8.0. Configure authentication logging destination. Failed (or all, depending on :config:option:`$cfg['AuthLogSuccess']`) authentication attempts will be logged according to this directive: ``auto`` Let phpMyAdmin automatically choose between ``syslog`` and ``php``. ``syslog`` Log using syslog, using AUTH facility, on most systems this ends up in :file:`/var/log/auth.log`. ``php`` Log into PHP error log. ``sapi`` Log into PHP SAPI logging. ``/path/to/file`` Any other value is treated as a filename and log entries are written there. .. note:: When logging to a file, make sure its permissions are correctly set for a web server user, the setup should closely match instructions described in :config:option:`$cfg['TempDir']`:
.. config:option:: $cfg['AuthLogSuccess'] :type: boolean :default: false .. versionadded:: 4.8.0 This is supported since phpMyAdmin 4.8.0. Whether to log successful authentication attempts into :config:option:`$cfg['AuthLog']`.
.. config:option:: $cfg['SuhosinDisableWarning'] :type: boolean :default: false A warning is displayed on the main page if Suhosin is detected. You can set this parameter to ``true`` to stop this message from appearing.
.. config:option:: $cfg['LoginCookieValidityDisableWarning'] :type: boolean :default: false A warning is displayed on the main page if the PHP parameter session.gc_maxlifetime is lower than cookie validity configured in phpMyAdmin. You can set this parameter to ``true`` to stop this message from appearing.
.. config:option:: $cfg['ServerLibraryDifference_DisableWarning'] :type: boolean :default: false .. deprecated:: 4.7.0 This setting was removed as the warning has been removed as well. A warning is displayed on the main page if there is a difference between the MySQL library and server version. You can set this parameter to ``true`` to stop this message from appearing.
.. config:option:: $cfg['ReservedWordDisableWarning'] :type: boolean :default: false This warning is displayed on the Structure page of a table if one or more column names match with words which are MySQL reserved. If you want to turn off this warning, you can set it to ``true`` and warning will no longer be displayed.
.. config:option:: $cfg['TranslationWarningThreshold'] :type: integer :default: 80 Show warning about incomplete translations on certain threshold.
.. config:option:: $cfg['SendErrorReports'] :type: string :default: ``'ask'`` Valid values are: * ``ask`` * ``always`` * ``never`` Sets the default behavior for JavaScript error reporting. Whenever an error is detected in the JavaScript execution, an error report may be sent to the phpMyAdmin team if the user agrees. The default setting of ``'ask'`` will ask the user everytime there is a new error report. However you can set this parameter to ``'always'`` to send error reports without asking for confirmation or you can set it to ``'never'`` to never send error reports. This directive is available both in the configuration file and in users preferences. If the person in charge of a multi-user installation prefers to disable this feature for all users, a value of ``'never'`` should be set, and the :config:option:`$cfg['UserprefsDisallow']` directive should contain ``'SendErrorReports'`` in one of its array values.
.. config:option:: $cfg['ConsoleEnterExecutes'] :type: boolean :default: false Setting this to ``true`` allows the user to execute queries by pressing Enter instead of Ctrl+Enter. A new line can be inserted by pressing Shift+Enter. The behaviour of the console can be temporarily changed using console's settings interface.
.. config:option:: $cfg['AllowThirdPartyFraming'] :type: boolean|string :default: false Setting this to ``true`` allows phpMyAdmin to be included inside a frame, and is a potential security hole allowing cross-frame scripting attacks or clickjacking. Setting this to 'sameorigin' prevents phpMyAdmin to be included from another document in a frame, unless that document belongs to the same domain.
Server connection settings
.. config:option:: $cfg['Servers'] :type: array :default: one server array with settings listed below Since version 1.4.2, phpMyAdmin supports the administration of multiple MySQL servers. Therefore, a :config:option:`$cfg['Servers']`-array has been added which contains the login information for the different servers. The first :config:option:`$cfg['Servers'][$i]['host']` contains the hostname of the first server, the second :config:option:`$cfg['Servers'][$i]['host']` the hostname of the second server, etc. You can put as many sections for server definition as you need in :file:`config.inc.php`, copy that block or needed parts (you don't have to define all settings, just those you need to change). .. note:: The :config:option:`$cfg['Servers']` array starts with $cfg['Servers'][1]. Do not use $cfg['Servers'][0]. If you want more than one server, just copy following section (including $i increment) several times. There is no need to define full server array, just define values you need to change.
.. config:option:: $cfg['Servers'][$i]['host'] :type: string :default: ``'localhost'`` The hostname or :term:`IP` address of your $i-th MySQL-server. E.g. ``localhost``. Possible values are: * hostname, e.g., ``'localhost'`` or ``'mydb.example.org'`` * IP address, e.g., ``'127.0.0.1'`` or ``'192.168.10.1'`` * IPv6 address, e.g. ``2001:cdba:0000:0000:0000:0000:3257:9652`` * dot - ``'.'``, i.e., use named pipes on windows systems * empty - ``''``, disables this server .. note:: The hostname ``localhost`` is handled specially by MySQL and it uses the socket based connection protocol. To use TCP/IP networking, use an IP address or hostname such as ``127.0.0.1`` or ``db.example.com``. You can configure the path to the socket with :config:option:`$cfg['Servers'][$i]['socket']`. .. seealso:: :config:option:`$cfg['Servers'][$i]['port']`, <https://dev.mysql.com/doc/refman/8.0/en/connecting.html>
.. config:option:: $cfg['Servers'][$i]['port'] :type: string :default: ``''`` The port-number of your $i-th MySQL-server. Default is 3306 (leave blank). .. note:: If you use ``localhost`` as the hostname, MySQL ignores this port number and connects with the socket, so if you want to connect to a port different from the default port, use ``127.0.0.1`` or the real hostname in :config:option:`$cfg['Servers'][$i]['host']`. .. seealso:: :config:option:`$cfg['Servers'][$i]['host']`, <https://dev.mysql.com/doc/refman/8.0/en/connecting.html>
.. config:option:: $cfg['Servers'][$i]['socket'] :type: string :default: ``''`` The path to the socket to use. Leave blank for default. To determine the correct socket, check your MySQL configuration or, using the :command:`mysql` command–line client, issue the ``status`` command. Among the resulting information displayed will be the socket used. .. note:: This takes effect only if :config:option:`$cfg['Servers'][$i]['host']` is set to ``localhost``. .. seealso:: :config:option:`$cfg['Servers'][$i]['host']`, <https://dev.mysql.com/doc/refman/8.0/en/connecting.html>
.. config:option:: $cfg['Servers'][$i]['ssl'] :type: boolean :default: false Whether to enable SSL for the connection between phpMyAdmin and the MySQL server to secure the connection. When using the ``'mysql'`` extension, none of the remaining ``'ssl...'`` configuration options apply. We strongly recommend the ``'mysqli'`` extension when using this option. .. seealso:: :ref:`ssl`, :ref:`example-google-ssl`, :ref:`example-aws-ssl`, :config:option:`$cfg['Servers'][$i]['ssl_key']`, :config:option:`$cfg['Servers'][$i]['ssl_cert']`, :config:option:`$cfg['Servers'][$i]['ssl_ca']`, :config:option:`$cfg['Servers'][$i]['ssl_ca_path']`, :config:option:`$cfg['Servers'][$i]['ssl_ciphers']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`
.. config:option:: $cfg['Servers'][$i]['ssl_key'] :type: string :default: NULL Path to the client key file when using SSL for connecting to the MySQL server. This is used to authenticate the client to the server. For example: .. code-block:: php $cfg['Servers'][$i]['ssl_key'] = '/etc/mysql/server-key.pem'; .. seealso:: :ref:`ssl`, :ref:`example-google-ssl`, :ref:`example-aws-ssl`, :config:option:`$cfg['Servers'][$i]['ssl']`, :config:option:`$cfg['Servers'][$i]['ssl_cert']`, :config:option:`$cfg['Servers'][$i]['ssl_ca']`, :config:option:`$cfg['Servers'][$i]['ssl_ca_path']`, :config:option:`$cfg['Servers'][$i]['ssl_ciphers']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`
.. config:option:: $cfg['Servers'][$i]['ssl_cert'] :type: string :default: NULL Path to the client certificate file when using SSL for connecting to the MySQL server. This is used to authenticate the client to the server. .. seealso:: :ref:`ssl`, :ref:`example-google-ssl`, :ref:`example-aws-ssl`, :config:option:`$cfg['Servers'][$i]['ssl']`, :config:option:`$cfg['Servers'][$i]['ssl_key']`, :config:option:`$cfg['Servers'][$i]['ssl_ca']`, :config:option:`$cfg['Servers'][$i]['ssl_ca_path']`, :config:option:`$cfg['Servers'][$i]['ssl_ciphers']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`
.. config:option:: $cfg['Servers'][$i]['ssl_ca'] :type: string :default: NULL Path to the CA file when using SSL for connecting to the MySQL server. .. seealso:: :ref:`ssl`, :ref:`example-google-ssl`, :ref:`example-aws-ssl`, :config:option:`$cfg['Servers'][$i]['ssl']`, :config:option:`$cfg['Servers'][$i]['ssl_key']`, :config:option:`$cfg['Servers'][$i]['ssl_cert']`, :config:option:`$cfg['Servers'][$i]['ssl_ca_path']`, :config:option:`$cfg['Servers'][$i]['ssl_ciphers']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`
.. config:option:: $cfg['Servers'][$i]['ssl_ca_path'] :type: string :default: NULL Directory containing trusted SSL CA certificates in PEM format. .. seealso:: :ref:`ssl`, :ref:`example-google-ssl`, :ref:`example-aws-ssl`, :config:option:`$cfg['Servers'][$i]['ssl']`, :config:option:`$cfg['Servers'][$i]['ssl_key']`, :config:option:`$cfg['Servers'][$i]['ssl_cert']`, :config:option:`$cfg['Servers'][$i]['ssl_ca']`, :config:option:`$cfg['Servers'][$i]['ssl_ciphers']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`
.. config:option:: $cfg['Servers'][$i]['ssl_ciphers'] :type: string :default: NULL List of allowable ciphers for SSL connections to the MySQL server. .. seealso:: :ref:`ssl`, :ref:`example-google-ssl`, :ref:`example-aws-ssl`, :config:option:`$cfg['Servers'][$i]['ssl']`, :config:option:`$cfg['Servers'][$i]['ssl_key']`, :config:option:`$cfg['Servers'][$i]['ssl_cert']`, :config:option:`$cfg['Servers'][$i]['ssl_ca']`, :config:option:`$cfg['Servers'][$i]['ssl_ca_path']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`
.. config:option:: $cfg['Servers'][$i]['ssl_verify'] :type: boolean :default: true .. versionadded:: 4.6.0 This is supported since phpMyAdmin 4.6.0. If your PHP install uses the MySQL Native Driver (mysqlnd), your MySQL server is 5.6 or later, and your SSL certificate is self-signed, there is a chance your SSL connection will fail due to validation. Setting this to ``false`` will disable the validation check. Since PHP 5.6.0 it also verifies whether server name matches CN of its certificate. There is currently no way to disable just this check without disabling complete SSL verification. .. warning:: Disabling the certificate verification defeats purpose of using SSL. This will make the connection vulnerable to man in the middle attacks. .. note:: This flag only works with PHP 5.6.16 or later. .. seealso:: :ref:`ssl`, :ref:`example-google-ssl`, :ref:`example-aws-ssl`, :config:option:`$cfg['Servers'][$i]['ssl']`, :config:option:`$cfg['Servers'][$i]['ssl_key']`, :config:option:`$cfg['Servers'][$i]['ssl_cert']`, :config:option:`$cfg['Servers'][$i]['ssl_ca']`, :config:option:`$cfg['Servers'][$i]['ssl_ca_path']`, :config:option:`$cfg['Servers'][$i]['ssl_ciphers']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`
.. config:option:: $cfg['Servers'][$i]['connect_type'] :type: string :default: ``'tcp'`` .. deprecated:: 4.7.0 This setting is no longer used as of 4.7.0, since MySQL decides the connection type based on host, so it could lead to unexpected results. Please set :config:option:`$cfg['Servers'][$i]['host']` accordingly instead. What type connection to use with the MySQL server. Your options are ``'socket'`` and ``'tcp'``. It defaults to tcp as that is nearly guaranteed to be available on all MySQL servers, while sockets are not supported on some platforms. To use the socket mode, your MySQL server must be on the same machine as the Web server.
.. config:option:: $cfg['Servers'][$i]['compress'] :type: boolean :default: false Whether to use a compressed protocol for the MySQL server connection or not (experimental).
.. config:option:: $cfg['Servers'][$i]['controlhost'] :type: string :default: ``''`` Permits to use an alternate host to hold the configuration storage data. .. seealso:: :config:option:`$cfg['Servers'][$i]['control_*']`
.. config:option:: $cfg['Servers'][$i]['controlport'] :type: string :default: ``''`` Permits to use an alternate port to connect to the host that holds the configuration storage. .. seealso:: :config:option:`$cfg['Servers'][$i]['control_*']`
.. config:option:: $cfg['Servers'][$i]['controluser'] :type: string :default: ``''``
.. config:option:: $cfg['Servers'][$i]['controlpass'] :type: string :default: ``''`` This special account is used to access :ref:`linked-tables`. You don't need it in single user case, but if phpMyAdmin is shared it is recommended to give access to :ref:`linked-tables` only to this user and configure phpMyAdmin to use it. All users will then be able to use the features without need to have direct access to :ref:`linked-tables`. .. versionchanged:: 2.2.5 those were called ``stduser`` and ``stdpass`` .. seealso:: :ref:`setup`, :ref:`authentication_modes`, :ref:`linked-tables`, :config:option:`$cfg['Servers'][$i]['pmadb']`, :config:option:`$cfg['Servers'][$i]['controlhost']`, :config:option:`$cfg['Servers'][$i]['controlport']`, :config:option:`$cfg['Servers'][$i]['control_*']`
.. config:option:: $cfg['Servers'][$i]['control_*'] :type: mixed .. versionadded:: 4.7.0 You can change any MySQL connection setting for control link (used to access :ref:`linked-tables`) using configuration prefixed with ``control_``. This can be used to change any aspect of the control connection, which by default uses same parameters as the user one. For example you can configure SSL for the control connection: .. code-block:: php // Enable SSL $cfg['Servers'][$i]['control_ssl'] = true; // Client secret key $cfg['Servers'][$i]['control_ssl_key'] = '../client-key.pem'; // Client certificate $cfg['Servers'][$i]['control_ssl_cert'] = '../client-cert.pem'; // Server certification authority $cfg['Servers'][$i]['control_ssl_ca'] = '../server-ca.pem'; .. seealso:: :config:option:`$cfg['Servers'][$i]['ssl']`, :config:option:`$cfg['Servers'][$i]['ssl_key']`, :config:option:`$cfg['Servers'][$i]['ssl_cert']`, :config:option:`$cfg['Servers'][$i]['ssl_ca']`, :config:option:`$cfg['Servers'][$i]['ssl_ca_path']`, :config:option:`$cfg['Servers'][$i]['ssl_ciphers']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`, :config:option:`$cfg['Servers'][$i]['socket']`, :config:option:`$cfg['Servers'][$i]['compress']`, :config:option:`$cfg['Servers'][$i]['hide_connection_errors']`
.. config:option:: $cfg['Servers'][$i]['auth_type'] :type: string :default: ``'cookie'`` Whether config or cookie or :term:`HTTP` or signon authentication should be used for this server. * 'config' authentication (``$auth_type = 'config'``) is the plain old way: username and password are stored in :file:`config.inc.php`. * 'cookie' authentication mode (``$auth_type = 'cookie'``) allows you to log in as any valid MySQL user with the help of cookies. * 'http' authentication allows you to log in as any valid MySQL user via HTTP-Auth. * 'signon' authentication mode (``$auth_type = 'signon'``) allows you to log in from prepared PHP session data or using supplied PHP script. .. seealso:: :ref:`authentication_modes`
.. config:option:: $cfg['Servers'][$i]['auth_http_realm'] :type: string :default: ``''`` When using auth_type = ``http``, this field allows to define a custom :term:`HTTP` Basic Auth Realm which will be displayed to the user. If not explicitly specified in your configuration, a string combined of "phpMyAdmin " and either :config:option:`$cfg['Servers'][$i]['verbose']` or :config:option:`$cfg['Servers'][$i]['host']` will be used.
.. config:option:: $cfg['Servers'][$i]['auth_swekey_config'] :type: string :default: ``''`` .. versionadded:: 3.0.0.0 This setting was named `$cfg['Servers'][$i]['auth_feebee_config']` and was renamed before the `3.0.0.0` release. .. deprecated:: 4.6.4 This setting was removed because their servers are no longer working and it was not working correctly. .. deprecated:: 4.0.10.17 This setting was removed in a maintenance release because their servers are no longer working and it was not working correctly. The name of the file containing swekey ids and login names for hardware authentication. Leave empty to deactivate this feature.
.. config:option:: $cfg['Servers'][$i]['user'] :type: string :default: ``'root'``
.. config:option:: $cfg['Servers'][$i]['password'] :type: string :default: ``''`` When using :config:option:`$cfg['Servers'][$i]['auth_type']` set to 'config', this is the user/password-pair which phpMyAdmin will use to connect to the MySQL server. This user/password pair is not needed when :term:`HTTP` or cookie authentication is used and should be empty.
.. config:option:: $cfg['Servers'][$i]['nopassword'] :type: boolean :default: false .. deprecated:: 4.7.0 This setting was removed as it can produce unexpected results. Allow attempt to log in without password when a login with password fails. This can be used together with http authentication, when authentication is done some other way and phpMyAdmin gets user name from auth and uses empty password for connecting to MySQL. Password login is still tried first, but as fallback, no password method is tried.
.. config:option:: $cfg['Servers'][$i]['only_db'] :type: string or array :default: ``''`` If set to a (an array of) database name(s), only this (these) database(s) will be shown to the user. Since phpMyAdmin 2.2.1, this/these database(s) name(s) may contain MySQL wildcards characters ("_" and "%"): if you want to use literal instances of these characters, escape them (I.E. use ``'my_db'`` and not ``'my_db'``). This setting is an efficient way to lower the server load since the latter does not need to send MySQL requests to build the available database list. But **it does not replace the privileges rules of the MySQL database server**. If set, it just means only these databases will be displayed but **not that all other databases can't be used.** An example of using more that one database: .. code-block:: php $cfg['Servers'][$i]['only_db'] = ['db1', 'db2']; .. versionchanged:: 4.0.0 Previous versions permitted to specify the display order of the database names via this directive.
.. config:option:: $cfg['Servers'][$i]['hide_db'] :type: string :default: ``''`` Regular expression for hiding some databases from unprivileged users. This only hides them from listing, but a user is still able to access them (using, for example, the SQL query area). To limit access, use the MySQL privilege system. For example, to hide all databases starting with the letter "a", use .. code-block:: php $cfg['Servers'][$i]['hide_db'] = '^a'; and to hide both "db1" and "db2" use .. code-block:: php $cfg['Servers'][$i]['hide_db'] = '^(db1|db2)$'; More information on regular expressions can be found in the `PCRE pattern syntax <https://www.php.net/manual/en/reference.pcre.pattern.syntax.php>`_ portion of the PHP reference manual.
.. config:option:: $cfg['Servers'][$i]['verbose'] :type: string :default: ``''`` Only useful when using phpMyAdmin with multiple server entries. If set, this string will be displayed instead of the hostname in the pull-down menu on the main page. This can be useful if you want to show only certain databases on your system, for example. For HTTP auth, all non-US-ASCII characters will be stripped.
.. config:option:: $cfg['Servers'][$i]['extension'] :type: string :default: ``'mysqli'`` .. deprecated:: 4.2.0 This setting was removed. The ``mysql`` extension will only be used when the ``mysqli`` extension is not available. As of 5.0.0, only the ``mysqli`` extension can be used. The PHP MySQL extension to use (``mysql`` or ``mysqli``). It is recommended to use ``mysqli`` in all installations.
.. config:option:: $cfg['Servers'][$i]['pmadb'] :type: string :default: ``''`` The name of the database containing the phpMyAdmin configuration storage. See the :ref:`linked-tables` section in this document to see the benefits of this feature, and for a quick way of creating this database and the needed tables. If you are the only user of this phpMyAdmin installation, you can use your current database to store those special tables; in this case, just put your current database name in :config:option:`$cfg['Servers'][$i]['pmadb']`. For a multi-user installation, set this parameter to the name of your central database containing the phpMyAdmin configuration storage.
.. config:option:: $cfg['Servers'][$i]['bookmarktable'] :type: string or false :default: ``''`` .. versionadded:: 2.2.0 Since release 2.2.0 phpMyAdmin allows users to bookmark queries. This can be useful for queries you often run. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * enter the table name in :config:option:`$cfg['Servers'][$i]['bookmarktable']` This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['relation'] :type: string or false :default: ``''`` .. versionadded:: 2.2.4 Since release 2.2.4 you can describe, in a special 'relation' table, which column is a key in another table (a foreign key). phpMyAdmin currently uses this to: * make clickable, when you browse the master table, the data values that point to the foreign table; * display in an optional tool-tip the "display column" when browsing the master table, if you move the mouse to a column containing a foreign key (use also the 'table_info' table); (see :ref:`faqdisplay`) * in edit/insert mode, display a drop-down list of possible foreign keys (key value and "display column" are shown) (see :ref:`faq6_21`) * display links on the table properties page, to check referential integrity (display missing foreign keys) for each described key; * in query-by-example, create automatic joins (see :ref:`faq6_6`) * enable you to get a :term:`PDF` schema of your database (also uses the table_coords table). The keys can be numeric or character. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the relation table name in :config:option:`$cfg['Servers'][$i]['relation']` * now as normal user open phpMyAdmin and for each one of your tables where you want to use this feature, click :guilabel:`Structure/Relation view/` and choose foreign columns. This feature can be disabled by setting the configuration to ``false``. .. note:: In the current version, ``master_db`` must be the same as ``foreign_db``. Those columns have been put in future development of the cross-db relations.
.. config:option:: $cfg['Servers'][$i]['table_info'] :type: string or false :default: ``''`` .. versionadded:: 2.3.0 Since release 2.3.0 you can describe, in a special 'table_info' table, which column is to be displayed as a tool-tip when moving the cursor over the corresponding key. This configuration variable will hold the name of this special table. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['table_info']` (e.g. ``pma__table_info``) * then for each table where you want to use this feature, click "Structure/Relation view/Choose column to display" to choose the column. This feature can be disabled by setting the configuration to ``false``. .. seealso:: :ref:`faqdisplay`
.. config:option:: $cfg['Servers'][$i]['table_coords'] :type: string or false :default: ``''`` The designer feature can save your page layout; by pressing the "Save page" or "Save page as" button in the expanding designer menu, you can customize the layout and have it loaded the next time you use the designer. That layout is stored in this table. Furthermore, this table is also required for using the PDF relation export feature, see :config:option:`$cfg['Servers'][$i]['pdf_pages']` for additional details.
.. config:option:: $cfg['Servers'][$i]['pdf_pages'] :type: string or false :default: ``''`` .. versionadded:: 2.3.0 Since release 2.3.0 you can have phpMyAdmin create :term:`PDF` pages showing the relations between your tables. Further, the designer interface permits visually managing the relations. To do this it needs two tables "pdf_pages" (storing information about the available :term:`PDF` pages) and "table_coords" (storing coordinates where each table will be placed on a :term:`PDF` schema output). You must be using the "relation" feature. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the correct table names in :config:option:`$cfg['Servers'][$i]['table_coords']` and :config:option:`$cfg['Servers'][$i]['pdf_pages']` This feature can be disabled by setting either of the configurations to ``false``. .. seealso:: :ref:`faqpdf`.
.. config:option:: $cfg['Servers'][$i]['designer_coords'] :type: string :default: ``''`` .. versionadded:: 2.10.0 Since release 2.10.0 a Designer interface is available; it permits to visually manage the relations. .. deprecated:: 4.3.0 This setting was removed and the Designer table positioning data is now stored into :config:option:`$cfg['Servers'][$i]['table_coords']`. .. note:: You can now delete the table `pma__designer_coords` from your phpMyAdmin configuration storage database and remove :config:option:`$cfg['Servers'][$i]['designer_coords']` from your configuration file.
.. config:option:: $cfg['Servers'][$i]['column_info'] :type: string or false :default: ``''`` .. versionadded:: 2.3.0 This part requires a content update! Since release 2.3.0 you can store comments to describe each column for each table. These will then be shown on the "printview". Starting with release 2.5.0, comments are consequently used on the table property pages and table browse view, showing up as tool-tips above the column name (properties page) or embedded within the header of table in browse view. They can also be shown in a table dump. Please see the relevant configuration directives later on. Also new in release 2.5.0 is a MIME- transformation system which is also based on the following table structure. See :ref:`transformations` for further information. To use the MIME- transformation system, your column_info table has to have the three new columns 'mimetype', 'transformation', 'transformation_options'. Starting with release 4.3.0, a new input-oriented transformation system has been introduced. Also, backward compatibility code used in the old transformations system was removed. As a result, an update to column_info table is necessary for previous transformations and the new input-oriented transformation system to work. phpMyAdmin will upgrade it automatically for you by analyzing your current column_info table structure. However, if something goes wrong with the auto-upgrade then you can use the SQL script found in ``./sql/upgrade_column_info_4_3_0+.sql`` to upgrade it manually. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['column_info']` (e.g. ``pma__column_info``) * to update your PRE-2.5.0 Column_comments table use this: and remember that the Variable in :file:`config.inc.php` has been renamed from :samp:`$cfg['Servers'][$i]['column_comments']` to :config:option:`$cfg['Servers'][$i]['column_info']` .. code-block:: mysql ALTER TABLE `pma__column_comments` ADD `mimetype` VARCHAR( 255 ) NOT NULL, ADD `transformation` VARCHAR( 255 ) NOT NULL, ADD `transformation_options` VARCHAR( 255 ) NOT NULL; * to update your PRE-4.3.0 Column_info table manually use this ``./sql/upgrade_column_info_4_3_0+.sql`` SQL script. This feature can be disabled by setting the configuration to ``false``. .. note:: For auto-upgrade functionality to work, your :config:option:`$cfg['Servers'][$i]['controluser']` must have ALTER privilege on ``phpmyadmin`` database. See the `MySQL documentation for GRANT <https://dev.mysql.com/doc/refman/8.0/en/grant.html>`_ on how to ``GRANT`` privileges to a user.
.. config:option:: $cfg['Servers'][$i]['history'] :type: string or false :default: ``''`` .. versionadded:: 2.5.0 Since release 2.5.0 you can store your :term:`SQL` history, which means all queries you entered manually into the phpMyAdmin interface. If you don't want to use a table-based history, you can use the JavaScript-based history. Using that, all your history items are deleted when closing the window. Using :config:option:`$cfg['QueryHistoryMax']` you can specify an amount of history items you want to have on hold. On every login, this list gets cut to the maximum amount. The query history is only available if JavaScript is enabled in your browser. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['history']` (e.g. ``pma__history``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['recent'] :type: string or false :default: ``''`` .. versionadded:: 3.5.0 Since release 3.5.0 you can show recently used tables in the navigation panel. It helps you to jump across table directly, without the need to select the database, and then select the table. Using :config:option:`$cfg['NumRecentTables']` you can configure the maximum number of recent tables shown. When you select a table from the list, it will jump to the page specified in :config:option:`$cfg['NavigationTreeDefaultTabTable']`. Without configuring the storage, you can still access the recently used tables, but it will disappear after you logout. To allow the usage of this functionality persistently: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['recent']` (e.g. ``pma__recent``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['favorite'] :type: string or false :default: ``''`` .. versionadded:: 4.2.0 Since release 4.2.0 you can show a list of selected tables in the navigation panel. It helps you to jump to the table directly, without the need to select the database, and then select the table. When you select a table from the list, it will jump to the page specified in :config:option:`$cfg['NavigationTreeDefaultTabTable']`. You can add tables to this list or remove tables from it in database structure page by clicking on the star icons next to table names. Using :config:option:`$cfg['NumFavoriteTables']` you can configure the maximum number of favorite tables shown. Without configuring the storage, you can still access the favorite tables, but it will disappear after you logout. To allow the usage of this functionality persistently: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['favorite']` (e.g. ``pma__favorite``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['table_uiprefs'] :type: string or false :default: ``''`` .. versionadded:: 3.5.0 Since release 3.5.0 phpMyAdmin can be configured to remember several things (sorted column :config:option:`$cfg['RememberSorting']`, column order, and column visibility from a database table) for browsing tables. Without configuring the storage, these features still can be used, but the values will disappear after you logout. To allow the usage of these functionality persistently: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['table_uiprefs']` (e.g. ``pma__table_uiprefs``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['users'] :type: string or false :default: ``''`` The table used by phpMyAdmin to store user name information for associating with user groups. See the next entry on :config:option:`$cfg['Servers'][$i]['usergroups']` for more details and the suggested settings.
.. config:option:: $cfg['Servers'][$i]['usergroups'] :type: string or false :default: ``''`` .. versionadded:: 4.1.0 Since release 4.1.0 you can create different user groups with menu items attached to them. Users can be assigned to these groups and the logged in user would only see menu items configured to the usergroup they are assigned to. To do this it needs two tables "usergroups" (storing allowed menu items for each user group) and "users" (storing users and their assignments to user groups). To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the correct table names in :config:option:`$cfg['Servers'][$i]['users']` (e.g. ``pma__users``) and :config:option:`$cfg['Servers'][$i]['usergroups']` (e.g. ``pma__usergroups``) This feature can be disabled by setting either of the configurations to ``false``. .. seealso:: :ref:`configurablemenus`
.. config:option:: $cfg['Servers'][$i]['navigationhiding'] :type: string or false :default: ``''`` .. versionadded:: 4.1.0 Since release 4.1.0 you can hide/show items in the navigation tree. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['navigationhiding']` (e.g. ``pma__navigationhiding``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['central_columns'] :type: string or false :default: ``''`` .. versionadded:: 4.3.0 Since release 4.3.0 you can have a central list of columns per database. You can add/remove columns to the list as per your requirement. These columns in the central list will be available to use while you create a new column for a table or create a table itself. You can select a column from central list while creating a new column, it will save you from writing the same column definition over again or from writing different names for similar column. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['central_columns']` (e.g. ``pma__central_columns``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['designer_settings'] :type: string or false :default: ``''`` .. versionadded:: 4.5.0 Since release 4.5.0 your designer settings can be remembered. Your choice regarding 'Angular/Direct Links', 'Snap to Grid', 'Toggle Relation Lines', 'Small/Big All', 'Move Menu' and 'Pin Text' can be remembered persistently. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['designer_settings']` (e.g. ``pma__designer_settings``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['savedsearches'] :type: string or false :default: ``''`` .. versionadded:: 4.2.0 Since release 4.2.0 you can save and load query-by-example searches from the Database > Query panel. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['savedsearches']` (e.g. ``pma__savedsearches``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['export_templates'] :type: string or false :default: ``''`` .. versionadded:: 4.5.0 Since release 4.5.0 you can save and load export templates. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['export_templates']` (e.g. ``pma__export_templates``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['tracking'] :type: string or false :default: ``''`` .. versionadded:: 3.3.x Since release 3.3.x a tracking mechanism is available. It helps you to track every :term:`SQL` command which is executed by phpMyAdmin. The mechanism supports logging of data manipulation and data definition statements. After enabling it you can create versions of tables. The creation of a version has two effects: * phpMyAdmin saves a snapshot of the table, including structure and indexes. * phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number. Of course you can view the tracked changes. On the :guilabel:`Tracking` page a complete report is available for every version. For the report you can use filters, for example you can get a list of statements within a date range. When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','. In addition you can export the (filtered) report to a file or to a temporary database. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['tracking']` (e.g. ``pma__tracking``) This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['tracking_version_auto_create'] :type: boolean :default: false Whether the tracking mechanism creates versions for tables and views automatically. If this is set to true and you create a table or view with * CREATE TABLE ... * CREATE VIEW ... and no version exists for it, the mechanism will create a version for you automatically.
.. config:option:: $cfg['Servers'][$i]['tracking_default_statements'] :type: string :default: ``'CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,CREATE INDEX,DROP INDEX,INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,CREATE VIEW,ALTER VIEW,DROP VIEW,CREATE DATABASE,ALTER DATABASE,DROP DATABASE'`` Defines the list of statements the auto-creation uses for new versions.
.. config:option:: $cfg['Servers'][$i]['tracking_add_drop_view'] :type: boolean :default: true Whether a `DROP VIEW IF EXISTS` statement will be added as first line to the log when creating a view.
.. config:option:: $cfg['Servers'][$i]['tracking_add_drop_table'] :type: boolean :default: true Whether a `DROP TABLE IF EXISTS` statement will be added as first line to the log when creating a table.
.. config:option:: $cfg['Servers'][$i]['tracking_add_drop_database'] :type: boolean :default: true Whether a `DROP DATABASE IF EXISTS` statement will be added as first line to the log when creating a database.
.. config:option:: $cfg['Servers'][$i]['userconfig'] :type: string or false :default: ``''`` .. versionadded:: 3.4.x Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves and store them in the database. If you don't allow for storing preferences in :config:option:`$cfg['Servers'][$i]['pmadb']`, users can still personalize phpMyAdmin, but settings will be saved in browser's local storage, or, it is is unavailable, until the end of session. To allow the usage of this functionality: * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage * put the table name in :config:option:`$cfg['Servers'][$i]['userconfig']` This feature can be disabled by setting the configuration to ``false``.
.. config:option:: $cfg['Servers'][$i]['MaxTableUiprefs'] :type: integer :default: 100 Maximum number of rows saved in :config:option:`$cfg['Servers'][$i]['table_uiprefs']` table. When tables are dropped or renamed, :config:option:`$cfg['Servers'][$i]['table_uiprefs']` may contain invalid data (referring to tables which no longer exist). We only keep this number of newest rows in :config:option:`$cfg['Servers'][$i]['table_uiprefs']` and automatically delete older rows.
.. config:option:: $cfg['Servers'][$i]['SessionTimeZone'] :type: string :default: ``''`` Sets the time zone used by phpMyAdmin. Leave blank to use the time zone of your database server. Possible values are explained at https://dev.mysql.com/doc/refman/8.0/en/time-zone-support.html This is useful when your database server uses a time zone which is different from the time zone you want to use in phpMyAdmin.
.. config:option:: $cfg['Servers'][$i]['AllowRoot'] :type: boolean :default: true Whether to allow root access. This is just a shortcut for the :config:option:`$cfg['Servers'][$i]['AllowDeny']['rules']` below.
.. config:option:: $cfg['Servers'][$i]['AllowNoPassword'] :type: boolean :default: false Whether to allow logins without a password. The default value of ``false`` for this parameter prevents unintended access to a MySQL server with was left with an empty password for root or on which an anonymous (blank) user is defined.
.. config:option:: $cfg['Servers'][$i]['AllowDeny']['order'] :type: string :default: ``''`` If your rule order is empty, then :term:`IP` authorization is disabled. If your rule order is set to ``'deny,allow'`` then the system applies all deny rules followed by allow rules. Access is allowed by default. Any client which does not match a Deny command or does match an Allow command will be allowed access to the server. If your rule order is set to ``'allow,deny'`` then the system applies all allow rules followed by deny rules. Access is denied by default. Any client which does not match an Allow directive or does match a Deny directive will be denied access to the server. If your rule order is set to ``'explicit'``, authorization is performed in a similar fashion to rule order 'deny,allow', with the added restriction that your host/username combination **must** be listed in the *allow* rules, and not listed in the *deny* rules. This is the **most** secure means of using Allow/Deny rules, and was available in Apache by specifying allow and deny rules without setting any order. Please also see :config:option:`$cfg['TrustedProxies']` for detecting IP address behind proxies.
.. config:option:: $cfg['Servers'][$i]['AllowDeny']['rules'] :type: array of strings :default: array() The general format for the rules is as such: .. code-block:: none <'allow' | 'deny'> <username> [from] <ipmask> If you wish to match all users, it is possible to use a ``'%'`` as a wildcard in the *username* field. There are a few shortcuts you can use in the *ipmask* field as well (please note that those containing SERVER_ADDRESS might not be available on all webservers): .. code-block:: none 'all' -> 0.0.0.0/0 'localhost' -> 127.0.0.1/8 'localnetA' -> SERVER_ADDRESS/8 'localnetB' -> SERVER_ADDRESS/16 'localnetC' -> SERVER_ADDRESS/24 Having an empty rule list is equivalent to either using ``'allow % from all'`` if your rule order is set to ``'deny,allow'`` or ``'deny % from all'`` if your rule order is set to ``'allow,deny'`` or ``'explicit'``. For the :term:`IP Address` matching system, the following work: * ``xxx.xxx.xxx.xxx`` (an exact :term:`IP Address`) * ``xxx.xxx.xxx.[yyy-zzz]`` (an :term:`IP Address` range) * ``xxx.xxx.xxx.xxx/nn`` (CIDR, Classless Inter-Domain Routing type :term:`IP` addresses) But the following does not work: * ``xxx.xxx.xxx.xx[yyy-zzz]`` (partial :term:`IP` address range) For :term:`IPv6` addresses, the following work: * ``xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx`` (an exact :term:`IPv6` address) * ``xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:[yyyy-zzzz]`` (an :term:`IPv6` address range) * ``xxxx:xxxx:xxxx:xxxx/nn`` (CIDR, Classless Inter-Domain Routing type :term:`IPv6` addresses) But the following does not work: * ``xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xx[yyy-zzz]`` (partial :term:`IPv6` address range) Examples: .. code-block:: none $cfg['Servers'][$i]['AllowDeny']['order'] = 'allow,deny'; $cfg['Servers'][$i]['AllowDeny']['rules'] = ['allow bob from all']; // Allow only 'bob' to connect from any host $cfg['Servers'][$i]['AllowDeny']['order'] = 'allow,deny'; $cfg['Servers'][$i]['AllowDeny']['rules'] = ['allow mary from 192.168.100.[50-100]']; // Allow only 'mary' to connect from host 192.168.100.50 through 192.168.100.100 $cfg['Servers'][$i]['AllowDeny']['order'] = 'allow,deny'; $cfg['Servers'][$i]['AllowDeny']['rules'] = ['allow % from 192.168.[5-6].10']; // Allow any user to connect from host 192.168.5.10 or 192.168.6.10 $cfg['Servers'][$i]['AllowDeny']['order'] = 'allow,deny'; $cfg['Servers'][$i]['AllowDeny']['rules'] = ['allow root from 192.168.5.50','allow % from 192.168.6.10']; // Allow any user to connect from 192.168.6.10, and additionally allow root to connect from 192.168.5.50
.. config:option:: $cfg['Servers'][$i]['DisableIS'] :type: boolean :default: false Disable using ``INFORMATION_SCHEMA`` to retrieve information (use ``SHOW`` commands instead), because of speed issues when many databases are present. .. note:: Enabling this option might give you a big performance boost on older MySQL servers.
.. config:option:: $cfg['Servers'][$i]['SignonScript'] :type: string :default: ``''`` .. versionadded:: 3.5.0 Name of PHP script to be sourced and executed to obtain login credentials. This is alternative approach to session based single signon. The script has to provide a function called ``get_login_credentials`` which returns list of username and password, accepting single parameter of existing username (can be empty). See :file:`examples/signon-script.php` for an example: .. literalinclude:: ../examples/signon-script.php :language: php .. seealso:: :ref:`auth_signon`
.. config:option:: $cfg['Servers'][$i]['SignonSession'] :type: string :default: ``''`` Name of session which will be used for signon authentication method. You should use something different than ``phpMyAdmin``, because this is session which phpMyAdmin uses internally. Takes effect only if :config:option:`$cfg['Servers'][$i]['SignonScript']` is not configured. .. seealso:: :ref:`auth_signon`
.. config:option:: $cfg['Servers'][$i]['SignonCookieParams'] :type: array :default: ``array()`` .. versionadded:: 4.7.0 An associative array of session cookie parameters of other authentication system. It is not needed if the other system doesn't use session_set_cookie_params(). Keys should include 'lifetime', 'path', 'domain', 'secure' or 'httponly'. Valid values are mentioned in `session_get_cookie_params <https://www.php.net/manual/en/ function.session-get-cookie-params.php>`_, they should be set to same values as the other application uses. Takes effect only if :config:option:`$cfg['Servers'][$i]['SignonScript']` is not configured. .. seealso:: :ref:`auth_signon`
.. config:option:: $cfg['Servers'][$i]['SignonURL'] :type: string :default: ``''`` :term:`URL` where user will be redirected to log in for signon authentication method. Should be absolute including protocol. .. seealso:: :ref:`auth_signon`
.. config:option:: $cfg['Servers'][$i]['LogoutURL'] :type: string :default: ``''`` :term:`URL` where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
.. config:option:: $cfg['Servers'][$i]['hide_connection_errors'] :type: boolean :default: false .. versionadded:: 4.9.8 Whether to show or hide detailed MySQL/MariaDB connection errors on the login page. .. note:: This error message can contain the target database server hostname or IP address, which may reveal information about your network to an attacker.
Generic settings
.. config:option:: $cfg['DisableShortcutKeys'] :type: boolean :default: false You can disable phpMyAdmin shortcut keys by setting :config:option:`$cfg['DisableShortcutKeys']` to true.
.. config:option:: $cfg['ServerDefault'] :type: integer :default: 1 If you have more than one server configured, you can set :config:option:`$cfg['ServerDefault']` to any one of them to autoconnect to that server when phpMyAdmin is started, or set it to 0 to be given a list of servers without logging in. If you have only one server configured, :config:option:`$cfg['ServerDefault']` MUST be set to that server.
.. config:option:: $cfg['VersionCheck'] :type: boolean :default: true Enables check for latest versions using JavaScript on the main phpMyAdmin page or by directly accessing `index.php?route=/version-check`. .. note:: This setting can be adjusted by your vendor.
.. config:option:: $cfg['ProxyUrl'] :type: string :default: ``''`` The url of the proxy to be used when phpmyadmin needs to access the outside internet such as when retrieving the latest version info or submitting error reports. You need this if the server where phpMyAdmin is installed does not have direct access to the internet. The format is: "hostname:portnumber"
.. config:option:: $cfg['ProxyUser'] :type: string :default: ``''`` The username for authenticating with the proxy. By default, no authentication is performed. If a username is supplied, Basic Authentication will be performed. No other types of authentication are currently supported.
.. config:option:: $cfg['ProxyPass'] :type: string :default: ``''`` The password for authenticating with the proxy.
.. config:option:: $cfg['MaxDbList'] :type: integer :default: 100 The maximum number of database names to be displayed in the main panel's database list.
.. config:option:: $cfg['MaxTableList'] :type: integer :default: 250 The maximum number of table names to be displayed in the main panel's list (except on the Export page).
.. config:option:: $cfg['ShowHint'] :type: boolean :default: true Whether or not to show hints (for example, hints when hovering over table headers).
.. config:option:: $cfg['MaxCharactersInDisplayedSQL'] :type: integer :default: 1000 The maximum number of characters when a :term:`SQL` query is displayed. The default limit of 1000 should be correct to avoid the display of tons of hexadecimal codes that represent BLOBs, but some users have real :term:`SQL` queries that are longer than 1000 characters. Also, if a query's length exceeds this limit, this query is not saved in the history.
.. config:option:: $cfg['PersistentConnections'] :type: boolean :default: false Whether `persistent connections <https://www.php.net/manual/en/features .persistent-connections.php>`_ should be used or not.
.. seealso:: `mysqli documentation for persistent connections <https://www.php.net/manual/en/mysqli.persistconns.php>`_
.. config:option:: $cfg['ForceSSL'] :type: boolean :default: false .. deprecated:: 4.6.0 This setting is no longer available since phpMyAdmin 4.6.0. Please adjust your webserver instead. Whether to force using https while accessing phpMyAdmin. In a reverse proxy setup, setting this to ``true`` is not supported. .. note:: In some setups (like separate SSL proxy or load balancer) you might have to set :config:option:`$cfg['PmaAbsoluteUri']` for correct redirection.
.. config:option:: $cfg['MysqlSslWarningSafeHosts'] :type: array :default: ``['127.0.0.1', 'localhost']`` This search is case-sensitive and will match the exact string only. If your setup does not use SSL but is safe because you are using a local connection or private network, you can add your hostname or :term:`IP` to the list. You can also remove the default entries to only include yours. This check uses the value of :config:option:`$cfg['Servers'][$i]['host']`. .. versionadded:: 5.1.0 Example configuration .. code-block:: php $cfg['MysqlSslWarningSafeHosts'] = ['127.0.0.1', 'localhost', 'mariadb.local'];
.. config:option:: $cfg['ExecTimeLimit'] :type: integer [number of seconds] :default: 300 Set the number of seconds a script is allowed to run. If seconds is set to zero, no time limit is imposed. This setting is used while importing/exporting dump files but has no effect when PHP is running in safe mode.
.. config:option:: $cfg['SessionSavePath'] :type: string :default: ``''`` Path for storing session data (`session_save_path PHP parameter <https://www.php.net/session_save_path>`_). .. warning:: This folder should not be publicly accessible through the webserver, otherwise you risk leaking private data from your session.
.. config:option:: $cfg['MemoryLimit'] :type: string [number of bytes] :default: ``'-1'`` Set the number of bytes a script is allowed to allocate. If set to ``'-1'``, no limit is imposed. If set to ``'0'``, no change of the memory limit is attempted and the :file:`php.ini` ``memory_limit`` is used. This setting is used while importing/exporting dump files so you definitely don't want to put here a too low value. It has no effect when PHP is running in safe mode. You can also use any string as in :file:`php.ini`, eg. '16M'. Ensure you don't omit the suffix (16 means 16 bytes!)
.. config:option:: $cfg['SkipLockedTables'] :type: boolean :default: false Mark used tables and make it possible to show databases with locked tables (since MySQL 3.23.30).
.. config:option:: $cfg['ShowSQL'] :type: boolean :default: true Defines whether :term:`SQL` queries generated by phpMyAdmin should be displayed or not.
.. config:option:: $cfg['RetainQueryBox'] :type: boolean :default: false Defines whether the :term:`SQL` query box should be kept displayed after its submission.
.. config:option:: $cfg['CodemirrorEnable'] :type: boolean :default: true Defines whether to use a Javascript code editor for SQL query boxes. CodeMirror provides syntax highlighting and line numbers. However, middle-clicking for pasting the clipboard contents in some Linux distributions (such as Ubuntu) is not supported by all browsers.
.. config:option:: $cfg['LintEnable'] :type: boolean :default: true .. versionadded:: 4.5.0 Defines whether to use the parser to find any errors in the query before executing.
.. config:option:: $cfg['DefaultForeignKeyChecks'] :type: string :default: ``'default'`` Default value of the checkbox for foreign key checks, to disable/enable foreign key checks for certain queries. The possible values are ``'default'``, ``'enable'`` or ``'disable'``. If set to ``'default'``, the value of the MySQL variable ``FOREIGN_KEY_CHECKS`` is used.
.. config:option:: $cfg['AllowUserDropDatabase'] :type: boolean :default: false .. warning:: This is not a security measure as there will be always ways to circumvent this. If you want to prohibit users from dropping databases, revoke their corresponding DROP privilege. Defines whether normal users (non-administrator) are allowed to delete their own database or not. If set as false, the link :guilabel:`Drop Database` will not be shown, and even a ``DROP DATABASE mydatabase`` will be rejected. Quite practical for :term:`ISP` 's with many customers. This limitation of :term:`SQL` queries is not as strict as when using MySQL privileges. This is due to nature of :term:`SQL` queries which might be quite complicated. So this choice should be viewed as help to avoid accidental dropping rather than strict privilege limitation.
.. config:option:: $cfg['Confirm'] :type: boolean :default: true Whether a warning ("Are your really sure...") should be displayed when you're about to lose data.
.. config:option:: $cfg['UseDbSearch'] :type: boolean :default: true Define whether the "search string inside database" is enabled or not.
.. config:option:: $cfg['IgnoreMultiSubmitErrors'] :type: boolean :default: false Define whether phpMyAdmin will continue executing a multi-query statement if one of the queries fails. Default is to abort execution.
.. config:option:: $cfg['enable_drag_drop_import'] :type: boolean :default: true Whether or not the drag and drop import feature is enabled. When enabled, a user can drag a file in to their browser and phpMyAdmin will attempt to import the file.
.. config:option:: $cfg['URLQueryEncryption'] :type: boolean :default: false .. versionadded:: 4.9.8 Define whether phpMyAdmin will encrypt sensitive data (like database name and table name) from the URL query string. Default is to not encrypt the URL query string.
.. config:option:: $cfg['URLQueryEncryptionSecretKey'] :type: string :default: ``''`` .. versionadded:: 4.9.8 A secret key used to encrypt/decrypt the URL query string. Should be 32 bytes long. .. seealso:: :ref:`faq2_10`
.. config:option:: $cfg['maxRowPlotLimit'] :type: integer :default: 500 Maximum number of rows retrieved for zoom search.
Cookie authentication options
.. config:option:: $cfg['blowfish_secret'] :type: string :default: ``''`` The "cookie" auth_type uses the :term:`Sodium` extension to encrypt the cookies (see :term:`Cookie`). If you are using the "cookie" auth_type, enter here a generated string of random bytes to be used as an encryption key. It will be used internally by the :term:`Sodium` extension: you won't be prompted for this encryption key. Since a binary string is usually not printable, it can be converted into a hexadecimal representation (using a function like `sodium_bin2hex <https://www.php.net/sodium_bin2hex>`_) and then used in the configuration file. For example: .. code-block:: php // The string is a hexadecimal representation of a 32-bytes long string of random bytes. $cfg['blowfish_secret'] = sodium_hex2bin('f16ce59f45714194371b48fe362072dc3b019da7861558cd4ad29e4d6fb13851'); Using a binary string is recommended. However, if all 32 bytes of the string are visible characters, then a function like `sodium_bin2hex <https://www.php.net/sodium_bin2hex>`_ is not required. For example: .. code-block:: php // A string of 32 characters. $cfg['blowfish_secret'] = 'JOFw435365IScA&Q!cDugr!lSfuAz*OW'; .. warning:: The encryption key must be 32 bytes long. If it is longer than the length of bytes, only the first 32 bytes will be used, and if it is shorter, a new temporary key will be automatically generated for you. However, this temporary key will only last for the duration of the session. .. note:: The configuration is called blowfish_secret for historical reasons as Blowfish algorithm was originally used to do the encryption. .. versionchanged:: 3.1.0 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it makes a bit weaker security as this generated secret is stored in session and furthermore it makes impossible to recall user name from cookie. .. versionchanged:: 5.2.0 Since version 5.2.0, phpMyAdmin uses the `sodium_crypto_secretbox <https://www.php.net/sodium_crypto_secretbox>`_ and `sodium_crypto_secretbox_open <https://www.php.net/sodium_crypto_secretbox_open>`_ PHP functions to encrypt and decrypt cookies, respectively. .. seealso:: :ref:`faq2_10`
.. config:option:: $cfg['CookieSameSite'] :type: string :default: ``'Strict'`` .. versionadded:: 5.1.0 It sets SameSite attribute of the Set-Cookie :term:`HTTP` response header. Valid values are: * ``Lax`` * ``Strict`` * ``None`` .. seealso:: `rfc6265 bis <https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-03#section-5.3.7>`_
.. config:option:: $cfg['LoginCookieRecall'] :type: boolean :default: true Define whether the previous login should be recalled or not in cookie authentication mode. This is automatically disabled if you do not have configured :config:option:`$cfg['blowfish_secret']`.
.. config:option:: $cfg['LoginCookieValidity'] :type: integer [number of seconds] :default: 1440 Define how long a login cookie is valid. Please note that php configuration option `session.gc_maxlifetime <https://www.php.net/manual/en/session.configuration.php#ini.session.gc- maxlifetime>`_ might limit session validity and if the session is lost, the login cookie is also invalidated. So it is a good idea to set ``session.gc_maxlifetime`` at least to the same value of :config:option:`$cfg['LoginCookieValidity']`.
.. config:option:: $cfg['LoginCookieStore'] :type: integer [number of seconds] :default: 0 Define how long login cookie should be stored in browser. Default 0 means that it will be kept for existing session. This is recommended for not trusted environments.
.. config:option:: $cfg['LoginCookieDeleteAll'] :type: boolean :default: true If enabled (default), logout deletes cookies for all servers, otherwise only for current one. Setting this to false makes it easy to forget to log out from other server, when you are using more of them.
.. config:option:: $cfg['AllowArbitraryServer'] :type: boolean :default: false If enabled, allows you to log in to arbitrary servers using cookie authentication. .. note:: Please use this carefully, as this may allow users access to MySQL servers behind the firewall where your :term:`HTTP` server is placed. See also :config:option:`$cfg['ArbitraryServerRegexp']`.
.. config:option:: $cfg['ArbitraryServerRegexp'] :type: string :default: ``''`` Restricts the MySQL servers to which the user can log in when :config:option:`$cfg['AllowArbitraryServer']` is enabled by matching the :term:`IP` or the hostname of the MySQL server to the given regular expression. The regular expression must be enclosed with a delimiter character. It is recommended to include start and end symbols in the regular expression, so that you can avoid partial matches on the string. **Examples:** .. code-block:: php // Allow connection to three listed servers: $cfg['ArbitraryServerRegexp'] = '/^(server|another|yetdifferent)$/'; // Allow connection to range of IP addresses: $cfg['ArbitraryServerRegexp'] = '@^192.168.0.[0-9]{1,}$@'; // Allow connection to server name ending with -mysql: $cfg['ArbitraryServerRegexp'] = '@^[^:]-mysql$@'; .. note:: The whole server name is matched, it can include port as well. Due to way MySQL is permissive in connection parameters, it is possible to use connection strings as ```server:3306-mysql```. This can be used to bypass regular expression by the suffix, while connecting to another server.
.. config:option:: $cfg['CaptchaMethod'] :type: string :default: ``'invisible'`` Valid values are: * ``'invisible'`` Use an invisible captcha checking method; * ``'checkbox'`` Use a checkbox to confirm the user is not a robot. .. versionadded:: 5.0.3
.. config:option:: $cfg['CaptchaApi'] :type: string :default: ``'https://www.google.com/recaptcha/api.js'`` .. versionadded:: 5.1.0 The URL for the reCaptcha v2 service's API, either Google's or a compatible one.
.. config:option:: $cfg['CaptchaCsp'] :type: string :default: ``'https://apis.google.com https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ https://ssl.gstatic.com/'`` .. versionadded:: 5.1.0 The Content-Security-Policy snippet (URLs from which to allow embedded content) for the reCaptcha v2 service, either Google's or a compatible one.
.. config:option:: $cfg['CaptchaRequestParam'] :type: string :default: ``'g-recaptcha'`` .. versionadded:: 5.1.0 The request parameter used for the reCaptcha v2 service.
.. config:option:: $cfg['CaptchaResponseParam'] :type: string :default: ``'g-recaptcha-response'`` .. versionadded:: 5.1.0 The response parameter used for the reCaptcha v2 service.
.. config:option:: $cfg['CaptchaLoginPublicKey'] :type: string :default: ``''`` The public key for the reCaptcha service that can be obtained from the "Admin Console" on https://www.google.com/recaptcha/about/. .. seealso:: <https://developers.google.com/recaptcha/docs/v3> reCaptcha will be then used in :ref:`cookie`. .. versionadded:: 4.1.0
.. config:option:: $cfg['CaptchaLoginPrivateKey'] :type: string :default: ``''`` The private key for the reCaptcha service that can be obtained from the "Admin Console" on https://www.google.com/recaptcha/about/. .. seealso:: <https://developers.google.com/recaptcha/docs/v3> reCaptcha will be then used in :ref:`cookie`. .. versionadded:: 4.1.0
.. config:option:: $cfg['CaptchaSiteVerifyURL'] :type: string :default: ``''`` The URL for the reCaptcha service to do siteverify action. reCaptcha will be then used in :ref:`cookie`. .. versionadded:: 5.1.0
Navigation panel setup
.. config:option:: $cfg['ShowDatabasesNavigationAsTree'] :type: boolean :default: true In the navigation panel, replaces the database tree with a selector
.. config:option:: $cfg['FirstLevelNavigationItems'] :type: integer :default: 100 The number of first level databases that can be displayed on each page of navigation tree.
.. config:option:: $cfg['MaxNavigationItems'] :type: integer :default: 50 The number of items (tables, columns, indexes) that can be displayed on each page of the navigation tree.
.. config:option:: $cfg['NavigationTreeEnableGrouping'] :type: boolean :default: true Defines whether to group the databases based on a common prefix in their name :config:option:`$cfg['NavigationTreeDbSeparator']`.
.. config:option:: $cfg['NavigationTreeDbSeparator'] :type: string :default: ``'_'`` The string used to separate the parts of the database name when showing them in a tree.
.. config:option:: $cfg['NavigationTreeTableSeparator'] :type: string or array :default: ``'__'`` Defines a string to be used to nest table spaces. This means if you have tables like ``first__second__third`` this will be shown as a three-level hierarchy like: first > second > third. If set to false or empty, the feature is disabled. NOTE: You should not use this separator at the beginning or end of a table name or multiple times after another without any other characters in between.
.. config:option:: $cfg['NavigationTreeTableLevel'] :type: integer :default: 1 Defines how many sublevels should be displayed when splitting up tables by the above separator.
.. config:option:: $cfg['NumRecentTables'] :type: integer :default: 10 The maximum number of recently used tables shown in the navigation panel. Set this to 0 (zero) to disable the listing of recent tables.
.. config:option:: $cfg['NumFavoriteTables'] :type: integer :default: 10 The maximum number of favorite tables shown in the navigation panel. Set this to 0 (zero) to disable the listing of favorite tables.
.. config:option:: $cfg['ZeroConf'] :type: boolean :default: true Enables Zero Configuration mode in which the user will be offered a choice to create phpMyAdmin configuration storage in the current database or use the existing one, if already present. This setting has no effect if the phpMyAdmin configuration storage database is properly created and the related configuration directives (such as :config:option:`$cfg['Servers'][$i]['pmadb']` and so on) are configured.
.. config:option:: $cfg['NavigationLinkWithMainPanel'] :type: boolean :default: true Defines whether or not to link with main panel by highlighting the current database or table.
.. config:option:: $cfg['NavigationDisplayLogo'] :type: boolean :default: true Defines whether or not to display the phpMyAdmin logo at the top of the navigation panel.
.. config:option:: $cfg['NavigationLogoLink'] :type: string :default: ``'index.php'`` Enter the :term:`URL` where the logo in the navigation panel will point to. For use especially with self made theme which changes this. For relative/internal URLs, you need to have leading `` ./ `` or trailing characters `` ? `` such as ``'./index.php?route=/server/sql?'``. For external URLs, you should include URL protocol schemes (``http`` or ``https``) with absolute URLs. You may want to make the link open in a new browser tab, for that you need to use :config:option:`$cfg['NavigationLogoLinkWindow']`
.. config:option:: $cfg['NavigationLogoLinkWindow'] :type: string :default: ``'main'`` Whether to open the linked page in the main window (``main``) or in a new one (``new``). Note: use ``new`` if you are linking to ``phpmyadmin.net``. To open the link in the main window you will need to add the value of :config:option:`$cfg['NavigationLogoLink']` to :config:option:`$cfg['CSPAllow']` because of the :term:`Content Security Policy` header.
.. config:option:: $cfg['NavigationTreeDisplayItemFilterMinimum'] :type: integer :default: 30 Defines the minimum number of items (tables, views, routines and events) to display a JavaScript filter box above the list of items in the navigation tree. To disable the filter completely some high number can be used (e.g. 9999)
.. config:option:: $cfg['NavigationTreeDisplayDbFilterMinimum'] :type: integer :default: 30 Defines the minimum number of databases to display a JavaScript filter box above the list of databases in the navigation tree. To disable the filter completely some high number can be used (e.g. 9999)
.. config:option:: $cfg['NavigationDisplayServers'] :type: boolean :default: true Defines whether or not to display a server choice at the top of the navigation panel.
.. config:option:: $cfg['DisplayServersList'] :type: boolean :default: false Defines whether to display this server choice as links instead of in a drop-down.
.. config:option:: $cfg['NavigationTreeDefaultTabTable'] :type: string :default: ``'structure'`` Defines the tab displayed by default when clicking the small icon next to each table name in the navigation panel. The possible values are the localized equivalent of: * ``structure`` * ``sql`` * ``search`` * ``insert`` * ``browse``
.. config:option:: $cfg['NavigationTreeDefaultTabTable2'] :type: string :default: null Defines the tab displayed by default when clicking the second small icon next to each table name in the navigation panel. The possible values are the localized equivalent of: * ``(empty)`` * ``structure`` * ``sql`` * ``search`` * ``insert`` * ``browse``
.. config:option:: $cfg['NavigationTreeEnableExpansion'] :type: boolean :default: true Whether to offer the possibility of tree expansion in the navigation panel.
.. config:option:: $cfg['NavigationTreeShowTables'] :type: boolean :default: true Whether to show tables under database in the navigation panel.
.. config:option:: $cfg['NavigationTreeShowViews'] :type: boolean :default: true Whether to show views under database in the navigation panel.
.. config:option:: $cfg['NavigationTreeShowFunctions'] :type: boolean :default: true Whether to show functions under database in the navigation panel.
.. config:option:: $cfg['NavigationTreeShowProcedures'] :type: boolean :default: true Whether to show procedures under database in the navigation panel.
.. config:option:: $cfg['NavigationTreeShowEvents'] :type: boolean :default: true Whether to show events under database in the navigation panel.
.. config:option:: $cfg['NavigationTreeAutoexpandSingleDb'] :type: boolean :default: true Whether to expand single database in the navigation tree automatically.
.. config:option:: $cfg['NavigationWidth'] :type: integer :default: 240 Navigation panel width, set to 0 to collapse it by default.
Main panel
.. config:option:: $cfg['ShowStats'] :type: boolean :default: true Defines whether or not to display space usage and statistics about databases and tables. Note that statistics requires at least MySQL 3.23.3 and that, at this date, MySQL doesn't return such information for Berkeley DB tables.
.. config:option:: $cfg['ShowServerInfo'] :type: boolean|string :default: true Defines whether to display detailed server information on main page. Possible values are: * ``true`` to show all server information * ``false`` to hide server information * ``'database-server'`` to show only database server information * ``'web-server'`` to show only web server information You can additionally hide more information by using :config:option:`$cfg['Servers'][$i]['verbose']`. .. versionchanged:: 6.0.0 Added ``'database-server'`` and ``'web-server'`` options.
.. config:option:: $cfg['ShowPhpInfo'] :type: boolean :default: false Defines whether to display the :guilabel:`PHP information` or not at the starting main (right) frame. Please note that to block the usage of ``phpinfo()`` in scripts, you have to put this in your :file:`php.ini`: .. code-block:: ini disable_functions = phpinfo() .. warning:: Enabling phpinfo page will leak quite a lot of information about server setup. Is it not recommended to enable this on shared installations. This might also make easier some remote attacks on your installations, so enable this only when needed.
.. config:option:: $cfg['ShowChgPassword'] :type: boolean :default: true Defines whether to display the :guilabel:`Change password` link or not at the starting main (right) frame. This setting does not check MySQL commands entered directly. Please note that enabling the :guilabel:`Change password` link has no effect with config authentication mode: because of the hard coded password value in the configuration file, end users can't be allowed to change their passwords.
.. config:option:: $cfg['ShowCreateDb'] :type: boolean :default: true Defines whether to display the form for creating database or not at the starting main (right) frame. This setting does not check MySQL commands entered directly.
.. config:option:: $cfg['ShowGitRevision'] :type: boolean :default: true Defines whether to display information about the current Git revision (if applicable) on the main panel.
.. config:option:: $cfg['MysqlMinVersion'] :type: array Defines the minimum supported MySQL version. The default is chosen by the phpMyAdmin team; however this directive was asked by a developer of the Plesk control panel to ease integration with older MySQL servers (where most of the phpMyAdmin features work).
Database structure
.. config:option:: $cfg['ShowDbStructureCharset'] :type: boolean :default: false Defines whether to show a column displaying the charset for all tables in the database structure page.
.. config:option:: $cfg['ShowDbStructureComment'] :type: boolean :default: false Defines whether to show a column displaying the comments for all tables in the database structure page.
.. config:option:: $cfg['ShowDbStructureCreation'] :type: boolean :default: false Defines whether the database structure page (tables list) has a "Creation" column that displays when each table was created.
.. config:option:: $cfg['ShowDbStructureLastUpdate'] :type: boolean :default: false Defines whether the database structure page (tables list) has a "Last update" column that displays when each table was last updated.
.. config:option:: $cfg['ShowDbStructureLastCheck'] :type: boolean :default: false Defines whether the database structure page (tables list) has a "Last check" column that displays when each table was last checked.
.. config:option:: $cfg['HideStructureActions'] :type: boolean :default: true Defines whether the table structure actions are hidden under a ":guilabel:`More`" drop-down.
.. config:option:: $cfg['ShowColumnComments'] :type: boolean :default: true Defines whether to show column comments as a column in the table structure view.
Browse mode
.. config:option:: $cfg['TableNavigationLinksMode'] :type: string :default: ``'icons'`` Defines whether the table navigation links contain ``'icons'``, ``'text'`` or ``'both'``.
.. config:option:: $cfg['ActionLinksMode'] :type: string :default: ``'both'`` If set to ``icons``, will display icons instead of text for db and table properties links (like :guilabel:`Browse`, :guilabel:`Select`, :guilabel:`Insert`, ...). Can be set to ``'both'`` if you want icons AND text. When set to ``text``, will only show text.
.. config:option:: $cfg['RowActionType'] :type: string :default: ``'both'`` Whether to display icons or text or both icons and text in table row action segment. Value can be either of ``'icons'``, ``'text'`` or ``'both'``.
.. config:option:: $cfg['ShowAll'] :type: boolean :default: false Defines whether a user should be displayed a ":guilabel:`Show all`" button in browse mode or not in all cases. By default it is shown only on small tables (less than 500 rows) to avoid performance issues while getting too many rows.
.. config:option:: $cfg['MaxRows'] :type: integer :default: 25 Number of rows displayed when browsing a result set and no LIMIT clause is used. If the result set contains more rows, ":guilabel:`Previous`" and ":guilabel:`Next`" links will be shown. Possible values: 25,50,100,250,500.
.. config:option:: $cfg['Order'] :type: string :default: ``'SMART'`` Defines whether columns are displayed in ascending (``ASC``) order, in descending (``DESC``) order or in a "smart" (``SMART``) order - I.E. descending order for columns of type TIME, DATE, DATETIME and TIMESTAMP, ascending order else- by default. .. versionchanged:: 3.4.0 Since phpMyAdmin 3.4.0 the default value is ``'SMART'``.
.. config:option:: $cfg['DisplayBinaryAsHex'] :type: boolean :default: true Defines whether the ":guilabel:`Show binary contents as HEX`" browse option is ticked by default. .. versionadded:: 3.3.0 .. deprecated:: 4.3.0 This setting was removed.
.. config:option:: $cfg['GridEditing'] :type: string :default: ``'double-click'`` Defines which action (``double-click`` or ``click``) triggers grid editing. Can be deactivated with the ``disabled`` value.
.. config:option:: $cfg['RelationalDisplay'] :type: string :default: ``'K'`` Defines the initial behavior for Options > Relational. ``K``, which is the default, displays the key while ``D`` shows the display column.
.. config:option:: $cfg['SaveCellsAtOnce'] :type: boolean :default: false Defines whether or not to save all edited cells at once for grid editing.
Editing mode
.. config:option:: $cfg['ProtectBinary'] :type: boolean or string :default: ``'blob'`` Defines whether ``BLOB`` or ``BINARY`` columns are protected from editing when browsing a table's content. Valid values are: * ``false`` to allow editing of all columns; * ``'blob'`` to allow editing of all columns except ``BLOBS``; * ``'noblob'`` to disallow editing of all columns except ``BLOBS`` (the opposite of ``'blob'``); * ``'all'`` to disallow editing of all ``BINARY`` or ``BLOB`` columns.
.. config:option:: $cfg['ShowFunctionFields'] :type: boolean :default: true Defines whether or not MySQL functions fields should be initially displayed in edit/insert mode. Since version 2.10, the user can toggle this setting from the interface.
.. config:option:: $cfg['ShowFieldTypesInDataEditView'] :type: boolean :default: true Defines whether or not type fields should be initially displayed in edit/insert mode. The user can toggle this setting from the interface.
.. config:option:: $cfg['InsertRows'] :type: integer :default: 2 Defines the default number of rows to be entered from the Insert page. Users can manually change this from the bottom of that page to add or remove blank rows.
.. config:option:: $cfg['ForeignKeyMaxLimit'] :type: integer :default: 100 If there are fewer items than this in the set of foreign keys, then a drop-down box of foreign keys is presented, in the style described by the :config:option:`$cfg['ForeignKeyDropdownOrder']` setting.
.. config:option:: $cfg['ForeignKeyDropdownOrder'] :type: array :default: array('content-id', 'id-content') For the foreign key drop-down fields, there are several methods of display, offering both the key and value data. The contents of the array should be one or both of the following strings: ``content-id``, ``id-content``.
Export and import settings
.. config:option:: $cfg['ZipDump'] :type: boolean :default: true
.. config:option:: $cfg['GZipDump'] :type: boolean :default: true
.. config:option:: $cfg['BZipDump'] :type: boolean :default: true Defines whether to allow the use of zip/GZip/BZip2 compression when creating a dump file
.. config:option:: $cfg['CompressOnFly'] :type: boolean :default: true Defines whether to allow on the fly compression for GZip/BZip2 compressed exports. This doesn't affect smaller dumps and allows users to create larger dumps that won't otherwise fit in memory due to php memory limit. Produced files contain more GZip/BZip2 headers, but all normal programs handle this correctly.
.. config:option:: $cfg['Export'] :type: array :default: array(...) In this array are defined default parameters for export, names of items are similar to texts seen on export page, so you can easily identify what they mean.
.. config:option:: $cfg['Export']['format'] :type: string :default: ``'sql'`` Default export format.
.. config:option:: $cfg['Export']['method'] :type: string :default: ``'quick'`` Defines how the export form is displayed when it loads. Valid values are: * ``quick`` to display the minimum number of options to configure * ``custom`` to display every available option to configure * ``custom-no-form`` same as ``custom`` but does not display the option of using quick export
.. config:option:: $cfg['Export']['compression'] :type: string :default: ``'none'`` Default export compression method. Possible values are ``'none'``, ``'zip'`` or ``'gzip'``.
.. config:option:: $cfg['Export']['charset'] :type: string :default: ``''`` Defines charset for generated export. By default no charset conversion is done assuming UTF-8.
.. config:option:: $cfg['Export']['file_template_table'] :type: string :default: ``'@TABLE@'`` Default filename template for table exports. .. seealso:: :ref:`faq6_27`
.. config:option:: $cfg['Export']['file_template_database'] :type: string :default: ``'@DATABASE@'`` Default filename template for database exports. .. seealso:: :ref:`faq6_27`
.. config:option:: $cfg['Export']['file_template_server'] :type: string :default: ``'@SERVER@'`` Default filename template for server exports. .. seealso:: :ref:`faq6_27`
.. config:option:: $cfg['Export']['remove_definer_from_definitions'] :type: boolean :default: false Remove DEFINER clause from the event, view and routine definitions. .. versionadded:: 5.2.0
.. config:option:: $cfg['Import'] :type: array :default: array(...) In this array are defined default parameters for import, names of items are similar to texts seen on import page, so you can easily identify what they mean.
.. config:option:: $cfg['Import']['charset'] :type: string :default: ``''`` Defines charset for import. By default no charset conversion is done assuming UTF-8.
.. config:option:: $cfg['Schema'] :type: array :default: array(...)
.. config:option:: $cfg['Schema']['format'] :type: string :default: ``'pdf'`` Defines the default format for schema export. Possible values are ``'pdf'``, ``'eps'``, ``'dia'`` or ``'svg'``.
Tabs display settings
.. config:option:: $cfg['TabsMode'] :type: string :default: ``'both'`` Defines whether the menu tabs contain ``'icons'``, ``'text'`` or ``'both'``.
.. config:option:: $cfg['PropertiesNumColumns'] :type: integer :default: 1 How many columns will be utilized to display the tables on the database property view? When setting this to a value larger than 1, the type of the database will be omitted for more display space.
.. config:option:: $cfg['DefaultTabServer'] :type: string :default: ``'welcome'`` Defines the tab displayed by default on server view. The possible values are the localized equivalent of: * ``welcome`` (recommended for multi-user setups) * ``databases``, * ``status`` * ``variables`` * ``privileges``
.. config:option:: $cfg['DefaultTabDatabase'] :type: string :default: ``'structure'`` Defines the tab displayed by default on database view. The possible values are the localized equivalent of: * ``structure`` * ``sql`` * ``search`` * ``operations``
.. config:option:: $cfg['DefaultTabTable'] :type: string :default: ``'browse'`` Defines the tab displayed by default on table view. The possible values are the localized equivalent of: * ``structure`` * ``sql`` * ``search`` * ``insert`` * ``browse``
PDF Options
.. config:option:: $cfg['PDFPageSizes'] :type: array :default: ``array('A3', 'A4', 'A5', 'letter', 'legal')`` Array of possible paper sizes for creating PDF pages. You should never need to change this.
.. config:option:: $cfg['PDFDefaultPageSize'] :type: string :default: ``'A4'`` Default page size to use when creating PDF pages. Valid values are any listed in :config:option:`$cfg['PDFPageSizes']`.
Languages
.. config:option:: $cfg['DefaultLang'] :type: string :default: ``'en'`` Defines the default language to use, if not browser-defined or user- defined. The corresponding language file needs to be in locale/*code*/LC_MESSAGES/phpmyadmin.mo.
.. config:option:: $cfg['DefaultConnectionCollation'] :type: string :default: ``'utf8mb4_general_ci'`` Defines the default connection collation to use, if not user-defined. See the `MySQL documentation for charsets <https://dev.mysql.com/doc/refman/5.7/en/charset-charsets.html>`_ for list of possible values.
.. config:option:: $cfg['Lang'] :type: string :default: not set Force language to use. The corresponding language file needs to be in locale/*code*/LC_MESSAGES/phpmyadmin.mo.
.. config:option:: $cfg['FilterLanguages'] :type: string :default: ``''`` Limit list of available languages to those matching the given regular expression. For example if you want only Czech and English, you should set filter to ``'^(cs|en)'``.
.. config:option:: $cfg['RecodingEngine'] :type: string :default: ``'auto'`` You can select here which functions will be used for character set conversion. Possible values are: * auto - automatically use available one (first is tested iconv, then recode) * iconv - use iconv or libiconv functions * recode - use recode_string function * mb - use :term:`mbstring` extension * none - disable encoding conversion Enabled charset conversion activates a pull-down menu in the Export and Import pages, to choose the character set when exporting a file. The default value in this menu comes from :config:option:`$cfg['Export']['charset']` and :config:option:`$cfg['Import']['charset']`.
.. config:option:: $cfg['IconvExtraParams'] :type: string :default: ``'//TRANSLIT'`` Specify some parameters for iconv used in charset conversion. See `iconv documentation <https://www.gnu.org/savannah-checkouts/gnu/libiconv/documentati on/libiconv-1.15/iconv_open.3.html>`_ for details. By default ``//TRANSLIT`` is used, so that invalid characters will be transliterated.
.. config:option:: $cfg['AvailableCharsets'] :type: array :default: array(...) Available character sets for MySQL conversion. You can add your own (any of supported by recode/iconv) or remove these which you don't use. Character sets will be shown in same order as here listed, so if you frequently use some of these move them to the top.
Web server settings
.. config:option:: $cfg['OBGzip'] :type: string/boolean :default: ``'auto'`` Defines whether to use GZip output buffering for increased speed in :term:`HTTP` transfers. Set to true/false for enabling/disabling. When set to 'auto' (string), phpMyAdmin tries to enable output buffering and will automatically disable it if your browser has some problems with buffering. IE6 with a certain patch is known to cause data corruption when having enabled buffering.
.. config:option:: $cfg['TrustedProxies'] :type: array :default: array() Lists proxies and HTTP headers which are trusted for :config:option:`$cfg['Servers'][$i]['AllowDeny']['order']`. This list is by default empty, you need to fill in some trusted proxy servers if you want to use rules for IP addresses behind proxy. The following example specifies that phpMyAdmin should trust a HTTP_X_FORWARDED_FOR (``X-Forwarded-For``) header coming from the proxy 1.2.3.4: .. code-block:: php $cfg['TrustedProxies'] = ['1.2.3.4' => 'HTTP_X_FORWARDED_FOR']; The :config:option:`$cfg['Servers'][$i]['AllowDeny']['rules']` directive uses the client's IP address as usual.
.. config:option:: $cfg['GD2Available'] :type: string :default: ``'auto'`` Specifies whether GD >= 2 is available. If yes it can be used for MIME transformations. Possible values are: * auto - automatically detect * yes - GD 2 functions can be used * no - GD 2 function cannot be used
.. config:option:: $cfg['CheckConfigurationPermissions'] :type: boolean :default: true We normally check the permissions on the configuration file to ensure it's not world writable. However, phpMyAdmin could be installed on a NTFS filesystem mounted on a non-Windows server, in which case the permissions seems wrong but in fact cannot be detected. In this case a sysadmin would set this parameter to ``false``.
.. config:option:: $cfg['LinkLengthLimit'] :type: integer :default: 1000 Limit for length of :term:`URL` in links. When length would be above this limit, it is replaced by form with button. This is required as some web servers (:term:`IIS`) have problems with long :term:`URL` .
.. config:option:: $cfg['CSPAllow'] :type: string :default: ``''`` Additional string to include in allowed script and image sources in Content Security Policy header. This can be useful when you want to include some external JavaScript files in :file:`config.footer.inc.php` or :file:`config.header.inc.php`, which would be normally not allowed by :term:`Content Security Policy`. To allow some sites, just list them within the string: .. code-block:: php $cfg['CSPAllow'] = 'example.com example.net'; .. versionadded:: 4.0.4
.. config:option:: $cfg['DisableMultiTableMaintenance'] :type: boolean :default: false In the database Structure page, it's possible to mark some tables then choose an operation like optimizing for many tables. This can slow down a server; therefore, setting this to ``true`` prevents this kind of multiple maintenance operation.
Theme settings
Please directly modify :file:`themes/themename/scss/_variables.scss`, although
your changes will be overwritten with the next update.
Design customization
.. config:option:: $cfg['NavigationTreePointerEnable'] :type: boolean :default: true When set to true, hovering over an item in the navigation panel causes that item to be marked (the background is highlighted).
.. config:option:: $cfg['BrowsePointerEnable'] :type: boolean :default: true When set to true, hovering over a row in the Browse page causes that row to be marked (the background is highlighted).
.. config:option:: $cfg['BrowseMarkerEnable'] :type: boolean :default: true When set to true, a data row is marked (the background is highlighted) when the row is selected with the checkbox.
.. config:option:: $cfg['LimitChars'] :type: integer :default: 50 Maximum number of characters shown in any non-numeric field on browse view. Can be turned off by a toggle button on the browse page.
.. config:option:: $cfg['RowActionLinks'] :type: string :default: ``'left'`` Defines the place where table row links (Edit, Copy, Delete) would be put when tables contents are displayed (you may have them displayed at the left side, right side, both sides or nowhere).
.. config:option:: $cfg['RowActionLinksWithoutUnique'] :type: boolean :default: false Defines whether to show row links (Edit, Copy, Delete) and checkboxes for multiple row operations even when the selection does not have a :term:`unique key`. Using row actions in the absence of a unique key may result in different/more rows being affected since there is no guaranteed way to select the exact row(s).
.. config:option:: $cfg['RememberSorting'] :type: boolean :default: true If enabled, remember the sorting of each table when browsing them.
.. config:option:: $cfg['TablePrimaryKeyOrder'] :type: string :default: ``'NONE'`` This defines the default sort order for the tables, having a :term:`primary key`, when there is no sort order defines externally. Acceptable values : ['NONE', 'ASC', 'DESC']
.. config:option:: $cfg['ShowBrowseComments'] :type: boolean :default: true
.. config:option:: $cfg['ShowPropertyComments'] :type: boolean :default: true By setting the corresponding variable to ``true`` you can enable the display of column comments in Browse or Property display. In browse mode, the comments are shown inside the header. In property mode, comments are displayed using a CSS-formatted dashed-line below the name of the column. The comment is shown as a tool-tip for that column.
.. config:option:: $cfg['FirstDayOfCalendar'] :type: integer :default: 0 This will define the first day of week in the calendar. The number can be set from 0 to 6, which represents the seven days of the week, Sunday to Saturday respectively. This value can also be configured by the user in :guilabel:`Settings` -> :guilabel:`Features` -> :guilabel:`General` -> :guilabel:`First day of calendar` field.
Text fields
.. config:option:: $cfg['CharEditing'] :type: string :default: ``'input'`` Defines which type of editing controls should be used for CHAR and VARCHAR columns. Applies to data editing and also to the default values in structure editing. Possible values are: * input - this allows to limit size of text to size of columns in MySQL, but has problems with newlines in columns * textarea - no problems with newlines in columns, but also no length limitations
.. config:option:: $cfg['MinSizeForInputField'] :type: integer :default: 4 Defines the minimum size for input fields generated for CHAR and VARCHAR columns.
.. config:option:: $cfg['MaxSizeForInputField'] :type: integer :default: 60 Defines the maximum size for input fields generated for CHAR and VARCHAR columns.
.. config:option:: $cfg['TextareaCols'] :type: integer :default: 40
.. config:option:: $cfg['TextareaRows'] :type: integer :default: 15
.. config:option:: $cfg['CharTextareaCols'] :type: integer :default: 40
.. config:option:: $cfg['CharTextareaRows'] :type: integer :default: 7 Number of columns and rows for the textareas. This value will be emphasized (*2) for :term:`SQL` query textareas and (*1.25) for :term:`SQL` textareas inside the query window. The Char* values are used for CHAR and VARCHAR editing (if configured via :config:option:`$cfg['CharEditing']`). .. versionchanged:: 5.0.0 The default value was changed from 2 to 7.
.. config:option:: $cfg['LongtextDoubleTextarea'] :type: boolean :default: true Defines whether textarea for LONGTEXT columns should have double size.
.. config:option:: $cfg['TextareaAutoSelect'] :type: boolean :default: false Defines if the whole textarea of the query box will be selected on click.
.. config:option:: $cfg['EnableAutocompleteForTablesAndColumns'] :type: boolean :default: true Whether to enable autocomplete for table and column names in any SQL query box.
SQL query box settings
.. config:option:: $cfg['SQLQuery']['Edit'] :type: boolean :default: true Whether to display an edit link to change a query in any SQL Query box.
.. config:option:: $cfg['SQLQuery']['Explain'] :type: boolean :default: true Whether to display a link to explain a SELECT query in any SQL Query box.
.. config:option:: $cfg['SQLQuery']['ShowAsPHP'] :type: boolean :default: true Whether to display a link to wrap a query in PHP code in any SQL Query box.
.. config:option:: $cfg['SQLQuery']['Refresh'] :type: boolean :default: true Whether to display a link to refresh a query in any SQL Query box.
Web server upload/save/import directories
If PHP is running in safe mode, all directories must be owned by the same user
as the owner of the phpMyAdmin scripts.
If the directory where phpMyAdmin is installed is subject to an
open_basedir
restriction, you need to create a temporary directory in some
directory accessible by the PHP interpreter.
For security reasons, all directories should be outside the tree published by
webserver. If you cannot avoid having this directory published by webserver,
limit access to it either by web server configuration (for example using
.htaccess or web.config files) or place at least an empty :file:`index.html`
file there, so that directory listing is not possible. However as long as the
directory is accessible by web server, an attacker can guess filenames to download
the files.
.. config:option:: $cfg['UploadDir'] :type: string :default: ``''`` The name of the directory where :term:`SQL` files have been uploaded by other means than phpMyAdmin (for example, FTP). Those files are available under a drop-down box when you click the database or table name, then the Import tab. If you want different directory for each user, %u will be replaced with username. Please note that the file names must have the suffix ".sql" (or ".sql.bz2" or ".sql.gz" if support for compressed formats is enabled). This feature is useful when your file is too big to be uploaded via :term:`HTTP`, or when file uploads are disabled in PHP. .. warning:: Please see top of this chapter (:ref:`web-dirs`) for instructions how to setup this directory and how to make its usage secure. .. seealso:: See :ref:`faq1_16` for alternatives.
.. config:option:: $cfg['SaveDir'] :type: string :default: ``''`` The name of the webserver directory where exported files can be saved. If you want a different directory for each user, %u will be replaced with the username. Please note that the directory must exist and has to be writable for the user running webserver. .. warning:: Please see top of this chapter (:ref:`web-dirs`) for instructions how to setup this directory and how to make its usage secure.
.. config:option:: $cfg['TempDir'] :type: string :default: ``'./tmp/'`` The name of the directory where temporary files can be stored. It is used for several purposes, currently: * The templates cache which speeds up page loading. * ESRI Shapefiles import, see :ref:`faq6_30`. * To work around limitations of ``open_basedir`` for uploaded files, see :ref:`faq1_11`. This directory should have as strict permissions as possible as the only user required to access this directory is the one who runs the webserver. If you have root privileges, simply make this user owner of this directory and make it accessible only by it: .. code-block:: sh chown www-data:www-data tmp chmod 700 tmp If you cannot change owner of the directory, you can achieve a similar setup using :term:`ACL`: .. code-block:: sh chmod 700 tmp setfacl -m "g:www-data:rwx" tmp setfacl -d -m "g:www-data:rwx" tmp If neither of above works for you, you can still make the directory :command:`chmod 777`, but it might impose risk of other users on system reading and writing data in this directory. .. warning:: Please see top of this chapter (:ref:`web-dirs`) for instructions how to setup this directory and how to make its usage secure.
Various display setting
.. config:option:: $cfg['RepeatCells'] :type: integer :default: 100 Repeat the headers every X cells, or 0 to deactivate.
.. config:option:: $cfg['EditInWindow'] :type: boolean :default: true .. seealso:: `Feature request to add a pop-up window back <https://github.com/phpmyadmin/phpmyadmin/issues/11983>`_ .. deprecated:: 4.3.0 This setting was removed.
.. config:option:: $cfg['QueryWindowWidth'] :type: integer :default: 550 .. deprecated:: 4.3.0 This setting was removed.
.. config:option:: $cfg['QueryWindowHeight'] :type: integer :default: 310 .. deprecated:: 4.3.0 This setting was removed.
.. config:option:: $cfg['QueryHistoryDB'] :type: boolean :default: false
.. config:option:: $cfg['QueryWindowDefTab'] :type: string :default: ``'sql'`` .. deprecated:: 4.3.0 This setting was removed.
.. config:option:: $cfg['QueryHistoryMax'] :type: integer :default: 25 If :config:option:`$cfg['QueryHistoryDB']` is set to ``true``, all your Queries are logged to a table, which has to be created by you (see :config:option:`$cfg['Servers'][$i]['history']`). If set to false, all your queries will be appended to the form, but only as long as your window is opened they remain saved. When using the JavaScript based query window, it will always get updated when you click on a new table/db to browse and will focus if you click on :guilabel:`Edit SQL` after using a query. You can suppress updating the query window by checking the box :guilabel:`Do not overwrite this query from outside the window` below the query textarea. Then you can browse tables/databases in the background without losing the contents of the textarea, so this is especially useful when composing a query with tables you first have to look in. The checkbox will get automatically checked whenever you change the contents of the textarea. Please uncheck the button whenever you definitely want the query window to get updated even though you have made alterations. If :config:option:`$cfg['QueryHistoryDB']` is set to ``true`` you can specify the amount of saved history items using :config:option:`$cfg['QueryHistoryMax']`.
.. config:option:: $cfg['AllowSharedBookmarks'] :type: boolean :default: true .. versionadded:: 6.0.0 Allow users to create bookmarks that are available for all other users
.. config:option:: $cfg['BrowseMIME'] :type: boolean :default: true Enable :ref:`transformations`.
.. config:option:: $cfg['MaxExactCount'] :type: integer :default: 50000 For InnoDB tables, determines for how large tables phpMyAdmin should get the exact row count using ``SELECT COUNT``. If the approximate row count as returned by ``SHOW TABLE STATUS`` is smaller than this value, ``SELECT COUNT`` will be used, otherwise the approximate count will be used. .. versionchanged:: 4.8.0 The default value was lowered to 50000 for performance reasons. .. versionchanged:: 4.2.6 The default value was changed to 500000. .. seealso:: :ref:`faq3_11`
.. config:option:: $cfg['MaxExactCountViews'] :type: integer :default: 0 For VIEWs, since obtaining the exact count could have an impact on performance, this value is the maximum to be displayed, using a ``SELECT COUNT ... LIMIT``. Setting this to 0 bypasses any row counting.
.. config:option:: $cfg['NaturalOrder'] :type: boolean :default: true Sorts database and table names according to natural order (for example, t1, t2, t10). Currently implemented in the navigation panel and in Database view, for the table list.
.. config:option:: $cfg['InitialSlidersState'] :type: string :default: ``'closed'`` If set to ``'closed'``, the visual sliders are initially in a closed state. A value of ``'open'`` does the reverse. To completely disable all visual sliders, use ``'disabled'``.
.. config:option:: $cfg['UserprefsDisallow'] :type: array :default: array() Contains names of configuration options (keys in ``$cfg`` array) that users can't set through user preferences. For possible values, refer to classes under :file:`libraries/classes/Config/Forms/User/`.
.. config:option:: $cfg['UserprefsDeveloperTab'] :type: boolean :default: false .. versionadded:: 3.4.0 Activates in the user preferences a tab containing options for developers of phpMyAdmin.
Page titles
The page title displayed by your browser’s window or tab title bar can be customized. You can use :ref:`faq6_27`.
The following four options allow customizing various parts of the phpMyAdmin interface. Note that the login page
title cannot be changed.
.. config:option:: $cfg['TitleTable'] :type: string :default: ``'@HTTP_HOST@ / @VSERVER@ / @DATABASE@ / @TABLE@ | @PHPMYADMIN@'``
.. config:option:: $cfg['TitleDatabase'] :type: string :default: ``'@HTTP_HOST@ / @VSERVER@ / @DATABASE@ | @PHPMYADMIN@'``
.. config:option:: $cfg['TitleServer'] :type: string :default: ``'@HTTP_HOST@ / @VSERVER@ | @PHPMYADMIN@'``
.. config:option:: $cfg['TitleDefault'] :type: string :default: ``'@HTTP_HOST@ | @PHPMYADMIN@'``
Theme manager settings
.. config:option:: $cfg['ThemeManager'] :type: boolean :default: true Enables user-selectable themes. See :ref:`faqthemes`.
.. config:option:: $cfg['ThemeDefault'] :type: string :default: ``'pmahomme'`` The default theme (a subdirectory under :file:`./themes/`).
.. config:option:: $cfg['ThemePerServer'] :type: boolean :default: false Whether to allow different theme for each server.
.. config:option:: $cfg['FontSize'] :type: string :default: '82%' .. deprecated:: 5.0.0 This setting was removed as the browser is more efficient, thus no need of this option. Font size to use, is applied in CSS.
Default queries
.. config:option:: $cfg['DefaultQueryTable'] :type: string :default: ``'SELECT * FROM @TABLE@ WHERE 1'``
.. config:option:: $cfg['DefaultQueryDatabase'] :type: string :default: ``''`` Default queries that will be displayed in query boxes when user didn't specify any. You can use standard :ref:`faq6_27`.
MySQL settings
.. config:option:: $cfg['DefaultFunctions'] :type: array :default: ``array('FUNC_CHAR' => '', 'FUNC_DATE' => '', 'FUNC_NUMBER' => '', 'FUNC_SPATIAL' => 'GeomFromText', 'FUNC_UUID' => 'UUID', 'first_timestamp' => 'NOW')`` Functions selected by default when inserting/changing row, Functions are defined for meta types as (``FUNC_NUMBER``, ``FUNC_DATE``, ``FUNC_CHAR``, ``FUNC_SPATIAL``, ``FUNC_UUID``) and for ``first_timestamp``, which is used for first timestamp column in table. Example configuration .. code-block:: php $cfg['DefaultFunctions'] = [ 'FUNC_CHAR' => '', 'FUNC_DATE' => '', 'FUNC_NUMBER' => '', 'FUNC_SPATIAL' => 'ST_GeomFromText', 'FUNC_UUID' => 'UUID', 'first_timestamp' => 'UTC_TIMESTAMP', ];
Default options for Transformations
.. config:option:: $cfg['DefaultTransformations'] :type: array :default: An array with below listed key-values
.. config:option:: $cfg['DefaultTransformations']['Substring'] :type: array :default: array(0, 'all', '…')
.. config:option:: $cfg['DefaultTransformations']['Bool2Text'] :type: array :default: array('T', 'F')
.. config:option:: $cfg['DefaultTransformations']['External'] :type: array :default: array(0, '-f /dev/null -i -wrap -q', 1, 1)
.. config:option:: $cfg['DefaultTransformations']['PreApPend'] :type: array :default: array('', '')
.. config:option:: $cfg['DefaultTransformations']['Hex'] :type: array :default: array('2')
.. config:option:: $cfg['DefaultTransformations']['DateFormat'] :type: array :default: array(0, '', 'local')
.. config:option:: $cfg['DefaultTransformations']['Inline'] :type: array :default: array('100', 100)
.. config:option:: $cfg['DefaultTransformations']['TextImageLink'] :type: array :default: array('', 100, 50)
.. config:option:: $cfg['DefaultTransformations']['TextLink'] :type: array :default: array('', '', '')
Console settings
Note
These settings are mostly meant to be changed by user.
.. config:option:: $cfg['Console']['StartHistory'] :type: boolean :default: false Show query history at start
.. config:option:: $cfg['Console']['AlwaysExpand'] :type: boolean :default: false Always expand query messages
.. config:option:: $cfg['Console']['CurrentQuery'] :type: boolean :default: true Show current browsing query
.. config:option:: $cfg['Console']['EnterExecutes'] :type: boolean :default: false Execute queries on Enter and insert new line with Shift+Enter
.. config:option:: $cfg['Console']['DarkTheme'] :type: boolean :default: false Switch to dark theme
.. config:option:: $cfg['Console']['Mode'] :type: string :default: 'info' Console mode
.. config:option:: $cfg['Console']['Height'] :type: integer :default: 92 Console height
Developer
Warning
These settings might have huge effect on performance or security.
.. config:option:: $cfg['environment'] :type: string :default: ``'production'`` Sets the working environment. This only needs to be changed when you are developing phpMyAdmin itself. The ``development`` mode may display debug information in some places. Possible values are ``'production'`` or ``'development'``.
.. config:option:: $cfg['DBG'] :type: array :default: []
.. config:option:: $cfg['DBG']['sql'] :type: boolean :default: false Enable logging queries and execution times to be displayed in the console's Debug SQL tab.
.. config:option:: $cfg['DBG']['sqllog'] :type: boolean :default: false Enable logging of queries and execution times to the syslog. Requires :config:option:`$cfg['DBG']['sql']` to be enabled.
.. config:option:: $cfg['DBG']['demo'] :type: boolean :default: false Enable to let server present itself as demo server. This is used for `phpMyAdmin demo server <https://www.phpmyadmin.net/try/>`_. It currently changes following behavior: * There is welcome message on the main page. * There is footer information about demo server and used Git revision. * The setup script is enabled even with existing configuration. * The setup does not try to connect to the MySQL server.
.. config:option:: $cfg['DBG']['simple2fa'] :type: boolean :default: false Can be used for testing two-factor authentication using :ref:`simple2fa`.
Examples
See following configuration snippets for typical setups of phpMyAdmin.
Basic example
Example configuration file, which can be copied to :file:`config.inc.php` to
get some core configuration layout; it is distributed with phpMyAdmin as
:file:`config.sample.inc.php`. Please note that it does not contain all
configuration options, only the most frequently used ones.
.. literalinclude:: ../config.sample.inc.php :language: php
Warning
Don’t use the controluser ‘pma’ if it does not yet exist and don’t use ‘pmapass’
as password.
Example for signon authentication
This example uses :file:`examples/signon.php` to demonstrate usage of :ref:`auth_signon`:
<?php $i = 0; $i++; $cfg['Servers'][$i]['auth_type'] = 'signon'; $cfg['Servers'][$i]['SignonSession'] = 'SignonSession'; $cfg['Servers'][$i]['SignonURL'] = 'examples/signon.php';
Example for IP address limited autologin
If you want to automatically login when accessing phpMyAdmin locally while asking
for a password when accessing remotely, you can achieve it using following snippet:
if ($_SERVER['REMOTE_ADDR'] === '127.0.0.1') { $cfg['Servers'][$i]['auth_type'] = 'config'; $cfg['Servers'][$i]['user'] = 'root'; $cfg['Servers'][$i]['password'] = 'yourpassword'; } else { $cfg['Servers'][$i]['auth_type'] = 'cookie'; }
Note
Filtering based on IP addresses isn’t reliable over the internet, use it
only for local address.
Example for using multiple MySQL servers
You can configure any number of servers using :config:option:`$cfg[‘Servers’]`,
following example shows two of them:
<?php // The string is a hexadecimal representation of a 32-bytes long string of random bytes. $cfg['blowfish_secret'] = sodium_hex2bin('f16ce59f45714194371b48fe362072dc3b019da7861558cd4ad29e4d6fb13851'); $i = 0; $i++; // server 1 : $cfg['Servers'][$i]['auth_type'] = 'cookie'; $cfg['Servers'][$i]['verbose'] = 'no1'; $cfg['Servers'][$i]['host'] = 'localhost'; // more options for #1 ... $i++; // server 2 : $cfg['Servers'][$i]['auth_type'] = 'cookie'; $cfg['Servers'][$i]['verbose'] = 'no2'; $cfg['Servers'][$i]['host'] = 'remote.host.addr';//or ip:'10.9.8.1' // this server must allow remote clients, e.g., host 10.9.8.% // not only in mysql.host but also in the startup configuration // more options for #2 ... // end of server sections $cfg['ServerDefault'] = 0; // to choose the server on startup // further general options ...
Google Cloud SQL with SSL
To connect to Google Could SQL, you currently need to disable certificate
verification. This is caused by the certificate being issued for CN matching
your instance name, but you connect to an IP address and PHP tries to match
these two. With verification you end up with error message like:
Peer certificate CN=`api-project-851612429544:pmatest' did not match expected CN=`8.8.8.8'
Warning
With disabled verification your traffic is encrypted, but you’re open to
man in the middle attacks.
To connect phpMyAdmin to Google Cloud SQL using SSL download the client and
server certificates and tell phpMyAdmin to use them:
// IP address of your instance $cfg['Servers'][$i]['host'] = '8.8.8.8'; // Use SSL for connection $cfg['Servers'][$i]['ssl'] = true; // Client secret key $cfg['Servers'][$i]['ssl_key'] = '../client-key.pem'; // Client certificate $cfg['Servers'][$i]['ssl_cert'] = '../client-cert.pem'; // Server certification authority $cfg['Servers'][$i]['ssl_ca'] = '../server-ca.pem'; // Disable SSL verification (see above note) $cfg['Servers'][$i]['ssl_verify'] = false;
.. seealso:: :ref:`ssl`, :config:option:`$cfg['Servers'][$i]['ssl']`, :config:option:`$cfg['Servers'][$i]['ssl_key']`, :config:option:`$cfg['Servers'][$i]['ssl_cert']`, :config:option:`$cfg['Servers'][$i]['ssl_ca']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`, <https://bugs.php.net/bug.php?id=72048>
Amazon RDS Aurora with SSL
To connect phpMyAdmin to an Amazon RDS Aurora MySQL database instance using SSL,
download the CA server certificate and tell phpMyAdmin to use it:
// Address of your instance $cfg['Servers'][$i]['host'] = 'replace-me-cluster-name.cluster-replace-me-id.replace-me-region.rds.amazonaws.com'; // Use SSL for connection $cfg['Servers'][$i]['ssl'] = true; // You need to have the region CA file and the authority CA file (2019 edition CA for example) in the PEM bundle for it to work $cfg['Servers'][$i]['ssl_ca'] = '../rds-combined-ca-bundle.pem'; // Enable SSL verification $cfg['Servers'][$i]['ssl_verify'] = true;
.. seealso:: :ref:`ssl`, :config:option:`$cfg['Servers'][$i]['ssl']`, :config:option:`$cfg['Servers'][$i]['ssl_ca']`, :config:option:`$cfg['Servers'][$i]['ssl_verify']`
.. seealso:: - Current RDS CA bundle for all regions https://s3.amazonaws.com/rds-downloads/rds-combined-ca-bundle.pem - The RDS CA (2019 edition) for the region `eu-west-3` without the parent CA https://s3.amazonaws.com/rds-downloads/rds-ca-2019-eu-west-3.pem - `List of available Amazon RDS CA files <https://s3.amazonaws.com/rds-downloads/>`_ - `Amazon MySQL Aurora security guide <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Security.html>`_ - `Amazon certificates bundles per region <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.SSL.html>`_
reCaptcha using hCaptcha
$cfg['CaptchaApi'] = 'https://www.hcaptcha.com/1/api.js'; $cfg['CaptchaCsp'] = 'https://hcaptcha.com https://*.hcaptcha.com'; $cfg['CaptchaRequestParam'] = 'h-captcha'; $cfg['CaptchaResponseParam'] = 'h-captcha-response'; $cfg['CaptchaSiteVerifyURL'] = 'https://hcaptcha.com/siteverify'; // This is the secret key from hCaptcha dashboard $cfg['CaptchaLoginPrivateKey'] = '0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'; // This is the site key from hCaptcha dashboard $cfg['CaptchaLoginPublicKey'] = 'xxx-xxx-xxx-xxx-xxxx';
.. seealso:: `hCaptcha website <https://www.hcaptcha.com/>`_
.. seealso:: `hCaptcha Developer Guide <https://docs.hcaptcha.com/>`_
reCaptcha using Turnstile
$cfg['CaptchaMethod'] = 'checkbox'; $cfg['CaptchaApi'] = 'https://challenges.cloudflare.com/turnstile/v0/api.js'; $cfg['CaptchaCsp'] = 'https://challenges.cloudflare.com https://static.cloudflareinsights.com'; $cfg['CaptchaRequestParam'] = 'cf-turnstile'; $cfg['CaptchaResponseParam'] = 'cf-turnstile-response'; $cfg['CaptchaLoginPublicKey'] = '0xxxxxxxxxxxxxxxxxxxxxx'; $cfg['CaptchaLoginPrivateKey'] = '0x4AAAAAAAA_xx_xxxxxxxxxxxxxxxxxxxx'; $cfg['CaptchaSiteVerifyURL'] = 'https://challenges.cloudflare.com/turnstile/v0/siteverify';
.. seealso:: `Cloudflare Dashboard <https://dash.cloudflare.com/>`_
.. seealso:: `Turnstile Developer Guide <https://developers.cloudflare.com/turnstile/get-started/>`_
reCaptcha using Google reCaptcha v2/v3
$cfg['CaptchaLoginPublicKey'] = 'xxxxxxxxxxxxxxxx-xxxxxxxxxxxx'; $cfg['CaptchaLoginPrivateKey'] = 'xxxxxxxxx-xxxxxxxxxxxxxx'; // Remove it if you dot not want the checkbox mode $cfg['CaptchaMethod'] = 'checkbox';
.. seealso:: `Google reCaptcha Developer's Guide <https://developers.google.com/recaptcha/intro>`_
.. seealso:: `Google reCaptcha types <https://developers.google.com/recaptcha/docs/versions>`_
phpMyAdmin is a web-based tool to help manage MariaDB or MySQL databases, written primarily in PHP and distributed under the GNU GPL.
Installation
Install the phpmyadmin package.
Running
PHP
Make sure the PHP mariadb and iconv
extensions have been enabled.
Optionally you can enable extension=bz2
and extension=zip
for compression support.
Note: If open_basedir
has been set, make sure to include /usr/share/webapps
and /etc/webapps
to open_basedir
in /etc/php/php.ini
. See PHP#Configuration.
Apache
Set up Apache to use PHP as outlined in the Apache HTTP Server#PHP article.
Create the Apache configuration file:
/etc/httpd/conf/extra/phpmyadmin.conf
Alias /phpmyadmin "/usr/share/webapps/phpMyAdmin" <Directory "/usr/share/webapps/phpMyAdmin"> DirectoryIndex index.php AllowOverride All Options FollowSymlinks Require all granted </Directory>
And include it in /etc/httpd/conf/httpd.conf
:
# phpMyAdmin configuration Include conf/extra/phpmyadmin.conf
Note: By default, everyone who can reach the Apache Web Server can see the phpMyAdmin login page under this URL. To change this, edit /etc/httpd/conf/extra/phpmyadmin.conf
to your liking. For example, if you only want to be able to access it from the same machine, replace Require all granted
by Require local
. Beware that this will disallow connecting to PhpMyAdmin on a remote server. If you still want to access PhpMyAdmin on a remote server securely, you might want to consider setting up an OpenSSH#Encrypted SOCKS tunnel.
After making changes to the Apache configuration file, restart httpd.service
.
Lighttpd
Configuring Lighttpd, make sure it is able to serve PHP files and mod_alias
has been enabled.
Add the following alias for PhpMyAdmin to the config:
alias.url = ( "/phpmyadmin" => "/usr/share/webapps/phpMyAdmin/")
Nginx
Make sure to set up nginx#FastCGI and use nginx#Server blocks to make management easier.
By preference, access phpMyAdmin by subdomain, e.g. https://pma.domain.tld
:
/etc/nginx/sites-available/pma.domain.tld
server { server_name pma.domain.tld; ; listen 80; # also listen on http ; listen [::]:80; listen 443 ssl http2; listen [::]:443 ssl http2; index index.php; access_log /var/log/nginx/pma.access.log; error_log /var/log/nginx/pma.error.log; # Allows limiting access to certain client addresses. ; allow 192.168.1.0/24; ; allow my-ip; ; deny all; root /usr/share/webapps/phpMyAdmin; location / { try_files $uri $uri/ =404; } error_page 404 /index.php; location ~ .php$ { try_files $uri $document_root$fastcgi_script_name =404; fastcgi_split_path_info ^(.+.php)(/.*)$; fastcgi_pass unix:/run/php-fpm/php-fpm.sock; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; include fastcgi_params; fastcgi_param HTTP_PROXY ""; fastcgi_param HTTPS on; fastcgi_request_buffering off; } }
Or by subdirectory, e.g. https://domain.tld/phpMyAdmin
:
/etc/nginx/sites-available/domain.tld
server { server_name domain.tld; listen 443 ssl http2; listen [::]:443 ssl http2; index index.php; access_log /var/log/nginx/domain.tld.access.log; error_log /var/log/nginx/domain.tld.error.log; root /srv/http/domain.tld; location / { try_files $uri $uri/ =404; } location /phpMyAdmin { root /usr/share/webapps/phpMyAdmin; } # Deny static files location ~ ^/phpMyAdmin/(README|LICENSE|ChangeLog|DCO)$ { deny all; } # Deny .md files location ~ ^/phpMyAdmin/(.+.md)$ { deny all; } # Deny setup directories location ~ ^/phpMyAdmin/(doc|sql|setup)/ { deny all; } #FastCGI config for phpMyAdmin location ~ /phpMyAdmin/(.+.php)$ { try_files $uri $document_root$fastcgi_script_name =404; fastcgi_split_path_info ^(.+.php)(/.*)$; fastcgi_pass unix:/run/php-fpm/php-fpm.sock; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; include fastcgi_params; fastcgi_param HTTP_PROXY ""; fastcgi_param HTTPS on; fastcgi_request_buffering off; } }
Configuration
The main configuration file is located at /usr/share/webapps/phpMyAdmin/config.inc.php
.
Define a remote MySQL server
If the MySQL server is a remote host, append the following line to the configuration file:
$cfg['Servers'][$i]['host'] = 'example.com';
Using setup script
To allow the usage of the phpMyAdmin setup script (e.g. http://localhost/phpmyadmin/setup), make sure /usr/share/webapps/phpMyAdmin
is writable for the http
user:
# mkdir /usr/share/webapps/phpMyAdmin/config # chown http:http /usr/share/webapps/phpMyAdmin/config # chmod 750 /usr/share/webapps/phpMyAdmin/config
Add blowfish_secret passphrase
It is required to enter a unique 32 characters long string to fully use the blowfish algorithm used by phpMyAdmin, thus preventing the message ERROR: The configuration file now needs a secret passphrase (blowfish_secret):
/usr/share/webapps/phpMyAdmin/config.inc.php
$cfg['blowfish_secret'] = '...';
Enabling Configuration Storage
Extra options such as table linking, change tracking, PDF creation, and bookmarking queries are disabled by default, displaying The phpMyAdmin configuration storage is not completely configured, some extended features have been deactivated. on the homepage.
Note: This example assumes you want to use the default username pma as the controluser
, and pmapass as the controlpass
.
In /usr/share/webapps/phpMyAdmin/config.inc.php
, uncomment (remove the leading «//»s), and change them to your desired credentials if needed:
/usr/share/webapps/phpMyAdmin/config.inc.php
/* User used to manipulate with storage */ // $cfg['Servers'][$i]['controlhost'] = 'my-host'; // $cfg['Servers'][$i]['controlport'] = '3306'; $cfg['Servers'][$i]['controluser'] = 'pma'; $cfg['Servers'][$i]['controlpass'] = 'pmapass'; /* Storage database and tables */ $cfg['Servers'][$i]['pmadb'] = 'phpmyadmin'; $cfg['Servers'][$i]['bookmarktable'] = 'pma__bookmark'; $cfg['Servers'][$i]['relation'] = 'pma__relation'; $cfg['Servers'][$i]['table_info'] = 'pma__table_info'; $cfg['Servers'][$i]['table_coords'] = 'pma__table_coords'; $cfg['Servers'][$i]['pdf_pages'] = 'pma__pdf_pages'; $cfg['Servers'][$i]['column_info'] = 'pma__column_info'; $cfg['Servers'][$i]['history'] = 'pma__history'; $cfg['Servers'][$i]['table_uiprefs'] = 'pma__table_uiprefs'; $cfg['Servers'][$i]['tracking'] = 'pma__tracking'; $cfg['Servers'][$i]['userconfig'] = 'pma__userconfig'; $cfg['Servers'][$i]['recent'] = 'pma__recent'; $cfg['Servers'][$i]['favorite'] = 'pma__favorite'; $cfg['Servers'][$i]['users'] = 'pma__users'; $cfg['Servers'][$i]['usergroups'] = 'pma__usergroups'; $cfg['Servers'][$i]['navigationhiding'] = 'pma__navigationhiding'; $cfg['Servers'][$i]['savedsearches'] = 'pma__savedsearches'; $cfg['Servers'][$i]['central_columns'] = 'pma__central_columns'; $cfg['Servers'][$i]['designer_settings'] = 'pma__designer_settings'; $cfg['Servers'][$i]['export_templates'] = 'pma__export_templates';
Setup database
Two options are available to create the required tables:
- Import
/usr/share/webapps/phpMyAdmin/sql/create_tables.sql
by using PhpMyAdmin. - Execute
mysql -u root -p < /usr/share/webapps/phpMyAdmin/sql/create_tables.sql
in the command line.
Setup database user
To apply the required permissions for controluser
, execute the following query:
Note: Make sure to replace all instances of pma
and pmapass
to the values set in config.inc.php
. If you are setting this up for a remote database, then you must also change localhost
to the proper host.
GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass'; GRANT SELECT ( Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv, Grant_priv, References_priv, Index_priv, Alter_priv, Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv, Execute_priv, Repl_slave_priv, Repl_client_priv ) ON mysql.user TO 'pma'@'localhost'; GRANT SELECT ON mysql.db TO 'pma'@'localhost'; GRANT SELECT ON mysql.host TO 'pma'@'localhost'; GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv) ON mysql.tables_priv TO 'pma'@'localhost';
In order use the bookmark and relation features, set the following permissions:
GRANT SELECT, INSERT, UPDATE, DELETE ON phpmyadmin.* TO 'pma'@'localhost';
Re-login to ensure the new features are activated.
Enabling template caching
Edit /usr/share/webapps/phpMyAdmin/config.inc.php
to add the line:
$cfg['TempDir'] = '/tmp/phpmyadmin';
Remove config directory
Remove temporary configuration directory once configuration is done. This will also suppress warning from web interface:
# rm -r /usr/share/webapps/phpMyAdmin/config
Install themes
Themes are located in /usr/share/webapps/phpMyAdmin/themes
. You can find new themes in https://www.phpmyadmin.net/themes/
You can simply download and extract the new theme and it will work after phpmyadmin refresh. However, you have to download theme for the correct version of phpmyadmin, themes for older versions will not work.
See also
- Official website