diff options
Diffstat (limited to 'srcs/phpmyadmin/doc/html/_sources')
23 files changed, 0 insertions, 10038 deletions
diff --git a/srcs/phpmyadmin/doc/html/_sources/bookmarks.txt b/srcs/phpmyadmin/doc/html/_sources/bookmarks.txt deleted file mode 100644 index 0da9194..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/bookmarks.txt +++ /dev/null @@ -1,77 +0,0 @@ -.. _bookmarks: - -Bookmarks -========= - -.. note:: - - You need to have configured the :ref:`linked-tables` for using bookmarks - feature. - -Storing bookmarks ------------------ - -Any query that is executed can be marked as a bookmark on the page -where the results are displayed. You will find a button labeled -:guilabel:`Bookmark this query` just at the end of the page. As soon as you have -stored a bookmark, that query is linked to the database. -You can now access a bookmark dropdown on each page where the query box appears on for that database. - -Variables inside bookmarks --------------------------- - -Inside a query, you can also add placeholders for variables. -This is done by inserting into the query SQL comments between ``/*`` and -``*/``. The special string ``[VARIABLE{variable-number}]`` is used inside the comments. -Be aware that the whole query minus the SQL comments must be -valid by itself, otherwise you won't be able to store it as a bookmark. -Also, note that the text 'VARIABLE' is case-sensitive. - -When you execute the bookmark, everything typed into the *Variables* -input boxes on the query box page will replace the strings ``/*[VARIABLE{variable-number}]*/`` in -your stored query. - -Also remember, that everything else inside the ``/*[VARIABLE{variable-number}]*/`` string for -your query will remain the way it is, but will be stripped of the ``/**/`` -chars. So you can use: - -.. code-block:: mysql - - /*, [VARIABLE1] AS myname */ - -which will be expanded to - -.. code-block:: mysql - - , VARIABLE1 as myname - -in your query, where VARIABLE1 is the string you entered in the Variable 1 input box. - -A more complex example, say you have stored this query: - -.. code-block:: mysql - - SELECT Name, Address FROM addresses WHERE 1 /* AND Name LIKE '%[VARIABLE1]%' */ - -If you wish to enter "phpMyAdmin" as the variable for the stored query, the full -query will be: - -.. code-block:: mysql - - SELECT Name, Address FROM addresses WHERE 1 AND Name LIKE '%phpMyAdmin%' - -**NOTE THE ABSENCE OF SPACES** inside the ``/**/`` construct. Any spaces -inserted there will be later also inserted as spaces in your query and may lead -to unexpected results especially when using the variable expansion inside of a -"LIKE ''" expression. - -Browsing a table using a bookmark ---------------------------------- - -When a bookmark has the same name as the table, it will be used as the query when browsing -this table. - -.. seealso:: - - :ref:`faqbookmark`, - :ref:`faq6_22` diff --git a/srcs/phpmyadmin/doc/html/_sources/charts.txt b/srcs/phpmyadmin/doc/html/_sources/charts.txt deleted file mode 100644 index 4896d9d..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/charts.txt +++ /dev/null @@ -1,143 +0,0 @@ -.. _charts: - -Charts -====== - -.. versionadded:: 3.4.0 - -Since phpMyAdmin version 3.4.0, you can easily generate charts from a SQL query -by clicking the "Display chart" link in the "Query results operations" area. - -.. image:: images/query_result_operations.png - -A window layer "Display chart" is shown in which you can customize the chart with the following options. - -- Chart type: Allows you to choose the type of chart. Supported types are bar charts, column charts, line charts, spline charts, area charts, pie charts and timeline charts (only the chart types applicable for current series selection are offered). -- X-axis: Allows to choose the field for the main axis. -- Series: Allows to choose series for the chart. You can choose multiple series. -- Title: Allows specifying a title for the chart which is displayed above the chart. -- X-axis and Y-axis labels: Allows specifying labels for axes. -- Start row and a number of rows: Allows generating charts only for a specified number of rows of the results set. - -.. image:: images/chart.png - -Chart implementation --------------------- - -Charts in phpMyAdmin are drawn using `jqPlot <http://www.jqplot.com/>`_ jQuery library. - -Examples --------- - -Pie chart -+++++++++ - -Query results for a simple pie chart can be generated with: - -.. code-block:: mysql - - SELECT 'Food' AS 'expense', - 1250 AS 'amount' UNION - SELECT 'Accommodation', 500 UNION - SELECT 'Travel', 720 UNION - SELECT 'Misc', 220 - -And the result of this query is: - -+---------------+--------+ -| expense | amount | -+===============+========+ -| Food | 1250 | -+---------------+--------+ -| Accommodation | 500 | -+---------------+--------+ -| Travel | 720 | -+---------------+--------+ -| Misc | 220 | -+---------------+--------+ - -Choosing expense as the X-axis and amount in series: - -.. image:: images/pie_chart.png - -Bar and column chart -++++++++++++++++++++ - -Both bar charts and column chats support stacking. Upon selecting one of these types a checkbox is displayed to select stacking. - -Query results for a simple bar or column chart can be generated with: - -.. code-block:: mysql - - SELECT - 'ACADEMY DINOSAUR' AS 'title', - 0.99 AS 'rental_rate', - 20.99 AS 'replacement_cost' UNION - SELECT 'ACE GOLDFINGER', 4.99, 12.99 UNION - SELECT 'ADAPTATION HOLES', 2.99, 18.99 UNION - SELECT 'AFFAIR PREJUDICE', 2.99, 26.99 UNION - SELECT 'AFRICAN EGG', 2.99, 22.99 - -And the result of this query is: - -+------------------+--------------+-------------------+ -| title | rental_rate | replacement_cost | -+==================+==============+===================+ -| ACADEMY DINOSAUR | 0.99 | 20.99 | -+------------------+--------------+-------------------+ -| ACE GOLDFINGER | 4.99 | 12.99 | -+------------------+--------------+-------------------+ -| ADAPTATION HOLES | 2.99 | 18.99 | -+------------------+--------------+-------------------+ -| AFFAIR PREJUDICE | 2.99 | 26.99 | -+------------------+--------------+-------------------+ -| AFRICAN EGG | 2.99 | 22.99 | -+------------------+--------------+-------------------+ - -Choosing title as the X-axis and rental_rate and replacement_cost as series: - -.. image:: images/column_chart.png - -Scatter chart -+++++++++++++ - -Scatter charts are useful in identifying the movement of one or more variable(s) compared to another variable. - -Using the same data set from bar and column charts section and choosing replacement_cost as the X-axis and rental_rate in series: - -.. image:: images/scatter_chart.png - -Line, spline and timeline charts -++++++++++++++++++++++++++++++++ - -These charts can be used to illustrate trends in underlying data. Spline charts draw smooth lines while timeline charts draw X-axis taking the distances between the dates/time into consideration. - -Query results for a simple line, spline or timeline chart can be generated with: - -.. code-block:: mysql - - SELECT - DATE('2006-01-08') AS 'date', - 2056 AS 'revenue', - 1378 AS 'cost' UNION - SELECT DATE('2006-01-09'), 1898, 2301 UNION - SELECT DATE('2006-01-15'), 1560, 600 UNION - SELECT DATE('2006-01-17'), 3457, 1565 - -And the result of this query is: - -+------------+---------+------+ -| date | revenue | cost | -+============+=========+======+ -| 2016-01-08 | 2056 | 1378 | -+------------+---------+------+ -| 2006-01-09 | 1898 | 2301 | -+------------+---------+------+ -| 2006-01-15 | 1560 | 600 | -+------------+---------+------+ -| 2006-01-17 | 3457 | 1565 | -+------------+---------+------+ - -.. image:: images/line_chart.png -.. image:: images/spline_chart.png -.. image:: images/timeline_chart.png diff --git a/srcs/phpmyadmin/doc/html/_sources/config.txt b/srcs/phpmyadmin/doc/html/_sources/config.txt deleted file mode 100644 index 97d7902..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/config.txt +++ /dev/null @@ -1,3609 +0,0 @@ -.. index:: config.inc.php - -.. _config: - -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 in -:file:`libraries/config.default.php` (this file is not inteded for changes). - -.. 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/layout.inc.php`. 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. - -.. warning:: - - :term:`Mac` users should note that if you are on a version before - :term:`Mac OS X`, PHP does not seem to - like :term:`Mac` end of lines character (``\r``). So - ensure you choose the option that allows to use the \*nix end of line - character (``\n``) in your text editor before saving a script you have - modified. - -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'`` - - 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. In - :file:`libraries/config.default.php`, there is only one section for server - definition, however you can put as many 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 - incrementation) serveral 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/5.7/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/5.7/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/5.7/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`, - :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`, - :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`, - :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`, - :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`, - :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`, - :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`, - :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). - -.. _controlhost: -.. 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_*']` - -.. _controlport: -.. 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_*']` - -.. _controluser: -.. 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]['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` - -.. _servers_auth_http_realm: -.. 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. - -.. _servers_user: -.. 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. - -.. _servers_nopassword: -.. 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. - -.. _servers_only_db: -.. 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'] = array('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. - -.. _bookmark: -.. config:option:: $cfg['Servers'][$i]['bookmarktable'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _relation: -.. config:option:: $cfg['Servers'][$i]['relation'] - - :type: string or false - :default: ``''`` - - 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. - -.. _table_info: -.. config:option:: $cfg['Servers'][$i]['table_info'] - - :type: string or false - :default: ``''`` - - 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` - -.. _table_coords: -.. 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: ``''`` - - 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`. - -.. _col_com: -.. config:option:: $cfg['Servers'][$i]['column_info'] - - :type: string or false - :default: ``''`` - - 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/5.7/en/grant.html>`_ on how to - ``GRANT`` privileges to a user. - -.. _history: -.. config:option:: $cfg['Servers'][$i]['history'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _recent: -.. config:option:: $cfg['Servers'][$i]['recent'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _favorite: -.. config:option:: $cfg['Servers'][$i]['favorite'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _table_uiprefs: -.. config:option:: $cfg['Servers'][$i]['table_uiprefs'] - - :type: string or false - :default: ``''`` - - 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: ``''`` - -.. config:option:: $cfg['Servers'][$i]['usergroups'] - - :type: string or false - :default: ``''`` - - 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 he is 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` - -.. _navigationhiding: -.. config:option:: $cfg['Servers'][$i]['navigationhiding'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _central_columns: -.. config:option:: $cfg['Servers'][$i]['central_columns'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _designer_settings: -.. config:option:: $cfg['Servers'][$i]['designer_settings'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _savedsearches: -.. config:option:: $cfg['Servers'][$i]['savedsearches'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _export_templates: -.. config:option:: $cfg['Servers'][$i]['export_templates'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _tracking: -.. config:option:: $cfg['Servers'][$i]['tracking'] - - :type: string or false - :default: ``''`` - - 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``. - -.. _tracking2: -.. 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. - -.. _tracking3: -.. 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. - -.. _tracking4: -.. 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. - -.. _tracking5: -.. 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. - -.. _tracking6: -.. 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. - -.. _userconfig: -.. config:option:: $cfg['Servers'][$i]['userconfig'] - - :type: string or false - :default: ``''`` - - 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/5.7/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. - -.. _servers_allowdeny_order: -.. 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. - -.. _servers_allowdeny_rules: -.. 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'] = 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 - -.. 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. - -Generic settings ----------------- - -.. config:option:: $cfg['DisableShortcutKeys'] - - :type: boolean - :default: false - - You can disable phpMyAdmin shortcut keys by setting :config:option:`$cfg['DisableShortcutKeys']` to false. - -.. 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 :file:`version_check.php`. - - .. 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. Works with - following extensions: - - * mysql (`mysql\_pconnect <https://www.php.net/manual/en/function.mysql- - pconnect.php>`_), - * mysqli (requires PHP 5.3.0 or newer, `more information - <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['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['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. - -Cookie authentication options ------------------------------ - -.. config:option:: $cfg['blowfish_secret'] - - :type: string - :default: ``''`` - - 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. - - .. 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. - -.. 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. - -.. _AllowArbitraryServer: -.. 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 regullar - 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 regullar expression by the suffix, while connecting to another - server. - -.. config:option:: $cfg['CaptchaLoginPublicKey'] - - :type: string - :default: ``''`` - - The public key for the reCaptcha service that can be obtained from - https://www.google.com/recaptcha/intro/v3.html. - - reCaptcha will be then used in :ref:`cookie`. - -.. config:option:: $cfg['CaptchaLoginPrivateKey'] - - :type: string - :default: ``''`` - - The private key for the reCaptcha service that can be obtain from - https://www.google.com/recaptcha/intro/v3.html. - - reCaptcha will be then used in :ref:`cookie`. - -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 :term:`URL` where 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 ``'./sql.php?'``. - For external URLs, you should include URL protocol schemes (``http`` or ``https``) with absolute URLs. - -.. 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``. - -.. 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['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 - :default: true - - Defines whether to display detailed server information on main page. - You can additionally hide more information by using - :config:option:`$cfg['Servers'][$i]['verbose']`. - -.. 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 informations 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['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 "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 "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, "Previous" and - "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['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']['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['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. - -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'] = array('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 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/layout.inc.php`, 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. - -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: 2 - - 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']`). - -.. 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-dirs: - -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['QueryHistoryDB'] - - :type: boolean - :default: false - -.. 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['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 clases under :file:`libraries/classes/Config/Forms/User/`. - -.. config:option:: $cfg['UserprefsDeveloperTab'] - - :type: boolean - :default: false - - Activates in the user preferences a tab containing options for - developers of phpMyAdmin. - -Page titles ------------ - -.. 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@'`` - - Allows you to specify window's title bar. You can use :ref:`faq6_27`. - -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(...) - - 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. - -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['DBG'] - - :type: array - :default: array(...) - -.. 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`. - -.. _config-examples: - -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-signon: - -Example for signon authentication -+++++++++++++++++++++++++++++++++ - -This example uses :file:`examples/signon.php` to demonstrate usage of :ref:`auth_signon`: - -.. code-block:: php - - <?php - $i = 0; - $i++; - $cfg['Servers'][$i]['extension'] = 'mysqli'; - $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: - -.. code-block:: php - - 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: - -.. code-block:: php - - <?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'; - $cfg['Servers'][$i]['extension'] = 'mysqli'; - // 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 - $cfg['Servers'][$i]['extension'] = 'mysqli'; - // more options for #2 ... - - // end of server sections - $cfg['ServerDefault'] = 0; // to choose the server on startup - - // further general options ... - -.. _example-google-ssl: - -Google Cloud SQL with SSL -+++++++++++++++++++++++++ - -To connect to Google Could SQL, you currently need to disable certificate -verification. This is caused by the certficate being issued for CN matching -your instance name, but you connect to an IP address and PHP tries to match -these two. With verfication you end up with error message like: - -.. code-block:: text - - 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: - -.. code-block:: php - - // 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> diff --git a/srcs/phpmyadmin/doc/html/_sources/copyright.txt b/srcs/phpmyadmin/doc/html/_sources/copyright.txt deleted file mode 100644 index ed18723..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/copyright.txt +++ /dev/null @@ -1,42 +0,0 @@ -.. _copyright: - -Copyright -========= - -.. code-block:: none - - Copyright (C) 1998-2000 Tobias Ratschiller <tobias_at_ratschiller.com> - Copyright (C) 2001-2018 Marc Delisle <marc_at_infomarc.info> - Olivier Müller <om_at_omnis.ch> - Robin Johnson <robbat2_at_users.sourceforge.net> - Alexander M. Turek <me_at_derrabus.de> - Michal Čihař <michal_at_cihar.com> - Garvin Hicking <me_at_supergarv.de> - Michael Keck <mkkeck_at_users.sourceforge.net> - Sebastian Mendel <cybot_tm_at_users.sourceforge.net> - [check credits for more details] - -This program is free software; you can redistribute it and/or modify -it under the terms of the GNU General Public License version 2, as -published by the Free Software Foundation. - -This program is distributed in the hope that it will be useful, but -WITHOUT ANY WARRANTY; without even the implied warranty of -MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -General Public License for more details. - -You should have received a copy of the GNU General Public License -along with this program. If not, see <https://www.gnu.org/licenses/>. - -Third party licenses -++++++++++++++++++++ - -phpMyAdmin includes several third-party libraries which come under their -respective licenses. - -jQuery's license, which is where we got the files under js/vendor/jquery/ is -(MIT|GPL), a copy of each license is available in this repository (GPL -is available as LICENSE, MIT as js/vendor/jquery/MIT-LICENSE.txt). - -The download kit additionally includes several composer libraries. See their -licensing information in the vendor/ directory. diff --git a/srcs/phpmyadmin/doc/html/_sources/credits.txt b/srcs/phpmyadmin/doc/html/_sources/credits.txt deleted file mode 100644 index 24d074d..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/credits.txt +++ /dev/null @@ -1,1080 +0,0 @@ -.. _credits: - -Credits -======= - -Credits, in chronological order -+++++++++++++++++++++++++++++++ - -* Tobias Ratschiller <tobias\_at\_ratschiller.com> - - * creator of the phpMyAdmin project - - * maintainer from 1998 to summer 2000 - -* Marc Delisle <marc\_at\_infomarc.info> - - * multi-language version in December 1998 - - * various fixes and improvements - - * first version of the :term:`SQL` analyser (most of it) - - * maintainer from 2001 to 2015 - -* Olivier Müller <om\_at\_omnis.ch> - - * started SourceForge phpMyAdmin project in March 2001 - - * sync'ed different existing CVS trees with new features and bugfixes - - * multi-language improvements, dynamic language selection - - * many bugfixes and improvements - -* Loïc Chapeaux <lolo\_at\_phpheaven.net> - - * rewrote and optimized JavaScript, DHTML and DOM stuff - - * rewrote the scripts so they fit the :term:`PEAR` coding standards and - generate XHTML1.0 and CSS2 compliant codes - - * improved the language detection system - - * many bugfixes and improvements - -* Robin Johnson <robbat2\_at\_users.sourceforge.net> - - * database maintenance controls - - * table type code - - * Host authentication :term:`IP` Allow/Deny - - * DB-based configuration (Not completed) - - * :term:`SQL` parser and pretty-printer - - * :term:`SQL` validator - - * many bugfixes and improvements - -* Armel Fauveau <armel.fauveau\_at\_globalis-ms.com> - - * bookmarks feature - - * multiple dump feature - - * gzip dump feature - - * zip dump feature - -* Geert Lund <glund\_at\_silversoft.dk> - - * various fixes - - * moderator of the phpMyAdmin former users forum at phpwizard.net - -* Korakot Chaovavanich <korakot\_at\_iname.com> - - * "insert as new row" feature - -* Pete Kelly <webmaster\_at\_trafficg.com> - - * rewrote and fix dump code - - * bugfixes - -* Steve Alberty <alberty\_at\_neptunlabs.de> - - * rewrote dump code for PHP4 - - * mySQL table statistics - - * bugfixes - -* Benjamin Gandon <gandon\_at\_isia.cma.fr> - - * main author of the version 2.1.0.1 - - * bugfixes - -* Alexander M. Turek <me\_at\_derrabus.de> - - * MySQL 4.0 / 4.1 / 5.0 compatibility - - * abstract database interface (PMA\_DBI) with MySQLi support - - * privileges administration - - * :term:`XML` exports - - * various features and fixes - - * German language file updates - -* Mike Beck <mike.beck\_at\_web.de> - - * automatic joins in QBE - - * links column in printview - - * Relation view - -* Michal Čihař <michal\_at\_cihar.com> - - * enhanced index creation/display feature - - * feature to use a different charset for HTML than for MySQL - - * improvements of export feature - - * various features and fixes - - * Czech language file updates - - * created current website for phpMyAdmin - -* Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin" - (https://sourceforge.net/projects/phpmysqlformgen/) - - * suggested the patch for multiple table printviews - -* Garvin Hicking <me\_at\_supergarv.de> - - * built the patch for vertical display of table rows - - * built the Javascript based Query window + :term:`SQL` history - - * Improvement of column/db comments - - * (MIME)-Transformations for columns - - * Use custom alias names for Databases in left frame - - * hierarchical/nested table display - - * :term:`PDF`-scratchboard for WYSIWYG- - distribution of :term:`PDF` relations - - * new icon sets - - * vertical display of column properties page - - * some bugfixes, features, support, German language additions - -* Yukihiro Kawada <kawada\_at\_den.fujifilm.co.jp> - - * japanese kanji encoding conversion feature - -* Piotr Roszatycki <d3xter\_at\_users.sourceforge.net> and Dan Wilson - - * the Cookie authentication mode - -* Axel Sander <n8falke\_at\_users.sourceforge.net> - - * table relation-links feature - -* Maxime Delorme <delorme.maxime\_at\_free.fr> - - * :term:`PDF` schema output, thanks also to - Olivier Plathey for the "FPDF" library (see <http://www.fpdf.org/>), Steven - Wittens for the "UFPDF" library and - Nicola Asuni for the "TCPDF" library (see <https://tcpdf.org/>). - -* Olof Edlund <olof.edlund\_at\_upright.se> - - * :term:`SQL` validator server - -* Ivan R. Lanin <ivanlanin\_at\_users.sourceforge.net> - - * phpMyAdmin logo (until June 2004) - -* Mike Cochrane <mike\_at\_graftonhall.co.nz> - - * blowfish library from the Horde project (withdrawn in release 4.0) - -* Marcel Tschopp <ne0x\_at\_users.sourceforge.net> - - * mysqli support - - * many bugfixes and improvements - -* Nicola Asuni (Tecnick.com) - - * TCPDF library (<https://tcpdf.org>) - -* Michael Keck <mkkeck\_at\_users.sourceforge.net> - - * redesign for 2.6.0 - - * phpMyAdmin sailboat logo (June 2004) - -* Mathias Landhäußer - - * Representation at conferences - -* Sebastian Mendel <cybot\_tm\_at\_users.sourceforge.net> - - * interface improvements - - * various bugfixes - -* Ivan A Kirillov - - * new relations Designer - -* Raj Kissu Rajandran (Google Summer of Code 2008) - - * BLOBstreaming support (withdrawn in release 4.0) - -* Piotr Przybylski (Google Summer of Code 2008, 2010 and 2011) - - * improved setup script - - * user preferences - - * Drizzle support - -* Derek Schaefer (Google Summer of Code 2009) - - * Improved the import system - -* Alexander Rutkowski (Google Summer of Code 2009) - - * Tracking mechanism - -* Zahra Naeem (Google Summer of Code 2009) - - * Synchronization feature (removed in release 4.0) - -* Tomáš Srnka (Google Summer of Code 2009) - - * Replication support - -* Muhammad Adnan (Google Summer of Code 2010) - - * Relation schema export to multiple formats - -* Lori Lee (Google Summer of Code 2010) - - * User interface improvements - - * ENUM/SET editor - - * Simplified interface for export/import - -* Ninad Pundalik (Google Summer of Code 2010) - - * AJAXifying the interface - -* Martynas Mickevičius (Google Summer of Code 2010) - - * Charts - -* Barrie Leslie - - * BLOBstreaming support with PBMS PHP extension (withdrawn in release - 4.0) - -* Ankit Gupta (Google Summer of Code 2010) - - * Visual query builder - -* Madhura Jayaratne (Google Summer of Code 2011) - - * OpenGIS support - -* Ammar Yasir (Google Summer of Code 2011) - - * Zoom search - -* Aris Feryanto (Google Summer of Code 2011) - - * Browse-mode improvements - -* Thilanka Kaushalya (Google Summer of Code 2011) - - * AJAXification - -* Tyron Madlener (Google Summer of Code 2011) - - * Query statistics and charts for the status page - -* Zarubin Stas (Google Summer of Code 2011) - - * Automated testing - -* Rouslan Placella (Google Summer of Code 2011 and 2012) - - * Improved support for Stored Routines, Triggers and Events - - * Italian translation updates - - * Removal of frames, new navigation - -* Dieter Adriaenssens - - * Various bugfixes - - * Dutch translation updates - -* Alex Marin (Google Summer of Code 2012) - - * New plugins and properties system - -* Thilina Buddika Abeyrathna (Google Summer of Code 2012) - - * Refactoring - -* Atul Pratap Singh (Google Summer of Code 2012) - - * Refactoring - -* Chanaka Indrajith (Google Summer of Code 2012) - - * Refactoring - -* Yasitha Pandithawatta (Google Summer of Code 2012) - - * Automated testing - -* Jim Wigginton (phpseclib.sourceforge.net) - - * phpseclib - -* Bin Zu (Google Summer of Code 2013) - - * Refactoring - -* Supun Nakandala (Google Summer of Code 2013) - - * Refactoring - -* Mohamed Ashraf (Google Summer of Code 2013) - - * AJAX error reporting - -* Adam Kang (Google Summer of Code 2013) - - * Automated testing - -* Ayush Chaudhary (Google Summer of Code 2013) - - * Automated testing - -* Kasun Chathuranga (Google Summer of Code 2013) - - * Interface improvements - -* Hugues Peccatte - - * Load/save query by example (database search bookmarks) - -* Smita Kumari (Google Summer of Code 2014) - - * Central list of columns - - * Improve table structure (normalization) - -* Ashutosh Dhundhara (Google Summer of Code 2014) - - * Interface improvements - -* Dhananjay Nakrani (Google Summer of Code 2014) - - * PHP error reporting - -* Edward Cheng (Google Summer of Code 2014) - - * SQL Query Console - -* Kankanamge Bimal Yashodha (Google Summer of Code 2014) - - * Refactoring: Designer/schema integration - -* Chirayu Chiripal (Google Summer of Code 2014) - - * Custom field handlers (Input based MIME transformations) - - * Export with table/column name changes - -* Dan Ungureanu (Google Summer of Code 2015) - - * New parser and analyzer - -* Nisarg Jhaveri (Google Summer of Code 2015) - - * Page-related settings - - * SQL debugging integration to the Console - - * Other UI improvements - -* Deven Bansod (Google Summer of Code 2015) - - * Print view using CSS - - * Other UI improvements and new features - -* Deven Bansod (Google Summer of Code 2017) - - * Improvements to the Error Reporting Server - - * Improved Selenium testing - -* Manish Bisht (Google Summer of Code 2017) - - * Mobile user interface - - * Remove inline JavaScript code - - * Other UI improvements - -* Raghuram Vadapalli (Google Summer of Code 2017) - - * Multi-table query interface - - * Allow Designer to work with tables from other databases - - * Other UI improvements - -* Maurício Meneghini Fauth - - * Major improvements and upgrades to the JavaScript core - * Modernize JavaScript library functionality - * Modernize templating and introduce Twig - -* William Desportes - - * Coding style improvements based on PHPStan - * Improve links to external MySQL and MariaDB documentation - * Numerous other bug fixes - -* Emanuel Bronshtein - - * Comprehensive security assessment and suggestions - -* Lakshya Arora (Google Summer of Code 2018) - - * Various improvements including: - - * Integrate user preferences with local storage - * Use a modal login after session expiration - * Add support for CHECK CONSTRAINTS - * and more! - -* Saksham Gupta (Google Summer of Code 2018) - - * Automated theme generator tool - -* Leonardo Strozzi (Google Summer of Code 2018) - - * Refactoring Twig templates and other internal code improvements - -* Piyush Vijay (Google Summer of Code 2018) - - * Modernize the JavaScript code including introducing Webpack, Babel, and Yarn as well as eslint and Jsdoc - -And also to the following people who have contributed minor changes, -enhancements, bugfixes or support for a new language since version -2.1.0: - -Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita, -Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow, Mats -Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger, -Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, -Andreas Pauley, Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval -Sarna, www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, -Peter Svec, Michael Tacelosky, Rachim Tamsjadi, Kositer Uros, Luís V., -Martijn W. van der Lee, Algis Vainauskas, Daniel Villanueva, Vinay, -Ignacio Vazquez-Abrams, Chee Wai, Jakub Wilk, Thomas Michael -Winningham, Vilius Zigmantas, "Manuzhai". - -Translators -+++++++++++ - -Following people have contributed to translation of phpMyAdmin: - -* Albanian - - * Arben Çokaj <acokaj\_at\_shkoder.net> - -* Arabic - - * Ahmed Saleh Abd El-Raouf Ismae <a.saleh.ismael\_at\_gmail.com> - * Ahmed Saad <egbrave\_at\_hotmail.com> - * hassan mokhtari <persiste1\_at\_gmail.com> - -* Armenian - - * Andrey Aleksanyants <aaleksanyants\_at\_yahoo.com> - -* Azerbaijani - - * Mircəlal <01youknowme\_at\_gmail.com> - * Huseyn <huseyn_esgerov\_at\_mail.ru> - * Sevdimali İsa <sevdimaliisayev\_at\_mail.ru> - * Jafar <sharifov\_at\_programmer.net> - -* Belarusian - - * Viktar Palstsiuk <vipals\_at\_gmail.com> - -* Bulgarian - - * Boyan Kehayov <bkehayov\_at\_gmail.com> - * Valter Georgiev <blagynchy\_at\_gmail.com> - * Valentin Mladenov <hudsonvsm\_at\_gmail.com> - * P <plamen_mbx\_at\_yahoo.com> - * krasimir <vip\_at\_krasio-valia.com> - -* Catalan - - * josep constanti <jconstanti\_at\_yahoo.es> - * Xavier Navarro <xvnavarro\_at\_gmail.com> - -* Chinese (China) - - * Vincent Lau <3092849\_at\_qq.com> - * Zheng Dan <clanboy\_at\_163.com> - * disorderman <disorderman\_at\_qq.com> - * Rex Lee <duguying2008\_at\_gmail.com> - * <fundawang\_at\_gmail.com> - * popcorner <memoword\_at\_163.com> - * Yizhou Qiang <qyz.yswy\_at\_hotmail.com> - * zz <tczzjin\_at\_gmail.com> - * Terry Weng <wengshiyu\_at\_gmail.com> - * whh <whhlcj\_at\_126.com> - -* Chinese (Taiwan) - - * Albert Song <albb0920\_at\_gmail.com> - * Chien Wei Lin <cwlin0416\_at\_gmail.com> - * Peter Dave Hello <xs910203\_at\_gmail.com> - -* Colognian - - * Purodha <publi\_at\_web.de> - -* Czech - - * Aleš Hakl <ales\_at\_hakl.net> - * Dalibor Straka <dalibor.straka3\_at\_gmail.com> - * Martin Vidner <martin\_at\_vidner.net> - * Ondra Šimeček <ondrasek.simecek\_at\_gmail.com> - * Jan Palider <palider\_at\_seznam.cz> - * Petr Kateřiňák <petr.katerinak\_at\_gmail.com> - -* Danish - - * Aputsiaĸ Niels Janussen <aj\_at\_isit.gl> - * Dennis Jakobsen <dennis.jakobsen\_at\_gmail.com> - * Jonas <jonas.den.smarte\_at\_gmail.com> - * Claus Svalekjaer <just.my.smtp.server\_at\_gmail.com> - -* Dutch - - * A. Voogt <a.voogt\_at\_hccnet.nl> - * dingo thirteen <dingo13\_at\_gmail.com> - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - * Dieter Adriaenssens <ruleant\_at\_users.sourceforge.net> - * Niko Strijbol <strijbol.niko\_at\_gmail.com> - -* English (United Kingdom) - - * Dries Verschuere <dries.verschuere\_at\_outlook.com> - * Francisco Rocha <j.francisco.o.rocha\_at\_zoho.com> - * Marc Delisle <marc\_at\_infomarc.info> - * Marek Tomaštík <tomastik.m\_at\_gmail.com> - -* Esperanto - - * Eliovir <eliovir\_at\_gmail.com> - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - -* Estonian - - * Kristjan Räts <kristjanrats\_at\_gmail.com> - -* Finnish - - * Juha Remes <jremes\_at\_outlook.com> - * Lari Oesch <lari\_at\_oesch.me> - -* French - - * Marc Delisle <marc\_at\_infomarc.info> - -* Frisian - - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - -* Galician - - * Xosé Calvo <xosecalvo\_at\_gmail.com> - -* German - - * Julian Ladisch <github.com-t3if\_at\_ladisch.de> - * Jan Erik Zassenhaus <jan.zassenhaus\_at\_jgerman.de> - * Lasse Goericke <lasse\_at\_mydom.de> - * Matthias Bluthardt <matthias\_at\_bluthardt.org> - * Michael Koch <michael.koch\_at\_enough.de> - * Ann + J.M. <phpMyAdmin\_at\_ZweiSteinSoft.de> - * <pma\_at\_sebastianmendel.de> - * Phillip Rohmberger <rohmberger\_at\_hotmail.de> - * Hauke Henningsen <sqrt\_at\_entless.org> - -* Greek - - * Παναγιώτης Παπάζογλου <papaz_p\_at\_yahoo.com> - -* Hebrew - - * Moshe Harush <mmh15\_at\_windowslive.com> - * Yaron Shahrabani <sh.yaron\_at\_gmail.com> - * Eyal Visoker <visokereyal\_at\_gmail.com> - -* Hindi - - * Atul Pratap Singh <atulpratapsingh05\_at\_gmail.com> - * Yogeshwar <charanyogeshwar\_at\_gmail.com> - * Deven Bansod <devenbansod.bits\_at\_gmail.com> - * Kushagra Pandey <kushagra4296\_at\_gmail.com> - * Nisarg Jhaveri <nisargjhaveri\_at\_gmail.com> - * Roohan Kazi <roohan_cena\_at\_yahoo.co.in> - * Yugal Pantola <yug.scorpio\_at\_gmail.com> - -* Hungarian - - * Akos Eros <erosakos02\_at\_gmail.com> - * Dániel Tóth <leedermeister\_at\_gmail.com> - * Szász Attila <undernetangel\_at\_gmail.com> - * Balázs Úr <urbalazs\_at\_gmail.com> - -* Indonesian - - * Deky Arifianto <Deky40\_at\_gmail.com> - * Andika Triwidada <andika\_at\_gmail.com> - * Dadan Setia <da2n_s\_at\_yahoo.co.id> - * Dadan Setia <dadan.setia\_at\_gmail.com> - * Yohanes Edwin <edwin\_at\_yohanesedwin.com> - * Fadhiil Rachman <fadhiilrachman\_at\_gmail.com> - * Benny <tarzq28\_at\_gmail.com> - * Tommy Surbakti <tommy\_at\_surbakti.net> - * Zufar Fathi Suhardi <zufar.bogor\_at\_gmail.com> - -* Interlingua - - * Giovanni Sora <g.sora\_at\_tiscali.it> - -* Italian - - * Francesco Saverio Giacobazzi <francesco.giacobazzi\_at\_ferrania.it> - * Marco Pozzato <ironpotts\_at\_gmail.com> - * Stefano Martinelli <stefano.ste.martinelli\_at\_gmail.com> - -* Japanese - - * k725 <alexalex.kobayashi\_at\_gmail.com> - * Hiroshi Chiyokawa <hiroshi.chiyokawa\_at\_gmail.com> - * Masahiko HISAKAWA <orzkun\_at\_ageage.jp> - * worldwideskier <worldwideskier\_at\_yahoo.co.jp> - -* Kannada - - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - * Shameem Ahmed A Mulla <shameem.sam\_at\_gmail.com> - -* Korean - - * Bumsoo Kim <bskim45\_at\_gmail.com> - * Kyeong Su Shin <cdac1234\_at\_gmail.com> - * Dongyoung Kim <dckyoung\_at\_gmail.com> - * Myung-han Yu <greatymh\_at\_gmail.com> - * JongDeok <human.zion\_at\_gmail.com> - * Yong Kim <kim\_at\_nhn.com> - * 이경준 <kyungjun2\_at\_gmail.com> - * Seongki Shin <skshin\_at\_gmail.com> - * Yoon Bum-Jong <virusyoon\_at\_gmail.com> - * Koo Youngmin <youngminz.kr\_at\_gmail.com> - -* Kurdish Sorani - - * Alan Hilal <alan.hilal94\_at\_gmail.com> - * Aso Naderi <aso.naderi\_at\_gmail.com> - * muhammad <esy_vb\_at\_yahoo.com> - * Zrng Abdulla <zhyarabdulla94\_at\_gmail.com> - -* Latvian - - * Latvian TV <dnighttv\_at\_gmail.com> - * Edgars Neimanis <edgarsneims5092\_at\_inbox.lv> - * Ukko <perkontevs\_at\_gmail.com> - -* Limburgish - - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - -* Lithuanian - - * Vytautas Motuzas <v.motuzas\_at\_gmail.com> - -* Malay - - * Amir Hamzah <amir.overlord666\_at\_gmail.com> - * diprofinfiniti <anonynuine-999\_at\_yahoo.com> - -* Nepali - - * Nabin Ghimire <nnabinn\_at\_hotmail.com> - -* Norwegian Bokmål - - * Børge Holm-Wennberg <borge947\_at\_gmail.com> - * Tor Stokkan <danorse\_at\_gmail.com> - * Espen Frøyshov <efroys\_at\_gmail.com> - * Kurt Eilertsen <kurt\_at\_kheds.com> - * Christoffer Haugom <ph3n1x.nobody\_at\_gmail.com> - * Sebastian <sebastian\_at\_sgundersen.com> - * Tomas <tomas\_at\_tomasruud.com> - -* Persian - - * ashkan shirian <ashkan.shirian\_at\_gmail.com> - * HM <goodlinuxuser\_at\_chmail.ir> - -* Polish - - * Andrzej <andrzej\_at\_kynu.pl> - * Przemo <info\_at\_opsbielany.waw.pl> - * Krystian Biesaga <krystian4842\_at\_gmail.com> - * Maciej Gryniuk <maciejka45\_at\_gmail.com> - * Michał VonFlynee <vonflynee\_at\_gmail.com> - -* Portuguese - - * Alexandre Badalo <alexandre.badalo\_at\_sapo.pt> - * João Rodrigues <geral\_at\_jonilive.com> - * Pedro Ribeiro <p.m42.ribeiro\_at\_gmail.com> - * Sandro Amaral <sandro123iv\_at\_gmail.com> - -* Portuguese (Brazil) - - * Alex Rohleder <alexrohleder96\_at\_outlook.com> - * bruno mendax <brunomendax\_at\_gmail.com> - * Danilo GUia <danilo.eng\_at\_globomail.com> - * Douglas Rafael Morais Kollar <douglas.kollar\_at\_pg.df.gov.br> - * Douglas Eccker <douglaseccker\_at\_hotmail.com> - * Ed Jr <edjacobjunior\_at\_gmail.com> - * Guilherme Souza Silva <g.szsilva\_at\_gmail.com> - * Guilherme Seibt <gui\_at\_webseibt.net> - * Helder Santana <helder.bs.santana\_at\_gmail.com> - * Junior Zancan <jrzancan\_at\_hotmail.com> - * Luis <luis.eduardo.braschi\_at\_outlook.com> - * Marcos Algeri <malgeri\_at\_gmail.com> - * Marc Delisle <marc\_at\_infomarc.info> - * Renato Rodrigues de Lima Júnio <renatomdd\_at\_yahoo.com.br> - * Thiago Casotti <thiago.casotti\_at\_uol.com.br> - * Victor Laureano <victor.laureano\_at\_gmail.com> - * Vinícius Araújo <vinipitta\_at\_gmail.com> - * Washington Bruno Rodrigues Cav <washingtonbruno\_at\_msn.com> - * Yan Gabriel <yansilvagabriel\_at\_gmail.com> - -* Punjabi - - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - -* Romanian - - * Alex <amihaita\_at\_yahoo.com> - * Costel Cocerhan <costa1988sv\_at\_gmail.com> - * Ion Adrian-Ionut <john\_at\_panevo.ro> - * Raul Molnar <molnar.raul\_at\_wservices.eu> - * Deleted User <noreply\_at\_weblate.org> - * Stefan Murariu <stefan.murariu\_at\_yahoo.com> - -* Russian - - * Andrey Aleksanyants <aaleksanyants\_at\_yahoo.com> - * <ddrmoscow\_at\_gmail.com> - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - * Хомутов Иван Сергеевич <khomutov.ivan\_at\_mail.ru> - * Alexey Rubinov <orion1979\_at\_yandex.ru> - * Олег Карпов <salvadoporjc\_at\_gmail.com> - * Egorov Artyom <unlucky\_at\_inbox.ru> - -* Serbian - - * Smart Kid <kidsmart33\_at\_gmail.com> - -* Sinhala - - * Madhura Jayaratne <madhura.cj\_at\_gmail.com> - -* Slovak - - * Martin Lacina <martin\_at\_whistler.sk> - * Patrik Kollmann <parkourpotex\_at\_gmail.com> - * Jozef Pistej <pistej2\_at\_gmail.com> - -* Slovenian - - * Domen <mitenem\_at\_outlook.com> - -* Spanish - - * Luis García Sevillano <floss.dev\_at\_gmail.com> - * Franco <fulanodetal.github1\_at\_openaliasbox.org> - * Luis Ruiz <luisan00\_at\_hotmail.com> - * Macofe <macofe.languagetool\_at\_gmail.com> - * Matías Bellone <matiasbellone+weblate\_at\_gmail.com> - * Rodrigo A. <ra4\_at\_openmailbox.org> - * FAMMA TV NOTICIAS MEDIOS DE CO <revistafammatvmusic.oficial\_at\_gmail.com> - * Ronnie Simon <ronniesimonf\_at\_gmail.com> - -* Swedish - - * Anders Jonsson <anders.jonsson\_at\_norsjovallen.se> - -* Tamil - - * கணேஷ் குமார் <GANESHTHEONE\_at\_gmail.com> - * Achchuthan Yogarajah <achch1990\_at\_gmail.com> - * Rifthy Ahmed <rifthy456\_at\_gmail.com> - -* Thai - - * <nontawat39\_at\_gmail.com> - * Somthanat W. <somthanat\_at\_gmail.com> - -* Turkish - - * Burak Yavuz <hitowerdigit\_at\_hotmail.com> - -* Ukrainian - - * Сергій Педько <nitrotoll\_at\_gmail.com> - * Igor <vmta\_at\_yahoo.com> - * Vitaliy Perekupka <vperekupka\_at\_gmail.com> - -* Vietnamese - - * Bao Phan <baophan94\_at\_icloud.com> - * Xuan Hung <mr.hungdx\_at\_gmail.com> - * Bao trinh minh <trinhminhbao\_at\_gmail.com> - -* West Flemish - - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - -Documentation translators -+++++++++++++++++++++++++ - -Following people have contributed to translation of phpMyAdmin documentation: - -* Albanian - - * Arben Çokaj <acokaj\_at\_shkoder.net> - -* Arabic - - * Ahmed El Azzabi <ahmedtek1993\_at\_gmail.com> - * Omar Essam <omar_2412\_at\_live.com> - -* Armenian - - * Andrey Aleksanyants <aaleksanyants\_at\_yahoo.com> - -* Azerbaijani - - * Mircəlal <01youknowme\_at\_gmail.com> - * Sevdimali İsa <sevdimaliisayev\_at\_mail.ru> - -* Catalan - - * josep constanti <jconstanti\_at\_yahoo.es> - * Joan Montané <joan\_at\_montane.cat> - * Xavier Navarro <xvnavarro\_at\_gmail.com> - -* Chinese (China) - - * Vincent Lau <3092849\_at\_qq.com> - * 罗攀登 <6375lpd\_at\_gmail.com> - * disorderman <disorderman\_at\_qq.com> - * ITXiaoPang <djh1017555\_at\_126.com> - * tunnel213 <tunnel213\_at\_aliyun.com> - * Terry Weng <wengshiyu\_at\_gmail.com> - * whh <whhlcj\_at\_126.com> - -* Chinese (Taiwan) - - * Chien Wei Lin <cwlin0416\_at\_gmail.com> - * Peter Dave Hello <xs910203\_at\_gmail.com> - -* Czech - - * Aleš Hakl <ales\_at\_hakl.net> - * Michal Čihař <michal\_at\_cihar.com> - * Jan Palider <palider\_at\_seznam.cz> - * Petr Kateřiňák <petr.katerinak\_at\_gmail.com> - -* Danish - - * Aputsiaĸ Niels Janussen <aj\_at\_isit.gl> - * Claus Svalekjaer <just.my.smtp.server\_at\_gmail.com> - -* Dutch - - * A. Voogt <a.voogt\_at\_hccnet.nl> - * dingo thirteen <dingo13\_at\_gmail.com> - * Dries Verschuere <dries.verschuere\_at\_outlook.com> - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - * Stefan Koolen <nast3zz\_at\_gmail.com> - * Ray Borggreve <ray\_at\_datahuis.net> - * Dieter Adriaenssens <ruleant\_at\_users.sourceforge.net> - * Tom Hofman <tom.hofman\_at\_gmail.com> - -* Estonian - - * Kristjan Räts <kristjanrats\_at\_gmail.com> - -* Finnish - - * Juha <jremes\_at\_outlook.com> - -* French - - * Cédric Corazza <cedric.corazza\_at\_wanadoo.fr> - * Étienne Gilli <etienne.gilli\_at\_gmail.com> - * Marc Delisle <marc\_at\_infomarc.info> - * Donavan_Martin <mart.donavan\_at\_hotmail.com> - -* Frisian - - * Robin van der Vliet <info\_at\_robinvandervliet.nl> - -* Galician - - * Xosé Calvo <xosecalvo\_at\_gmail.com> - -* German - - * Daniel <d.gnauk89\_at\_googlemail.com> - * JH M <janhenrikm\_at\_yahoo.de> - * Lasse Goericke <lasse\_at\_mydom.de> - * Michael Koch <michael.koch\_at\_enough.de> - * Ann + J.M. <phpMyAdmin\_at\_ZweiSteinSoft.de> - * Niemand Jedermann <predatorix\_at\_web.de> - * Phillip Rohmberger <rohmberger\_at\_hotmail.de> - * Hauke Henningsen <sqrt\_at\_entless.org> - -* Greek - - * Παναγιώτης Παπάζογλου <papaz_p\_at\_yahoo.com> - -* Hungarian - - * Balázs Úr <urbalazs\_at\_gmail.com> - -* Italian - - * Francesco Saverio Giacobazzi <francesco.giacobazzi\_at\_ferrania.it> - * Marco Pozzato <ironpotts\_at\_gmail.com> - * Stefano Martinelli <stefano.ste.martinelli\_at\_gmail.com> - * TWS <tablettws\_at\_gmail.com> - -* Japanese - - * Eshin Kunishima <ek\_at\_luna.miko.im> - * Hiroshi Chiyokawa <hiroshi.chiyokawa\_at\_gmail.com> - -* Lithuanian - - * Jur Kis <atvejis\_at\_gmail.com> - * Dovydas <dovy.buz\_at\_gmail.com> - -* Norwegian Bokmål - - * Tor Stokkan <danorse\_at\_gmail.com> - * Kurt Eilertsen <kurt\_at\_kheds.com> - -* Portuguese (Brazil) - - * Alexandre Moretti <alemoretti2010\_at\_hotmail.com> - * Douglas Rafael Morais Kollar <douglas.kollar\_at\_pg.df.gov.br> - * Guilherme Seibt <gui\_at\_webseibt.net> - * Helder Santana <helder.bs.santana\_at\_gmail.com> - * Michal Čihař <michal\_at\_cihar.com> - * Michel Souza <michel.ekio\_at\_gmail.com> - * Danilo Azevedo <mrdaniloazevedo\_at\_gmail.com> - * Thiago Casotti <thiago.casotti\_at\_uol.com.br> - * Vinícius Araújo <vinipitta\_at\_gmail.com> - * Yan Gabriel <yansilvagabriel\_at\_gmail.com> - -* Slovak - - * Martin Lacina <martin\_at\_whistler.sk> - * Michal Čihař <michal\_at\_cihar.com> - * Jozef Pistej <pistej2\_at\_gmail.com> - -* Slovenian - - * Domen <mitenem\_at\_outlook.com> - -* Spanish - - * Luis García Sevillano <floss.dev\_at\_gmail.com> - * Franco <fulanodetal.github1\_at\_openaliasbox.org> - * Matías Bellone <matiasbellone+weblate\_at\_gmail.com> - * Ronnie Simon <ronniesimonf\_at\_gmail.com> - -* Turkish - - * Burak Yavuz <hitowerdigit\_at\_hotmail.com> - -Original Credits of Version 2.1.0 -+++++++++++++++++++++++++++++++++ - -This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his -idea to create a web-based interface to MySQL using PHP3. Although I -have not used any of his source-code, there are some concepts I've -borrowed from him. phpMyAdmin was created because Peter told me he -wasn't going to further develop his (great) tool. - -Thanks go to - -* Amalesh Kempf <ak-lsml\_at\_living-source.com> who contributed the - code for the check when dropping a table or database. He also - suggested that you should be able to specify the primary key on - tbl\_create.php3. To version 1.1.1 he contributed the ldi\_\*.php3-set - (Import text-files) as well as a bug-report. Plus many smaller - improvements. -* Jan Legenhausen <jan\_at\_nrw.net>: He made many of the changes that - were introduced in 1.3.0 (including quite significant ones like the - authentication). For 1.4.1 he enhanced the table-dump feature. Plus - bug-fixes and help. -* Marc Delisle <DelislMa\_at\_CollegeSherbrooke.qc.ca> made phpMyAdmin - language-independent by outsourcing the strings to a separate file. He - also contributed the French translation. -* Alexandr Bravo <abravo\_at\_hq.admiral.ru> who contributed - tbl\_select.php3, a feature to display only some columns from a table. -* Chris Jackson <chrisj\_at\_ctel.net> added support for MySQL functions - in tbl\_change.php3. He also added the "Query by Example" feature in - 2.0. -* Dave Walton <walton\_at\_nordicdms.com> added support for multiple - servers and is a regular contributor for bug-fixes. -* Gabriel Ash <ga244\_at\_is8.nyu.edu> contributed the random access - features for 2.0.6. - -The following people have contributed minor changes, enhancements, -bugfixes or support for a new language: - -Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas -Kleemann, Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel -Piankov, Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, -Jannis Hermanns, G. Wieggers. - -And thanks to everyone else who sent me email with suggestions, bug- -reports and or just some feedback. diff --git a/srcs/phpmyadmin/doc/html/_sources/developers.txt b/srcs/phpmyadmin/doc/html/_sources/developers.txt deleted file mode 100644 index 2b2f586..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/developers.txt +++ /dev/null @@ -1,12 +0,0 @@ -.. _developers: - -Developers Information -====================== - -phpMyAdmin is Open Source, so you're invited to contribute to it. Many -great features have been written by other people and you too can help -to make phpMyAdmin a useful tool. - -You can check out all the possibilities to contribute in the -`contribute section on our website -<https://www.phpmyadmin.net/contribute/>`_. diff --git a/srcs/phpmyadmin/doc/html/_sources/faq.txt b/srcs/phpmyadmin/doc/html/_sources/faq.txt deleted file mode 100644 index fbd1cc6..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/faq.txt +++ /dev/null @@ -1,2290 +0,0 @@ -.. _faq: - -FAQ - Frequently Asked Questions -================================ - -Please have a look at our `Link section -<https://www.phpmyadmin.net/docs/>`_ on the official -phpMyAdmin homepage for in-depth coverage of phpMyAdmin's features and -or interface. - -.. _faqserver: - -Server -++++++ - -.. _faq1_1: - -1.1 My server is crashing each time a specific action is required or phpMyAdmin sends a blank page or a page full of cryptic characters to my browser, what can I do? ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- - -Try to set the :config:option:`$cfg['OBGzip']` directive to ``false`` in your -:file:`config.inc.php` file and the ``zlib.output_compression`` directive to -``Off`` in your php configuration file. - -.. _faq1_2: - -1.2 My Apache server crashes when using phpMyAdmin. ---------------------------------------------------- - -You should first try the latest versions of Apache (and possibly MySQL). If -your server keeps crashing, please ask for help in the various Apache support -groups. - -.. seealso:: :ref:`faq1_1` - -.. _faq1_3: - -1.3 (withdrawn). ----------------- - -.. _faq1_4: - -1.4 Using phpMyAdmin on IIS, I'm displayed the error message: "The specified CGI application misbehaved by not returning a complete set of HTTP headers ...". -------------------------------------------------------------------------------------------------------------------------------------------------------------- - -You just forgot to read the *install.txt* file from the PHP -distribution. Have a look at the last message in this `PHP bug report #12061 -<https://bugs.php.net/bug.php?id=12061>`_ from the official PHP bug -database. - -.. _faq1_5: - -1.5 Using phpMyAdmin on IIS, I'm facing crashes and/or many error messages with the HTTP. ------------------------------------------------------------------------------------------ - -This is a known problem with the PHP :term:`ISAPI` filter: it's not so stable. -Please use instead the cookie authentication mode. - -.. _faq1_6: - -1.6 I can't use phpMyAdmin on PWS: nothing is displayed! --------------------------------------------------------- - -This seems to be a PWS bug. Filippo Simoncini found a workaround (at -this time there is no better fix): remove or comment the ``DOCTYPE`` -declarations (2 lines) from the scripts :file:`libraries/Header.class.php` -and :file:`index.php`. - -.. _faq1_7: - -1.7 How can I gzip a dump or a CSV export? It does not seem to work. --------------------------------------------------------------------- - -This feature is based on the ``gzencode()`` -PHP function to be more independent of the platform (Unix/Windows, -Safe Mode or not, and so on). So, you must have Zlib support -(``--with-zlib``). - -.. _faq1_8: - -1.8 I cannot insert a text file in a table, and I get an error about safe mode being in effect. ------------------------------------------------------------------------------------------------ - -Your uploaded file is saved by PHP in the "upload dir", as defined in -:file:`php.ini` by the variable ``upload_tmp_dir`` (usually the system -default is */tmp*). We recommend the following setup for Apache -servers running in safe mode, to enable uploads of files while being -reasonably secure: - -* create a separate directory for uploads: :command:`mkdir /tmp/php` -* give ownership to the Apache server's user.group: :command:`chown - apache.apache /tmp/php` -* give proper permission: :command:`chmod 600 /tmp/php` -* put ``upload_tmp_dir = /tmp/php`` in :file:`php.ini` -* restart Apache - -.. _faq1_9: - -1.9 (withdrawn). ----------------- - -.. _faq1_10: - -1.10 I'm having troubles when uploading files with phpMyAdmin running on a secure server. My browser is Internet Explorer and I'm using the Apache server. ----------------------------------------------------------------------------------------------------------------------------------------------------------- - -As suggested by "Rob M" in the phpWizard forum, add this line to your -*httpd.conf*: - -.. code-block:: apache - - SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown - -It seems to clear up many problems between Internet Explorer and SSL. - -.. _faq1_11: - -1.11 I get an 'open\_basedir restriction' while uploading a file from the import tab. -------------------------------------------------------------------------------------- - -Since version 2.2.4, phpMyAdmin supports servers with open\_basedir -restrictions. However you need to create temporary directory and configure it -as :config:option:`$cfg['TempDir']`. The uploaded files will be moved there, -and after execution of your :term:`SQL` commands, removed. - -.. _faq1_12: - -1.12 I have lost my MySQL root password, what can I do? -------------------------------------------------------- - -phpMyAdmin does authenticate against MySQL server you're using, so to recover -from phpMyAdmin password loss, you need to recover at MySQL level. - -The MySQL manual explains how to `reset the permissions -<https://dev.mysql.com/doc/refman/5.7/en/resetting-permissions.html>`_. - -If you are using MySQL server installed by your hosting provider, please -contact their support to recover the password for you. - -.. _faq1_13: - -1.13 (withdrawn). ------------------ - -.. _faq1_14: - -1.14 (withdrawn). ------------------ - -.. _faq1_15: - -1.15 I have problems with *mysql.user* column names. ----------------------------------------------------- - -In previous MySQL versions, the ``User`` and ``Password`` columns were -named ``user`` and ``password``. Please modify your column names to -align with current standards. - -.. _faq1_16: - -1.16 I cannot upload big dump files (memory, HTTP or timeout problems). ------------------------------------------------------------------------ - -Starting with version 2.7.0, the import engine has been re–written and -these problems should not occur. If possible, upgrade your phpMyAdmin -to the latest version to take advantage of the new import features. - -The first things to check (or ask your host provider to check) are the values -of ``max_execution_time``, ``upload_max_filesize``, ``memory_limit`` and -``post_max_size`` in the :file:`php.ini` configuration file. All of these -settings limit the maximum size of data that can be submitted and handled by -PHP. Please note that ``post_max_size`` needs to be larger than -``upload_max_filesize``. There exist several workarounds if your upload is too -big or your hosting provider is unwilling to change the settings: - -* Look at the :config:option:`$cfg['UploadDir']` feature. This allows one to upload a file to the server - via scp, FTP, or your favorite file transfer method. PhpMyAdmin is - then able to import the files from the temporary directory. More - information is available in the :ref:`config` of this document. -* Using a utility (such as `BigDump - <https://www.ozerov.de/bigdump/>`_) to split the files before - uploading. We cannot support this or any third party applications, but - are aware of users having success with it. -* If you have shell (command line) access, use MySQL to import the files - directly. You can do this by issuing the "source" command from within - MySQL: - - .. code-block:: mysql - - source filename.sql; - -.. _faq1_17: - -1.17 Which Database versions does phpMyAdmin support? ------------------------------------------------------ - -For `MySQL <https://www.mysql.com/>`_, versions 5.5 and newer are supported. -For older MySQL versions, our `Downloads <https://www.phpmyadmin.net/downloads/>`_ page offers older phpMyAdmin versions -(which may have become unsupported). - -For `MariaDB <https://mariadb.org/>`_, versions 5.5 and newer are supported. - -.. _faq1_17a: - -1.17a I cannot connect to the MySQL server. It always returns the error message, "Client does not support authentication protocol requested by server; consider upgrading MySQL client" ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- - -You tried to access MySQL with an old MySQL client library. The -version of your MySQL client library can be checked in your phpinfo() -output. In general, it should have at least the same minor version as -your server - as mentioned in :ref:`faq1_17`. This problem is -generally caused by using MySQL version 4.1 or newer. MySQL changed -the authentication hash and your PHP is trying to use the old method. -The proper solution is to use the `mysqli extension -<https://www.php.net/mysqli>`_ with the proper client library to match -your MySQL installation. More -information (and several workarounds) are located in the `MySQL -Documentation <https://dev.mysql.com/doc/refman/5.7/en/common-errors.html>`_. - -.. _faq1_18: - -1.18 (withdrawn). ------------------ - -.. _faq1_19: - -1.19 I can't run the "display relations" feature because the script seems not to know the font face I'm using! --------------------------------------------------------------------------------------------------------------- - -The :term:`TCPDF` library we're using for this feature requires some special -files to use font faces. Please refers to the `TCPDF manual -<https://tcpdf.org/>`_ to build these files. - -.. _faqmysql: - -1.20 I receive an error about missing mysqli and mysql extensions. ------------------------------------------------------------------- - -To connect to a MySQL server, PHP needs a set of MySQL functions -called "MySQL extension". This extension may be part of the PHP -distribution (compiled-in), otherwise it needs to be loaded -dynamically. Its name is probably *mysqli.so* or *php\_mysqli.dll*. -phpMyAdmin tried to load the extension but failed. Usually, the -problem is solved by installing a software package called "PHP-MySQL" -or something similar. - -There are currently two interfaces PHP provides as MySQL extensions - ``mysql`` -and ``mysqli``. The ``mysqli`` is tried first, because it's the best one. - -This problem can be also caused by wrong paths in the :file:`php.ini` or using -wrong :file:`php.ini`. - -Make sure that the extension files do exist in the folder which the -``extension_dir`` points to and that the corresponding lines in your -:file:`php.ini` are not commented out (you can use ``phpinfo()`` to check -current setup): - -.. code-block:: ini - - [PHP] - - ; Directory in which the loadable extensions (modules) reside. - extension_dir = "C:/Apache2/modules/php/ext" - -The :file:`php.ini` can be loaded from several locations (especially on -Windows), so please check you're updating the correct one. If using Apache, you -can tell it to use specific path for this file using ``PHPIniDir`` directive: - -.. code-block:: apache - - LoadFile "C:/php/php5ts.dll" - LoadModule php5_module "C:/php/php5apache2_2.dll" - <IfModule php5_module> - PHPIniDir "C:/PHP" - <Location> - AddType text/html .php - AddHandler application/x-httpd-php .php - </Location> - </IfModule> - -In some rare cases this problem can be also caused by other extensions loaded -in PHP which prevent MySQL extensions to be loaded. If anything else fails, you -can try commenting out extensions for other databses from :file:`php.ini`. - -.. _faq1_21: - -1.21 I am running the CGI version of PHP under Unix, and I cannot log in using cookie auth. -------------------------------------------------------------------------------------------- - -In :file:`php.ini`, set ``mysql.max_links`` higher than 1. - -.. _faq1_22: - -1.22 I don't see the "Location of text file" field, so I cannot upload. ------------------------------------------------------------------------ - -This is most likely because in :file:`php.ini`, your ``file_uploads`` -parameter is not set to "on". - -.. _faq1_23: - -1.23 I'm running MySQL on a Win32 machine. Each time I create a new table the table and column names are changed to lowercase! ------------------------------------------------------------------------------------------------------------------------------- - -This happens because the MySQL directive ``lower_case_table_names`` -defaults to 1 (``ON``) in the Win32 version of MySQL. You can change -this behavior by simply changing the directive to 0 (``OFF``): Just -edit your ``my.ini`` file that should be located in your Windows -directory and add the following line to the group [mysqld]: - -.. code-block:: ini - - set-variable = lower_case_table_names=0 - -.. note:: - - Forcing this variable to 0 with --lower-case-table-names=0 on a - case-insensitive filesystem and access MyISAM tablenames using different - lettercases, index corruption may result. - -Next, save the file and restart the MySQL service. You can always -check the value of this directive using the query - -.. code-block:: mysql - - SHOW VARIABLES LIKE 'lower_case_table_names'; - -.. seealso:: `Identifier Case Sensitivity in the MySQL Reference Manual <https://dev.mysql.com/doc/refman/5.7/en/identifier-case-sensitivity.html>`_ - -.. _faq1_24: - -1.24 (withdrawn). ------------------ - -.. _faq1_25: - -1.25 I am running Apache with mod\_gzip-1.3.26.1a on Windows XP, and I get problems, such as undefined variables when I run a SQL query. ----------------------------------------------------------------------------------------------------------------------------------------- - -A tip from Jose Fandos: put a comment on the following two lines in -httpd.conf, like this: - -.. code-block:: apache - - # mod_gzip_item_include file \.php$ - # mod_gzip_item_include mime "application/x-httpd-php.*" - -as this version of mod\_gzip on Apache (Windows) has problems handling -PHP scripts. Of course you have to restart Apache. - -.. _faq1_26: - -1.26 I just installed phpMyAdmin in my document root of IIS but I get the error "No input file specified" when trying to run phpMyAdmin. ----------------------------------------------------------------------------------------------------------------------------------------- - -This is a permission problem. Right-click on the phpmyadmin folder and -choose properties. Under the tab Security, click on "Add" and select -the user "IUSR\_machine" from the list. Now set his permissions and it -should work. - -.. _faq1_27: - -1.27 I get empty page when I want to view huge page (eg. db\_structure.php with plenty of tables). --------------------------------------------------------------------------------------------------- - -This was caused by a `PHP bug <https://bugs.php.net/bug.php?id=21079>`_ that occur when -GZIP output buffering is enabled. If you turn off it (by -:config:option:`$cfg['OBGzip']` in :file:`config.inc.php`), it should work. -This bug will has been fixed in PHP 5.0.0. - -.. _faq1_28: - -1.28 My MySQL server sometimes refuses queries and returns the message 'Errorcode: 13'. What does this mean? ------------------------------------------------------------------------------------------------------------- - -This can happen due to a MySQL bug when having database / table names -with upper case characters although ``lower_case_table_names`` is -set to 1. To fix this, turn off this directive, convert all database -and table names to lower case and turn it on again. Alternatively, -there's a bug-fix available starting with MySQL 3.23.56 / -4.0.11-gamma. - -.. _faq1_29: - -1.29 When I create a table or modify a column, I get an error and the columns are duplicated. ---------------------------------------------------------------------------------------------- - -It is possible to configure Apache in such a way that PHP has problems -interpreting .php files. - -The problems occur when two different (and conflicting) set of -directives are used: - -.. code-block:: apache - - SetOutputFilter PHP - SetInputFilter PHP - -and - -.. code-block:: apache - - AddType application/x-httpd-php .php - -In the case we saw, one set of directives was in -``/etc/httpd/conf/httpd.conf``, while the other set was in -``/etc/httpd/conf/addon-modules/php.conf``. The recommended way is -with ``AddType``, so just comment out the first set of lines and -restart Apache: - -.. code-block:: apache - - #SetOutputFilter PHP - #SetInputFilter PHP - -.. _faq1_30: - -1.30 I get the error "navigation.php: Missing hash". ----------------------------------------------------- - -This problem is known to happen when the server is running Turck -MMCache but upgrading MMCache to version 2.3.21 solves the problem. - -.. _faq1_31: - -1.31 Which PHP versions does phpMyAdmin support? ------------------------------------------------- - -Since release 4.5, phpMyAdmin supports only PHP 5.5 and newer. Since release -4.1 phpMyAdmin supports only PHP 5.3 and newer. For PHP 5.2 you can use 4.0.x -releases. - -PHP 7 is supported since phpMyAdmin 4.6, PHP 7.1 is supported since 4.6.5, -PHP 7.2 is supported since 4.7.4. - -HHVM is supported up to phpMyAdmin 4.8. - -Since release 5.0, phpMyAdmin supports only PHP 7.1 and newer. - -.. _faq1_32: - -1.32 Can I use HTTP authentication with IIS? --------------------------------------------- - -Yes. This procedure was tested with phpMyAdmin 2.6.1, PHP 4.3.9 in -:term:`ISAPI` mode under :term:`IIS` 5.1. - -#. In your :file:`php.ini` file, set ``cgi.rfc2616_headers = 0`` -#. In ``Web Site Properties -> File/Directory Security -> Anonymous - Access`` dialog box, check the ``Anonymous access`` checkbox and - uncheck any other checkboxes (i.e. uncheck ``Basic authentication``, - ``Integrated Windows authentication``, and ``Digest`` if it's - enabled.) Click ``OK``. -#. In ``Custom Errors``, select the range of ``401;1`` through ``401;5`` - and click the ``Set to Default`` button. - -.. seealso:: :rfc:`2616` - -.. _faq1_33: - -1.33 (withdrawn). ------------------ - -.. _faq1_34: - -1.34 Can I directly access a database or table pages? ------------------------------------------------------ - -Yes. Out of the box, you can use a :term:`URL` like -``http://server/phpMyAdmin/index.php?server=X&db=database&table=table&target=script``. -For ``server`` you can use the server number -which refers to the numeric host index (from ``$i``) in -:file:`config.inc.php`. The table and script parts are optional. - -If you want a URL like -``http://server/phpMyAdmin/database[/table][/script]``, you need to do some additional configuration. The following -lines apply only for the `Apache <https://httpd.apache.org>`_ web server. -First, make sure that you have enabled some features within the Apache global -configuration. You need ``Options SymLinksIfOwnerMatch`` and ``AllowOverride -FileInfo`` enabled for directory where phpMyAdmin is installed and you -need mod\_rewrite to be enabled. Then you just need to create the -following :term:`.htaccess` file in root folder of phpMyAdmin installation (don't -forget to change directory name inside of it): - -.. code-block:: apache - - RewriteEngine On - RewriteBase /path_to_phpMyAdmin - RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R] - RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R] - RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R] - RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R] - -.. seealso:: :ref:`faq4_8` - -.. _faq1_35: - -1.35 Can I use HTTP authentication with Apache CGI? ---------------------------------------------------- - -Yes. However you need to pass authentication variable to :term:`CGI` using -following rewrite rule: - -.. code-block:: apache - - RewriteEngine On - RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L] - -.. _faq1_36: - -1.36 I get an error "500 Internal Server Error". ------------------------------------------------- - -There can be many explanations to this and a look at your server's -error log file might give a clue. - -.. _faq1_37: - -1.37 I run phpMyAdmin on cluster of different machines and password encryption in cookie auth doesn't work. ------------------------------------------------------------------------------------------------------------ - -If your cluster consist of different architectures, PHP code used for -encryption/decryption won't work correct. This is caused by use of -pack/unpack functions in code. Only solution is to use mcrypt -extension which works fine in this case. - -.. _faq1_38: - -1.38 Can I use phpMyAdmin on a server on which Suhosin is enabled? ------------------------------------------------------------------- - -Yes but the default configuration values of Suhosin are known to cause -problems with some operations, for example editing a table with many -columns and no :term:`primary key` or with textual :term:`primary key`. - -Suhosin configuration might lead to malfunction in some cases and it -can not be fully avoided as phpMyAdmin is kind of application which -needs to transfer big amounts of columns in single HTTP request, what -is something what Suhosin tries to prevent. Generally all -``suhosin.request.*``, ``suhosin.post.*`` and ``suhosin.get.*`` -directives can have negative effect on phpMyAdmin usability. You can -always find in your error logs which limit did cause dropping of -variable, so you can diagnose the problem and adjust matching -configuration variable. - -The default values for most Suhosin configuration options will work in -most scenarios, however you might want to adjust at least following -parameters: - -* `suhosin.request.max\_vars <https://suhosin.org/stories/configuration.html#suhosin-request-max-vars>`_ should - be increased (eg. 2048) -* `suhosin.post.max\_vars <https://suhosin.org/stories/configuration.html#suhosin-post-max-vars>`_ should be - increased (eg. 2048) -* `suhosin.request.max\_array\_index\_length <https://suhosin.org/stories/configuration.html#suhosin-request-max-array-index-length>`_ - should be increased (eg. 256) -* `suhosin.post.max\_array\_index\_length <https://suhosin.org/stories/configuration.html#suhosin-post-max-array-index-length>`_ - should be increased (eg. 256) -* `suhosin.request.max\_totalname\_length <https://suhosin.org/stories/configuration.html#suhosin-request-max-totalname-length>`_ - should be increased (eg. 8192) -* `suhosin.post.max\_totalname\_length <https://suhosin.org/stories/configuration.html#suhosin-post-max-totalname-length>`_ should be - increased (eg. 8192) -* `suhosin.get.max\_value\_length <https://suhosin.org/stories/configuration.html#suhosin-get-max-value-length>`_ - should be increased (eg. 1024) -* `suhosin.sql.bailout\_on\_error <https://suhosin.org/stories/configuration.html#suhosin-sql-bailout-on-error>`_ - needs to be disabled (the default) -* `suhosin.log.\* <https://suhosin.org/stories/configuration.html#logging-configuration>`_ should not - include :term:`SQL`, otherwise you get big - slowdown -* `suhosin.sql.union <https://suhosin.org/stories/configuration.html#suhosin- - sql-union>`_ must be disabled (which is the default). -* `suhosin.sql.multiselect <https://suhosin.org/stories/configuration.html# - suhosin-sql-multiselect>`_ must be disabled (which is the default). -* `suhosin.sql.comment <https://suhosin.org/stories/configuration.html#suhosin- - sql-comment>`_ must be disabled (which is the default). - -To further improve security, we also recommend these modifications: - -* `suhosin.executor.include.max\_traversal <https://suhosin.org/stories/ - configuration.html#suhosin-executor-include-max-traversal>`_ should be - enabled as a mitigation against local file inclusion attacks. We suggest - setting this to 2 as ``../`` is used with the ReCaptcha library. -* `suhosin.cookie.encrypt <https://suhosin.org/stories/configuration.html# - suhosin-cookie-encrypt>`_ should be enabled. -* `suhosin.executor.disable_emodifier <https://suhosin.org/stories/config - uration.html#suhosin-executor-disable-emodifier>`_ should be enabled. - -You can also disable the warning using the :config:option:`$cfg['SuhosinDisableWarning']`. - -.. _faq1_39: - -1.39 When I try to connect via https, I can log in, but then my connection is redirected back to http. What can cause this behavior? ------------------------------------------------------------------------------------------------------------------------------------- - -This is caused by the fact that PHP scripts have no knowledge that the site is -using https. Depending on used webserver, you should configure it to let PHP -know about URL and scheme used to access it. - -For example in Apache ensure that you have enabled ``SSLOptions`` and -``StdEnvVars`` in the configuration. - -.. seealso:: <https://httpd.apache.org/docs/2.4/mod/mod_ssl.html> - -.. _faq1_40: - -1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work. ---------------------------------------------------------------------------------------- - -To be able to use cookie auth Apache must know that it has to rewrite -the set-cookie headers. Example from the Apache 2.2 documentation: - -.. code-block:: apache - - ProxyPass /mirror/foo/ http://backend.example.com/ - ProxyPassReverse /mirror/foo/ http://backend.example.com/ - ProxyPassReverseCookieDomain backend.example.com public.example.com - ProxyPassReverseCookiePath / /mirror/foo/ - -Note: if the backend url looks like ``http://server/~user/phpmyadmin``, the -tilde (~) must be url encoded as %7E in the ProxyPassReverse\* lines. -This is not specific to phpmyadmin, it's just the behavior of Apache. - -.. code-block:: apache - - ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin - ProxyPassReverse /mirror/foo/ http://backend.example.com/%7Euser/phpmyadmin - ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo - -.. seealso:: <https://httpd.apache.org/docs/2.2/mod/mod_proxy.html>, :config:option:`$cfg['PmaAbsoluteUri']` - -.. _faq1_41: - -1.41 When I view a database and ask to see its privileges, I get an error about an unknown column. --------------------------------------------------------------------------------------------------- - -The MySQL server's privilege tables are not up to date, you need to -run the :command:`mysql_upgrade` command on the server. - -.. _faq1_42: - -1.42 How can I prevent robots from accessing phpMyAdmin? --------------------------------------------------------- - -You can add various rules to :term:`.htaccess` to filter access based on user agent -field. This is quite easy to circumvent, but could prevent at least -some robots accessing your installation. - -.. code-block:: apache - - RewriteEngine on - - # Allow only GET and POST verbs - RewriteCond %{REQUEST_METHOD} !^(GET|POST)$ [NC,OR] - - # Ban Typical Vulnerability Scanners and others - # Kick out Script Kiddies - RewriteCond %{HTTP_USER_AGENT} ^(java|curl|wget).* [NC,OR] - RewriteCond %{HTTP_USER_AGENT} ^.*(libwww-perl|curl|wget|python|nikto|wkito|pikto|scan|acunetix).* [NC,OR] - RewriteCond %{HTTP_USER_AGENT} ^.*(winhttp|HTTrack|clshttp|archiver|loader|email|harvest|extract|grab|miner).* [NC,OR] - - # Ban Search Engines, Crawlers to your administrative panel - # No reasons to access from bots - # Ultimately Better than the useless robots.txt - # Did google respect robots.txt? - # Try google: intitle:phpMyAdmin intext:"Welcome to phpMyAdmin *.*.*" intext:"Log in" -wiki -forum -forums -questions intext:"Cookies must be enabled" - RewriteCond %{HTTP_USER_AGENT} ^.*(AdsBot-Google|ia_archiver|Scooter|Ask.Jeeves|Baiduspider|Exabot|FAST.Enterprise.Crawler|FAST-WebCrawler|www\.neomo\.de|Gigabot|Mediapartners-Google|Google.Desktop|Feedfetcher-Google|Googlebot|heise-IT-Markt-Crawler|heritrix|ibm.com\cs/crawler|ICCrawler|ichiro|MJ12bot|MetagerBot|msnbot-NewsBlogs|msnbot|msnbot-media|NG-Search|lucene.apache.org|NutchCVS|OmniExplorer_Bot|online.link.validator|psbot0|Seekbot|Sensis.Web.Crawler|SEO.search.Crawler|Seoma.\[SEO.Crawler\]|SEOsearch|Snappy|www.urltrends.com|www.tkl.iis.u-tokyo.ac.jp/~crawler|SynooBot|crawleradmin.t-info@telekom.de|TurnitinBot|voyager|W3.SiteSearch.Crawler|W3C-checklink|W3C_Validator|www.WISEnutbot.com|yacybot|Yahoo-MMCrawler|Yahoo\!.DE.Slurp|Yahoo\!.Slurp|YahooSeeker).* [NC] - RewriteRule .* - [F] - -.. _faq1_43: - -1.43 Why can't I display the structure of my table containing hundreds of columns? ----------------------------------------------------------------------------------- - -Because your PHP's ``memory_limit`` is too low; adjust it in :file:`php.ini`. - -.. _faq1:44: - -1.44 How can I reduce the installed size of phpMyAdmin on disk? ---------------------------------------------------------------- - -Some users have requested to be able to reduce the size of the phpMyAdmin installation. -This is not recommended and could lead to confusion over missing features, but can be done. -A list of files and corresponding functionality which degrade gracefully when removed include: - -* :file:`./vendor/tecnickcom/tcpdf` folder (exporting to PDF) -* :file:`./locale/` folder, or unused subfolders (interface translations) -* Any unused themes in :file:`./themes/` -* :file:`./js/vendor/jquery/src/` (included for licensing reasons) -* :file:`./js/line_counts.php` (removed in phpMyAdmin 4.8) -* :file:`./doc/` (documentation) -* :file:`./setup/` (setup script) -* :file:`./examples/` -* :file:`./sql/` (SQL scripts to configure advanced functionality) -* :file:`./js/vendor/openlayers/` (GIS visualization) - -.. _faq1_45: - -1.45 I get an error message about unknown authentication method caching_sha2_password when trying to log in ------------------------------------------------------------------------------------------------------------ - -When logging in using MySQL version 8 or newer, you may encounter an error message like this: - - mysqli_real_connect(): The server requested authentication method unknown to the client [caching_sha2_password] - - mysqli_real_connect(): (HY000/2054): The server requested authentication method unknown to the client - -This error is because of a version compatibility problem between PHP and MySQL. The MySQL project introduced a new authentication -method (our tests show this began with version 8.0.11) however PHP did not include the ability to use that authentication method. -PHP reports that this was fixed in PHP version 7.4. - -Users experiencing this are encouraged to upgrade their PHP installation, however a workaround exists. Your MySQL user account -can be set to use the older authentication with a command such as - -.. code-block:: mysql - - ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'PASSWORD'; - -.. seealso:: <https://github.com/phpmyadmin/phpmyadmin/issues/14220>, <https://stackoverflow.com/questions/49948350/phpmyadmin-on-mysql-8-0>, <https://bugs.php.net/bug.php?id=76243> - -.. _faqconfig: - -Configuration -+++++++++++++ - -.. _faq2_1: - -2.1 The error message "Warning: Cannot add header information - headers already sent by ..." is displayed, what's the problem? ------------------------------------------------------------------------------------------------------------------------------- - -Edit your :file:`config.inc.php` file and ensure there is nothing (I.E. no -blank lines, no spaces, no characters...) neither before the ``<?php`` tag at -the beginning, neither after the ``?>`` tag at the end. - -.. _faq2_2: - -2.2 phpMyAdmin can't connect to MySQL. What's wrong? ----------------------------------------------------- - -Either there is an error with your PHP setup or your username/password -is wrong. Try to make a small script which uses mysql\_connect and see -if it works. If it doesn't, it may be you haven't even compiled MySQL -support into PHP. - -.. _faq2_3: - -2.3 The error message "Warning: MySQL Connection Failed: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (111) ..." is displayed. What can I do? ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- - -The error message can also be: :guilabel:`Error #2002 - The server is not -responding (or the local MySQL server's socket is not correctly configured)`. - -First, you need to determine what socket is being used by MySQL. To do this, -connect to your server and go to the MySQL bin directory. In this directory -there should be a file named *mysqladmin*. Type ``./mysqladmin variables``, and -this should give you a bunch of info about your MySQL server, including the -socket (*/tmp/mysql.sock*, for example). You can also ask your ISP for the -connection info or, if you're hosting your own, connect from the 'mysql' -command-line client and type 'status' to get the connection type and socket or -port number. - -Then, you need to tell PHP to use this socket. You can do this for all PHP in -the :file:`php.ini` or for phpMyAdmin only in the :file:`config.inc.php`. For -example: :config:option:`$cfg['Servers'][$i]['socket']` Please also make sure -that the permissions of this file allow to be readable by your webserver. - -On my RedHat-Box the socket of MySQL is */var/lib/mysql/mysql.sock*. -In your :file:`php.ini` you will find a line - -.. code-block:: ini - - mysql.default_socket = /tmp/mysql.sock - -change it to - -.. code-block:: ini - - mysql.default_socket = /var/lib/mysql/mysql.sock - -Then restart apache and it will work. - -Have also a look at the `corresponding section of the MySQL -documentation <https://dev.mysql.com/doc/refman/5.7/en/can-not-connect-to-server.html>`_. - -.. _faq2_4: - -2.4 Nothing is displayed by my browser when I try to run phpMyAdmin, what can I do? ------------------------------------------------------------------------------------ - -Try to set the :config:option:`$cfg['OBGzip']` directive to ``false`` in the phpMyAdmin configuration -file. It helps sometime. Also have a look at your PHP version number: -if it contains "b" or "alpha" it means you're running a testing -version of PHP. That's not a so good idea, please upgrade to a plain -revision. - -.. _faq2_5: - -2.5 Each time I want to insert or change a row or drop a database or a table, an error 404 (page not found) is displayed or, with HTTP or cookie authentication, I'm asked to log in again. What's wrong? ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- - -Check your webserver setup if it correctly fills in either PHP_SELF or REQUEST_URI variables. - -If you are running phpMyAdmin behind reverse proxy, please set the -:config:option:`$cfg['PmaAbsoluteUri']` directive in the phpMyAdmin -configuration file to match your setup. - -.. _faq2_6: - -2.6 I get an "Access denied for user: 'root@localhost' (Using password: YES)"-error when trying to access a MySQL-Server on a host which is port-forwarded for my localhost. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- - -When you are using a port on your localhost, which you redirect via -port-forwarding to another host, MySQL is not resolving the localhost -as expected. Erik Wasser explains: The solution is: if your host is -"localhost" MySQL (the command line tool :command:`mysql` as well) always -tries to use the socket connection for speeding up things. And that -doesn't work in this configuration with port forwarding. If you enter -"127.0.0.1" as hostname, everything is right and MySQL uses the -:term:`TCP` connection. - -.. _faqthemes: - -2.7 Using and creating themes ------------------------------ - -See :ref:`themes`. - -.. _faqmissingparameters: - -2.8 I get "Missing parameters" errors, what can I do? ------------------------------------------------------ - -Here are a few points to check: - -* In :file:`config.inc.php`, try to leave the :config:option:`$cfg['PmaAbsoluteUri']` directive empty. See also - :ref:`faq4_7`. -* Maybe you have a broken PHP installation or you need to upgrade your - Zend Optimizer. See <https://bugs.php.net/bug.php?id=31134>. -* If you are using Hardened PHP with the ini directive - ``varfilter.max_request_variables`` set to the default (200) or - another low value, you could get this error if your table has a high - number of columns. Adjust this setting accordingly. (Thanks to Klaus - Dorninger for the hint). -* In the :file:`php.ini` directive ``arg_separator.input``, a value of ";" - will cause this error. Replace it with "&;". -* If you are using `Suhosin <https://suhosin.org/stories/index.html>`_, you - might want to increase `request limits <https://suhosin.org/stories/faq.html>`_. -* The directory specified in the :file:`php.ini` directive - ``session.save_path`` does not exist or is read-only (this can be caused - by `bug in the PHP installer <https://bugs.php.net/bug.php?id=39842>`_). - -.. _faq2_9: - -2.9 Seeing an upload progress bar ---------------------------------- - -To be able to see a progress bar during your uploads, your server must -have the `APC <https://www.php.net/manual/en/book.apc.php>`_ extension, the -`uploadprogress <https://pecl.php.net/package/uploadprogress>`_ one, or -you must be running PHP 5.4.0 or higher. Moreover, the JSON extension -has to be enabled in your PHP. - -If using APC, you must set ``apc.rfc1867`` to ``on`` in your :file:`php.ini`. - -If using PHP 5.4.0 or higher, you must set -``session.upload_progress.enabled`` to ``1`` in your :file:`php.ini`. However, -starting from phpMyAdmin version 4.0.4, session-based upload progress has -been temporarily deactivated due to its problematic behavior. - -.. seealso:: :rfc:`1867` - -.. _faqlimitations: - -Known limitations -+++++++++++++++++ - -.. _login_bug: - -3.1 When using HTTP authentication, a user who logged out can not log in again in with the same nick. ------------------------------------------------------------------------------------------------------ - -This is related to the authentication mechanism (protocol) used by -phpMyAdmin. To bypass this problem: just close all the opened browser -windows and then go back to phpMyAdmin. You should be able to log in -again. - -.. _faq3_2: - -3.2 When dumping a large table in compressed mode, I get a memory limit error or a time limit error. ----------------------------------------------------------------------------------------------------- - -Compressed dumps are built in memory and because of this are limited -to php's memory limit. For gzip/bzip2 exports this can be overcome -since 2.5.4 using :config:option:`$cfg['CompressOnFly']` (enabled by default). -zip exports can not be handled this way, so if you need zip files for larger -dump, you have to use another way. - -.. _faq3_3: - -3.3 With InnoDB tables, I lose foreign key relationships when I rename a table or a column. -------------------------------------------------------------------------------------------- - -This is an InnoDB bug, see <https://bugs.mysql.com/bug.php?id=21704>. - -.. _faq3_4: - -3.4 I am unable to import dumps I created with the mysqldump tool bundled with the MySQL server distribution. -------------------------------------------------------------------------------------------------------------- - -The problem is that older versions of ``mysqldump`` created invalid -comments like this: - -.. code-block:: mysql - - -- MySQL dump 8.22 - -- - -- Host: localhost Database: database - --------------------------------------------------------- - -- Server version 3.23.54 - -The invalid part of the code is the horizontal line made of dashes -that appears once in every dump created with mysqldump. If you want to -run your dump you have to turn it into valid MySQL. This means, you -have to add a whitespace after the first two dashes of the line or add -a # before it: ``-- -------------------------------------------------------`` or -``#---------------------------------------------------------`` - -.. _faq3_5: - -3.5 When using nested folders, multiple hierarchies are displayed in a wrong manner. ------------------------------------------------------------------------------------- - -Please note that you should not use the separating string multiple -times without any characters between them, or at the beginning/end of -your table name. If you have to, think about using another -TableSeparator or disabling that feature. - -.. seealso:: :config:option:`$cfg['NavigationTreeTableSeparator']` - -.. _faq3_6: - -3.6 (withdrawn). ------------------ - -.. _faq3_7: - -3.7 I have table with many (100+) columns and when I try to browse table I get series of errors like "Warning: unable to parse url". How can this be fixed? ------------------------------------------------------------------------------------------------------------------------------------------------------------ - -Your table neither have a :term:`primary key` nor an :term:`unique key`, so we must -use a long expression to identify this row. This causes problems to -parse\_url function. The workaround is to create a :term:`primary key` -or :term:`unique key`. - -.. _faq3_8: - -3.8 I cannot use (clickable) HTML-forms in columns where I put a MIME-Transformation onto! ------------------------------------------------------------------------------------------- - -Due to a surrounding form-container (for multi-row delete checkboxes), -no nested forms can be put inside the table where phpMyAdmin displays -the results. You can, however, use any form inside of a table if keep -the parent form-container with the target to tbl\_row\_delete.php and -just put your own input-elements inside. If you use a custom submit -input field, the form will submit itself to the displaying page again, -where you can validate the $HTTP\_POST\_VARS in a transformation. For -a tutorial on how to effectively use transformations, see our `Link -section <https://www.phpmyadmin.net/docs/>`_ on the -official phpMyAdmin-homepage. - -.. _faq3_9: - -3.9 I get error messages when using "--sql\_mode=ANSI" for the MySQL server. ----------------------------------------------------------------------------- - -When MySQL is running in ANSI-compatibility mode, there are some major -differences in how :term:`SQL` is structured (see -<https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html>). Most important of all, the -quote-character (") is interpreted as an identifier quote character and not as -a string quote character, which makes many internal phpMyAdmin operations into -invalid :term:`SQL` statements. There is no -workaround to this behaviour. News to this item will be posted in `issue -#7383 <https://github.com/phpmyadmin/phpmyadmin/issues/7383>`_. - -.. _faq3_10: - -3.10 Homonyms and no primary key: When the results of a SELECT display more that one column with the same value (for example ``SELECT lastname from employees where firstname like 'A%'`` and two "Smith" values are displayed), if I click Edit I cannot be sure that I am editing the intended row. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ - -Please make sure that your table has a :term:`primary key`, so that phpMyAdmin -can use it for the Edit and Delete links. - -.. _faq3_11: - -3.11 The number of rows for InnoDB tables is not correct. ---------------------------------------------------------- - -phpMyAdmin uses a quick method to get the row count, and this method only -returns an approximate count in the case of InnoDB tables. See -:config:option:`$cfg['MaxExactCount']` for a way to modify those results, but -this could have a serious impact on performance. -However, one can easily replace the approximate row count with exact count by -simply clicking on the approximate count. This can also be done for all tables -at once by clicking on the rows sum displayed at the bottom. - -.. seealso:: :config:option:`$cfg['MaxExactCount']` - -.. _faq3_12: - -3.12 (withdrawn). ------------------ - -.. _faq3_13: - -3.13 I get an error when entering ``USE`` followed by a db name containing an hyphen. -------------------------------------------------------------------------------------- - -The tests I have made with MySQL 5.1.49 shows that the API does not -accept this syntax for the USE command. - -.. _faq3_14: - -3.14 I am not able to browse a table when I don't have the right to SELECT one of the columns. ----------------------------------------------------------------------------------------------- - -This has been a known limitation of phpMyAdmin since the beginning and -it's not likely to be solved in the future. - -.. _faq3_15: - -3.15 (withdrawn). ------------------ - -.. _faq3_16: - -3.16 (withdrawn). ------------------ - -.. _faq3_17: - -3.17 (withdrawn). ------------------ - -.. _faq3_18: - -3.18 When I import a CSV file that contains multiple tables, they are lumped together into a single table. ----------------------------------------------------------------------------------------------------------- - -There is no reliable way to differentiate tables in :term:`CSV` format. For the -time being, you will have to break apart :term:`CSV` files containing multiple -tables. - -.. _faq3_19: - -3.19 When I import a file and have phpMyAdmin determine the appropriate data structure it only uses int, decimal, and varchar types. ------------------------------------------------------------------------------------------------------------------------------------- - -Currently, the import type-detection system can only assign these -MySQL types to columns. In future, more will likely be added but for -the time being you will have to edit the structure to your liking -post-import. Also, you should note the fact that phpMyAdmin will use -the size of the largest item in any given column as the column size -for the appropriate type. If you know you will be adding larger items -to that column then you should manually adjust the column sizes -accordingly. This is done for the sake of efficiency. - -.. _faq3_20: - -3.20 After upgrading, some bookmarks are gone or their content cannot be shown. -------------------------------------------------------------------------------- - -At some point, the character set used to store bookmark content has changed. -It's better to recreate your bookmark from the newer phpMyAdmin version. - -.. _faq3_21: - -3.21 I am unable to log in with a username containing unicode characters such as á. ------------------------------------------------------------------------------------ - -This can happen if MySQL server is not configured to use utf-8 as default -charset. This is a limitation of how PHP and the MySQL server interact; there -is no way for PHP to set the charset before authenticating. - -.. seealso:: - - `phpMyAdmin issue 12232 <https://github.com/phpmyadmin/phpmyadmin/issues/12232>`_, - `MySQL documentation note <https://www.php.net/manual/en/mysqli.real-connect.php#refsect1-mysqli.real-connect-notes>`_ - -.. _faqmultiuser: - -ISPs, multi-user installations -++++++++++++++++++++++++++++++ - -.. _faq4_1: - -4.1 I'm an ISP. Can I setup one central copy of phpMyAdmin or do I need to install it for each customer? --------------------------------------------------------------------------------------------------------- - -Since version 2.0.3, you can setup a central copy of phpMyAdmin for all your -users. The development of this feature was kindly sponsored by NetCologne GmbH. -This requires a properly setup MySQL user management and phpMyAdmin -:term:`HTTP` or cookie authentication. - -.. seealso:: :ref:`authentication_modes` - -.. _faq4_2: - -4.2 What's the preferred way of making phpMyAdmin secure against evil access? ------------------------------------------------------------------------------ - -This depends on your system. If you're running a server which cannot be -accessed by other people, it's sufficient to use the directory protection -bundled with your webserver (with Apache you can use :term:`.htaccess` files, -for example). If other people have telnet access to your server, you should use -phpMyAdmin's :term:`HTTP` or cookie authentication features. - -Suggestions: - -* Your :file:`config.inc.php` file should be ``chmod 660``. -* All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy - is a user whose password is only known to you, and apache is the group - under which Apache runs. -* Follow security recommendations for PHP and your webserver. - -.. _faq4_3: - -4.3 I get errors about not being able to include a file in */lang* or in */libraries*. --------------------------------------------------------------------------------------- - -Check :file:`php.ini`, or ask your sysadmin to check it. The -``include_path`` must contain "." somewhere in it, and -``open_basedir``, if used, must contain "." and "./lang" to allow -normal operation of phpMyAdmin. - -.. _faq4_4: - -4.4 phpMyAdmin always gives "Access denied" when using HTTP authentication. ---------------------------------------------------------------------------- - -This could happen for several reasons: - -* :config:option:`$cfg['Servers'][$i]['controluser']` and/or :config:option:`$cfg['Servers'][$i]['controlpass']` are wrong. -* The username/password you specify in the login dialog are invalid. -* You have already setup a security mechanism for the phpMyAdmin- - directory, eg. a :term:`.htaccess` file. This would interfere with phpMyAdmin's - authentication, so remove it. - -.. _faq4_5: - -4.5 Is it possible to let users create their own databases? ------------------------------------------------------------ - -Starting with 2.2.5, in the user management page, you can enter a -wildcard database name for a user (for example "joe%"), and put the -privileges you want. For example, adding ``SELECT, INSERT, UPDATE, -DELETE, CREATE, DROP, INDEX, ALTER`` would let a user create/manage -his/her database(s). - -.. _faq4_6: - -4.6 How can I use the Host-based authentication additions? ----------------------------------------------------------- - -If you have existing rules from an old :term:`.htaccess` file, you can take them and -add a username between the ``'deny'``/``'allow'`` and ``'from'`` -strings. Using the username wildcard of ``'%'`` would be a major -benefit here if your installation is suited to using it. Then you can -just add those updated lines into the -:config:option:`$cfg['Servers'][$i]['AllowDeny']['rules']` array. - -If you want a pre-made sample, you can try this fragment. It stops the -'root' user from logging in from any networks other than the private -network :term:`IP` blocks. - -.. code-block:: php - - //block root from logging in except from the private networks - $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow'; - $cfg['Servers'][$i]['AllowDeny']['rules'] = array( - 'deny root from all', - 'allow root from localhost', - 'allow root from 10.0.0.0/8', - 'allow root from 192.168.0.0/16', - 'allow root from 172.16.0.0/12', - ); - -.. _faq4_7: - -4.7 Authentication window is displayed more than once, why? ------------------------------------------------------------ - -This happens if you are using a :term:`URL` to start phpMyAdmin which is -different than the one set in your :config:option:`$cfg['PmaAbsoluteUri']`. For -example, a missing "www", or entering with an :term:`IP` address while a domain -name is defined in the config file. - -.. _faq4_8: - -4.8 Which parameters can I use in the URL that starts phpMyAdmin? ------------------------------------------------------------------ - -When starting phpMyAdmin, you can use the ``db`` -and ``server`` parameters. This last one can contain -either the numeric host index (from ``$i`` of the configuration file) -or one of the host names present in the configuration file. - -For example, to jump directly to a particular database, a URL can be constructed as -``https://example.com/phpmyadmin/?db=sakila``. - -.. seealso:: :ref:`faq1_34` - -.. versionchanged:: 4.9.0 - - Support for using the ``pma_username`` and ``pma_password`` parameters was removed - in phpMyAdmin 4.9.0 (see `PMASA-2019-4 <https://www.phpmyadmin.net/security/PMASA-2019-4/>`_). - -.. _faqbrowsers: - -Browsers or client OS -+++++++++++++++++++++ - -.. _faq5_1: - -5.1 I get an out of memory error, and my controls are non-functional, when trying to create a table with more than 14 columns. ------------------------------------------------------------------------------------------------------------------------------- - -We could reproduce this problem only under Win98/98SE. Testing under -WinNT4 or Win2K, we could easily create more than 60 columns. A -workaround is to create a smaller number of columns, then come back to -your table properties and add the other columns. - -.. _faq5_2: - -5.2 With Xitami 2.5b4, phpMyAdmin won't process form fields. ------------------------------------------------------------- - -This is not a phpMyAdmin problem but a Xitami known bug: you'll face -it with each script/website that use forms. Upgrade or downgrade your -Xitami server. - -.. _faq5_3: - -5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2). ---------------------------------------------------------------------- - -With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except -that the proposed file name for the dump is always 'tbl\_dump.php'. -The bzip2 dumps don't seem to work. With Konqueror 2.2.1: plain dumps -work; zip dumps are placed into the user's temporary directory, so -they must be moved before closing Konqueror, or else they disappear. -gzip dumps give an error message. Testing needs to be done for -Konqueror 2.2.2. - -.. _faq5_4: - -5.4 I can't use the cookie authentication mode because Internet Explorer never stores the cookies. --------------------------------------------------------------------------------------------------- - -MS Internet Explorer seems to be really buggy about cookies, at least -till version 6. - -.. _faq5_5: - -5.5 (withdrawn). ----------------------------------------------------------------------------- - -.. _faq5_6: - -5.6 (withdrawn). ------------------------------------------------------------------------------------------------------------------------------------------------------------------ - -.. _faq5_7: - -5.7 I refresh (reload) my browser, and come back to the welcome page. ---------------------------------------------------------------------- - -Some browsers support right-clicking into the frame you want to -refresh, just do this in the right frame. - -.. _faq5_8: - -5.8 With Mozilla 0.9.7 I have problems sending a query modified in the query box. ---------------------------------------------------------------------------------- - -Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future -Mozilla versions. - -.. _faq5_9: - -5.9 With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a whitespace in the SQL-Query edit area: the page scrolls down. -------------------------------------------------------------------------------------------------------------------------------- - -This is a Mozilla bug (see bug #26882 at `BugZilla -<https://bugzilla.mozilla.org/>`_). - -.. _faq5_10: - -5.10 (withdrawn). ------------------------------------------------------------------------------------------ - -.. _faq5_11: - -5.11 Extended-ASCII characters like German umlauts are displayed wrong. ------------------------------------------------------------------------ - -Please ensure that you have set your browser's character set to the -one of the language file you have selected on phpMyAdmin's start page. -Alternatively, you can try the auto detection mode that is supported -by the recent versions of the most browsers. - -.. _faq5_12: - -5.12 Mac OS X Safari browser changes special characters to "?". ---------------------------------------------------------------- - -This issue has been reported by a :term:`Mac OS X` user, who adds that Chimera, -Netscape and Mozilla do not have this problem. - -.. _faq5_13: - -5.13 (withdrawn) ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- - -.. _faq5_14: - -5.14 (withdrawn) ------------------------------------------------------------------------------------------------------------------- - -.. _faq5_15: - -5.15 (withdrawn) ------------------------------------------ - -.. _faq5_16: - -5.16 With Internet Explorer, I get "Access is denied" Javascript errors. Or I cannot make phpMyAdmin work under Windows. ------------------------------------------------------------------------------------------------------------------------- - -Please check the following points: - -* Maybe you have defined your :config:option:`$cfg['PmaAbsoluteUri']` setting in - :file:`config.inc.php` to an :term:`IP` address and you are starting phpMyAdmin - with a :term:`URL` containing a domain name, or the reverse situation. -* Security settings in IE and/or Microsoft Security Center are too high, - thus blocking scripts execution. -* The Windows Firewall is blocking Apache and MySQL. You must allow - :term:`HTTP` ports (80 or 443) and MySQL - port (usually 3306) in the "in" and "out" directions. - -.. _faq5_17: - -5.17 With Firefox, I cannot delete rows of data or drop a database. -------------------------------------------------------------------- - -Many users have confirmed that the Tabbrowser Extensions plugin they -installed in their Firefox is causing the problem. - -.. _faq5_18: - -5.18 (withdrawn) ------------------------------------------------------------------------------------------ - -.. _faq5_19: - -5.19 I get JavaScript errors in my browser. -------------------------------------------- - -Issues have been reported with some combinations of browser -extensions. To troubleshoot, disable all extensions then clear your -browser cache to see if the problem goes away. - -.. _faq5_20: - -5.20 I get errors about violating Content Security Policy. ----------------------------------------------------------- - -If you see errors like: - -.. code-block:: text - - Refused to apply inline style because it violates the following Content Security Policy directive - -This is usually caused by some software, which wrongly rewrites -:mailheader:`Content Security Policy` headers. Usually this is caused by -antivirus proxy or browser addons which are causing such errors. - -If you see these errors, try disabling the HTTP proxy in antivirus or disable -the :mailheader:`Content Security Policy` rewriting in it. If that doesn't -help, try disabling browser extensions. - -Alternatively it can be also server configuration issue (if the webserver is -configured to emit :mailheader:`Content Security Policy` headers, they can -override the ones from phpMyAdmin). - -Programs known to cause these kind of errors: - -* Kaspersky Internet Security - -.. _faq5_21: - -5.21 I get errors about potentially unsafe operation when browsing table or executing SQL query. ------------------------------------------------------------------------------------------------- - -If you see errors like: - -.. code-block:: text - - A potentially unsafe operation has been detected in your request to this site. - -This is usually caused by web application firewall doing requests filtering. It -tries to prevent SQL injection, however phpMyAdmin is tool designed to execute -SQL queries, thus it makes it unusable. - -Please whitelist phpMyAdmin scripts from the web application firewall settings -or disable it completely for phpMyAdmin path. - -Programs known to cause these kind of errors: - -* Wordfence Web Application Firewall - -.. _faqusing: - -Using phpMyAdmin -++++++++++++++++ - -.. _faq6_1: - -6.1 I can't insert new rows into a table / I can't create a table - MySQL brings up a SQL error. ------------------------------------------------------------------------------------------------- - -Examine the :term:`SQL` error with care. -Often the problem is caused by specifying a wrong column-type. Common -errors include: - -* Using ``VARCHAR`` without a size argument -* Using ``TEXT`` or ``BLOB`` with a size argument - -Also, look at the syntax chapter in the MySQL manual to confirm that -your syntax is correct. - -.. _faq6_2: - -6.2 When I create a table, I set an index for two columns and phpMyAdmin generates only one index with those two columns. -------------------------------------------------------------------------------------------------------------------------- - -This is the way to create a multi-columns index. If you want two -indexes, create the first one when creating the table, save, then -display the table properties and click the Index link to create the -other index. - -.. _faq6_3: - -6.3 How can I insert a null value into my table? ------------------------------------------------- - -Since version 2.2.3, you have a checkbox for each column that can be -null. Before 2.2.3, you had to enter "null", without the quotes, as -the column's value. Since version 2.5.5, you have to use the checkbox -to get a real NULL value, so if you enter "NULL" this means you want a -literal NULL in the column, and not a NULL value (this works in PHP4). - -.. _faq6_4: - -6.4 How can I backup my database or table? ------------------------------------------- - -Click on a database or table name in the navigation panel, the properties will -be displayed. Then on the menu, click "Export", you can dump the structure, the -data, or both. This will generate standard :term:`SQL` statements that can be -used to recreate your database/table. You will need to choose "Save as file", -so that phpMyAdmin can transmit the resulting dump to your station. Depending -on your PHP configuration, you will see options to compress the dump. See also -the :config:option:`$cfg['ExecTimeLimit']` configuration variable. For -additional help on this subject, look for the word "dump" in this document. - -.. _faq6_5: - -6.5 How can I restore (upload) my database or table using a dump? How can I run a ".sql" file? ----------------------------------------------------------------------------------------------- - -Click on a database name in the navigation panel, the properties will -be displayed. Select "Import" from the list of tabs in the right–hand -frame (or ":term:`SQL`" if your phpMyAdmin -version is previous to 2.7.0). In the "Location of the text file" -section, type in the path to your dump filename, or use the Browse -button. Then click Go. With version 2.7.0, the import engine has been -re–written, if possible it is suggested that you upgrade to take -advantage of the new features. For additional help on this subject, -look for the word "upload" in this document. - -Note: For errors while importing of dumps exported from older MySQL versions to newer MySQL versions, -please check :ref:`faq6_41`. - -.. _faq6_6: - -6.6 How can I use the relation table in Query-by-example? ---------------------------------------------------------- - -Here is an example with the tables persons, towns and countries, all -located in the database "mydb". If you don't have a ``pma__relation`` -table, create it as explained in the configuration section. Then -create the example tables: - -.. code-block:: mysql - - CREATE TABLE REL_countries ( - country_code char(1) NOT NULL default '', - description varchar(10) NOT NULL default '', - PRIMARY KEY (country_code) - ) ENGINE=MyISAM; - - INSERT INTO REL_countries VALUES ('C', 'Canada'); - - CREATE TABLE REL_persons ( - id tinyint(4) NOT NULL auto_increment, - person_name varchar(32) NOT NULL default '', - town_code varchar(5) default '0', - country_code char(1) NOT NULL default '', - PRIMARY KEY (id) - ) ENGINE=MyISAM; - - INSERT INTO REL_persons VALUES (11, 'Marc', 'S', 'C'); - INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C'); - - CREATE TABLE REL_towns ( - town_code varchar(5) NOT NULL default '0', - description varchar(30) NOT NULL default '', - PRIMARY KEY (town_code) - ) ENGINE=MyISAM; - - INSERT INTO REL_towns VALUES ('S', 'Sherbrooke'); - INSERT INTO REL_towns VALUES ('M', 'Montréal'); - -To setup appropriate links and display information: - -* on table "REL\_persons" click Structure, then Relation view -* for "town\_code", choose from dropdowns, "mydb", "REL\_towns", "code" - for foreign database, table and column respectively -* for "country\_code", choose from dropdowns, "mydb", "REL\_countries", - "country\_code" for foreign database, table and column respectively -* on table "REL\_towns" click Structure, then Relation view -* in "Choose column to display", choose "description" -* repeat the two previous steps for table "REL\_countries" - -Then test like this: - -* Click on your db name in the navigation panel -* Choose "Query" -* Use tables: persons, towns, countries -* Click "Update query" -* In the columns row, choose persons.person\_name and click the "Show" - tickbox -* Do the same for towns.description and countries.descriptions in the - other 2 columns -* Click "Update query" and you will see in the query box that the - correct joins have been generated -* Click "Submit query" - -.. _faqdisplay: - -6.7 How can I use the "display column" feature? ------------------------------------------------ - -Starting from the previous example, create the ``pma__table_info`` as -explained in the configuration section, then browse your persons -table, and move the mouse over a town code or country code. See also -:ref:`faq6_21` for an additional feature that "display column" -enables: drop-down list of possible values. - -.. _faqpdf: - -6.8 How can I produce a PDF schema of my database? --------------------------------------------------- - -First the configuration variables "relation", "table\_coords" and -"pdf\_pages" have to be filled in. Then you need to think about your -schema layout. Which tables will go on which pages? - -* Select your database in the navigation panel. -* Choose "Operations" in the navigation bar at the top. -* Choose "Edit :term:`PDF` Pages" near the - bottom of the page. -* Enter a name for the first :term:`PDF` page - and click Go. If you like, you can use the "automatic layout," which - will put all your linked tables onto the new page. -* Select the name of the new page (making sure the Edit radio button is - selected) and click Go. -* Select a table from the list, enter its coordinates and click Save. - Coordinates are relative; your diagram will be automatically scaled to - fit the page. When initially placing tables on the page, just pick any - coordinates -- say, 50x50. After clicking Save, you can then use the - :ref:`wysiwyg` to position the element correctly. -* When you'd like to look at your :term:`PDF`, first be sure to click the Save - button beneath the list of tables and coordinates, to save any changes you - made there. Then scroll all the way down, select the :term:`PDF` options you - want, and click Go. -* Internet Explorer for Windows may suggest an incorrect filename when - you try to save a generated :term:`PDF`. - When saving a generated :term:`PDF`, be - sure that the filename ends in ".pdf", for example "schema.pdf". - Browsers on other operating systems, and other browsers on Windows, do - not have this problem. - -.. seealso:: - - :ref:`relations` - -.. _faq6_9: - -6.9 phpMyAdmin is changing the type of one of my columns! ---------------------------------------------------------- - -No, it's MySQL that is doing `silent column type changing -<https://dev.mysql.com/doc/refman/5.7/en/silent-column-changes.html>`_. - -.. _underscore: - -6.10 When creating a privilege, what happens with underscores in the database name? ------------------------------------------------------------------------------------ - -If you do not put a backslash before the underscore, this is a -wildcard grant, and the underscore means "any character". So, if the -database name is "john\_db", the user would get rights to john1db, -john2db ... If you put a backslash before the underscore, it means -that the database name will have a real underscore. - -.. _faq6_11: - -6.11 What is the curious symbol ø in the statistics pages? ----------------------------------------------------------- - -It means "average". - -.. _faqexport: - -6.12 I want to understand some Export options. ----------------------------------------------- - -**Structure:** - -* "Add DROP TABLE" will add a line telling MySQL to `drop the table - <https://dev.mysql.com/doc/refman/5.7/en/drop-table.html>`_, if it already - exists during the import. It does NOT drop the table after your - export, it only affects the import file. -* "If Not Exists" will only create the table if it doesn't exist. - Otherwise, you may get an error if the table name exists but has a - different structure. -* "Add AUTO\_INCREMENT value" ensures that AUTO\_INCREMENT value (if - any) will be included in backup. -* "Enclose table and column names with backquotes" ensures that column - and table names formed with special characters are protected. -* "Add into comments" includes column comments, relations, and media (MIME) - types set in the pmadb in the dump as :term:`SQL` comments - (*/\* xxx \*/*). - -**Data:** - -* "Complete inserts" adds the column names on every INSERT command, for - better documentation (but resulting file is bigger). -* "Extended inserts" provides a shorter dump file by using only once the - INSERT verb and the table name. -* "Delayed inserts" are best explained in the `MySQL manual - INSERT DELAYED Syntax - <https://dev.mysql.com/doc/refman/5.7/en/insert-delayed.html>`_. -* "Ignore inserts" treats errors as a warning instead. Again, more info - is provided in the `MySQL manual - INSERT Syntax - <https://dev.mysql.com/doc/refman/5.7/en/insert.html>`_, but basically with - this selected, invalid values are adjusted and inserted rather than - causing the entire statement to fail. - -.. _faq6_13: - -6.13 I would like to create a database with a dot in its name. --------------------------------------------------------------- - -This is a bad idea, because in MySQL the syntax "database.table" is -the normal way to reference a database and table name. Worse, MySQL -will usually let you create a database with a dot, but then you cannot -work with it, nor delete it. - -.. _faqsqlvalidator: - -6.14 (withdrawn). ------------------ - -.. _faq6_15: - -6.15 I want to add a BLOB column and put an index on it, but MySQL says "BLOB column '...' used in key specification without a key length". -------------------------------------------------------------------------------------------------------------------------------------------- - -The right way to do this, is to create the column without any indexes, -then display the table structure and use the "Create an index" dialog. -On this page, you will be able to choose your BLOB column, and set a -size to the index, which is the condition to create an index on a BLOB -column. - -.. _faq6_16: - -6.16 How can I simply move in page with plenty editing fields? --------------------------------------------------------------- - -You can use :kbd:`Ctrl+arrows` (:kbd:`Option+Arrows` in Safari) for moving on -most pages with many editing fields (table structure changes, row editing, -etc.). - -.. _faq6_17: - -6.17 Transformations: I can't enter my own mimetype! What is this feature then useful for? ------------------------------------------------------------------------------------------- - -Defining mimetypes is of no use if you can't put -transformations on them. Otherwise you could just put a comment on the -column. Because entering your own mimetype will cause serious syntax -checking issues and validation, this introduces a high-risk false- -user-input situation. Instead you have to initialize mimetypes using -functions or empty mimetype definitions. - -Plus, you have a whole overview of available mimetypes. Who knows all those -mimetypes by heart so he/she can enter it at will? - -.. _faqbookmark: - -6.18 Bookmarks: Where can I store bookmarks? Why can't I see any bookmarks below the query box? What are these variables for? ------------------------------------------------------------------------------------------------------------------------------ - -You need to have configured the :ref:`linked-tables` for using bookmarks -feature. Once you have done that, you can use bookmarks in the :guilabel:`SQL` tab. - -.. seealso:: :ref:`bookmarks` - -.. _faq6_19: - -6.19 How can I create simple LATEX document to include exported table? ----------------------------------------------------------------------- - -You can simply include table in your LATEX documents, -minimal sample document should look like following one (assuming you -have table exported in file :file:`table.tex`): - -.. code-block:: latex - - \documentclass{article} % or any class you want - \usepackage{longtable} % for displaying table - \begin{document} % start of document - \include{table} % including exported table - \end{document} % end of document - -.. _faq6_20: - -6.20 I see a lot of databases which are not mine, and cannot access them. -------------------------------------------------------------------------- - -You have one of these global privileges: CREATE TEMPORARY TABLES, SHOW -DATABASES, LOCK TABLES. Those privileges also enable users to see all the -database names. So if your users do not need those privileges, you can remove -them and their databases list will shorten. - -.. seealso:: <https://bugs.mysql.com/bug.php?id=179> - -.. _faq6_21: - -6.21 In edit/insert mode, how can I see a list of possible values for a column, based on some foreign table? ------------------------------------------------------------------------------------------------------------- - -You have to setup appropriate links between the tables, and also setup -the "display column" in the foreign table. See :ref:`faq6_6` for an -example. Then, if there are 100 values or less in the foreign table, a -drop-down list of values will be available. You will see two lists of -values, the first list containing the key and the display column, the -second list containing the display column and the key. The reason for -this is to be able to type the first letter of either the key or the -display column. For 100 values or more, a distinct window will appear, -to browse foreign key values and choose one. To change the default -limit of 100, see :config:option:`$cfg['ForeignKeyMaxLimit']`. - -.. _faq6_22: - -6.22 Bookmarks: Can I execute a default bookmark automatically when entering Browse mode for a table? ------------------------------------------------------------------------------------------------------ - -Yes. If a bookmark has the same label as a table name and it's not a -public bookmark, it will be executed. - -.. seealso:: :ref:`bookmarks` - -.. _faq6_23: - -6.23 Export: I heard phpMyAdmin can export Microsoft Excel files? ------------------------------------------------------------------ - -You can use :term:`CSV` for Microsoft Excel, -which works out of the box. - -.. versionchanged:: 3.4.5 - Since phpMyAdmin 3.4.5 support for direct export to Microsoft Excel version - 97 and newer was dropped. - -.. _faq6_24: - -6.24 Now that phpMyAdmin supports native MySQL 4.1.x column comments, what happens to my column comments stored in pmadb? -------------------------------------------------------------------------------------------------------------------------- - -Automatic migration of a table's pmadb-style column comments to the -native ones is done whenever you enter Structure page for this table. - -.. _faq6_25: - -6.25 (withdrawn). ------------------ - -.. _faq6_26: - -6.26 How can I select a range of rows? --------------------------------------- - -Click the first row of the range, hold the shift key and click the -last row of the range. This works everywhere you see rows, for example -in Browse mode or on the Structure page. - -.. _faq6_27: - -6.27 What format strings can I use? ------------------------------------ - -In all places where phpMyAdmin accepts format strings, you can use -``@VARIABLE@`` expansion and `strftime <https://www.php.net/strftime>`_ -format strings. The expanded variables depend on a context (for -example, if you haven't chosen a table, you can not get the table -name), but the following variables can be used: - -``@HTTP_HOST@`` - HTTP host that runs phpMyAdmin -``@SERVER@`` - MySQL server name -``@VERBOSE@`` - Verbose MySQL server name as defined in :config:option:`$cfg['Servers'][$i]['verbose']` -``@VSERVER@`` - Verbose MySQL server name if set, otherwise normal -``@DATABASE@`` - Currently opened database -``@TABLE@`` - Currently opened table -``@COLUMNS@`` - Columns of the currently opened table -``@PHPMYADMIN@`` - phpMyAdmin with version - -.. _wysiwyg: - -6.28 How can I easily edit relational schema for export? --------------------------------------------------------- - -By clicking on the button 'toggle scratchboard' on the page where you -edit x/y coordinates of those elements you can activate a scratchboard -where all your elements are placed. By clicking on an element, you can -move them around in the pre-defined area and the x/y coordinates will -get updated dynamically. Likewise, when entering a new position -directly into the input field, the new position in the scratchboard -changes after your cursor leaves the input field. - -You have to click on the 'OK'-button below the tables to save the new -positions. If you want to place a new element, first add it to the -table of elements and then you can drag the new element around. - -By changing the paper size and the orientation you can change the size -of the scratchboard as well. You can do so by just changing the -dropdown field below, and the scratchboard will resize automatically, -without interfering with the current placement of the elements. - -If ever an element gets out of range you can either enlarge the paper -size or click on the 'reset' button to place all elements below each -other. - -.. _faq6_29: - -6.29 Why can't I get a chart from my query result table? --------------------------------------------------------- - -Not every table can be put to the chart. Only tables with one, two or -three columns can be visualised as a chart. Moreover the table must be -in a special format for chart script to understand it. Currently -supported formats can be found in :ref:`charts`. - -.. _faq6_30: - -6.30 Import: How can I import ESRI Shapefiles? ----------------------------------------------- - -An ESRI Shapefile is actually a set of several files, where .shp file -contains geometry data and .dbf file contains data related to those -geometry data. To read data from .dbf file you need to have PHP -compiled with the dBase extension (--enable-dbase). Otherwise only -geometry data will be imported. - -To upload these set of files you can use either of the following -methods: - -Configure upload directory with :config:option:`$cfg['UploadDir']`, upload both .shp and .dbf files with -the same filename and chose the .shp file from the import page. - -Create a zip archive with .shp and .dbf files and import it. For this -to work, you need to set :config:option:`$cfg['TempDir']` to a place where the web server user can -write (for example ``'./tmp'``). - -To create the temporary directory on a UNIX-based system, you can do: - -.. code-block:: sh - - cd phpMyAdmin - mkdir tmp - chmod o+rwx tmp - -.. _faq6_31: - -6.31 How do I create a relation in designer? --------------------------------------------- - -To select relation, click: The display column is shown in pink. To -set/unset a column as the display column, click the "Choose column to -display" icon, then click on the appropriate column name. - -.. _faq6_32: - -6.32 How can I use the zoom search feature? -------------------------------------------- - -The Zoom search feature is an alternative to table search feature. It allows -you to explore a table by representing its data in a scatter plot. You can -locate this feature by selecting a table and clicking the :guilabel:`Search` -tab. One of the sub-tabs in the :guilabel:`Table Search` page is -:guilabel:`Zoom Search`. - -Consider the table REL\_persons in :ref:`faq6_6` for -an example. To use zoom search, two columns need to be selected, for -example, id and town\_code. The id values will be represented on one -axis and town\_code values on the other axis. Each row will be -represented as a point in a scatter plot based on its id and -town\_code. You can include two additional search criteria apart from -the two fields to display. - -You can choose which field should be -displayed as label for each point. If a display column has been set -for the table (see :ref:`faqdisplay`), it is taken as the label unless -you specify otherwise. You can also select the maximum number of rows -you want to be displayed in the plot by specifing it in the 'Max rows -to plot' field. Once you have decided over your criteria, click 'Go' -to display the plot. - -After the plot is generated, you can use the -mousewheel to zoom in and out of the plot. In addition, panning -feature is enabled to navigate through the plot. You can zoom-in to a -certain level of detail and use panning to locate your area of -interest. Clicking on a point opens a dialogue box, displaying field -values of the data row represented by the point. You can edit the -values if required and click on submit to issue an update query. Basic -instructions on how to use can be viewed by clicking the 'How to use?' -link located just above the plot. - -.. _faq6_33: - -6.33 When browsing a table, how can I copy a column name? ---------------------------------------------------------- - -Selecting the name of the column within the browse table header cell -for copying is difficult, as the columns support reordering by -dragging the header cells as well as sorting by clicking on the linked -column name. To copy a column name, double-click on the empty area -next to the column name, when the tooltip tells you to do so. This -will show you an input box with the column name. You may right-click -the column name within this input box to copy it to your clipboard. - -.. _faq6_34: - -6.34 How can I use the Favorite Tables feature? ---------------------------------------------------------- - -Favorite Tables feature is very much similar to Recent Tables feature. -It allows you to add a shortcut for the frequently used tables of any -database in the navigation panel . You can easily navigate to any table -in the list by simply choosing it from the list. These tables are stored -in your browser's local storage if you have not configured your -`phpMyAdmin Configuration Storage`. Otherwise these entries are stored in -`phpMyAdmin Configuration Storage`. - -IMPORTANT: In absence of `phpMyAdmin Configuration Storage`, your Favorite -tables may be different in different browsers based on your different -selections in them. - -To add a table to Favorite list simply click on the `Gray` star in front -of a table name in the list of tables of a Database and wait until it -turns to `Yellow`. -To remove a table from list, simply click on the `Yellow` star and -wait until it turns `Gray` again. - -Using :config:option:`$cfg['NumFavoriteTables']` in your :file:`config.inc.php` -file, you can define the maximum number of favorite tables shown in the -navigation panel. Its default value is `10`. - -.. _faq6_35: - -6.35 How can I use the Range search feature? ---------------------------------------------------------- - -With the help of range search feature, one can specify a range of values for -particular column(s) while performing search operation on a table from the `Search` -tab. - -To use this feature simply click on the `BETWEEN` or `NOT BETWEEN` operators -from the operator select list in front of the column name. On choosing one of the -above options, a dialog box will show up asking for the `Minimum` and `Maximum` -value for that column. Only the specified range of values will be included -in case of `BETWEEN` and excluded in case of `NOT BETWEEN` from the final results. - -Note: The Range search feature will work only `Numeric` and `Date` data type columns. - -.. _faq6_36: - -6.36 What is Central columns and how can I use this feature? ------------------------------------------------------------- - -As the name suggests, the Central columns feature enables to maintain a central list of -columns per database to avoid similar name for the same data element and bring consistency -of data type for the same data element. You can use the central list of columns to -add an element to any table structure in that database which will save from writing -similar column name and column definition. - -To add a column to central list, go to table structure page, check the columns you want -to include and then simply click on "Add to central columns". If you want to add all -unique columns from more than one table from a database then go to database structure page, -check the tables you want to include and then select "Add columns to central list". - -To remove a column from central list, go to Table structure page, check the columns you want -to remove and then simply click on "Remove from central columns". If you want to remove all -columns from more than one tables from a database then go to database structure page, -check the tables you want to include and then select "Remove columns from central list". - -To view and manage the central list, select the database you want to manage central columns -for then from the top menu click on "Central columns". You will be taken to a page where -you will have options to edit, delete or add new columns to central list. - -.. _faq6_37: - -6.37 How can I use Improve Table structure feature? ---------------------------------------------------------- - -Improve table structure feature helps to bring the table structure upto -Third Normal Form. A wizard is presented to user which asks questions about the -elements during the various steps for normalization and a new structure is proposed -accordingly to bring the table into the First/Second/Third Normal form. -On startup of the wizard, user gets to select upto what normal form they want to -normalize the table structure. - -Here is an example table which you can use to test all of the three First, Second and -Third Normal Form. - -.. code-block:: mysql - - CREATE TABLE `VetOffice` ( - `petName` varchar(64) NOT NULL, - `petBreed` varchar(64) NOT NULL, - `petType` varchar(64) NOT NULL, - `petDOB` date NOT NULL, - `ownerLastName` varchar(64) NOT NULL, - `ownerFirstName` varchar(64) NOT NULL, - `ownerPhone1` int(12) NOT NULL, - `ownerPhone2` int(12) NOT NULL, - `ownerEmail` varchar(64) NOT NULL, - ); - -The above table is not in First normal Form as no :term:`primary key` exists. Primary key -is supposed to be (`petName`,`ownerLastName`,`ownerFirstName`) . If the :term:`primary key` -is chosen as suggested the resultant table won't be in Second as well as Third Normal -form as the following dependencies exists. - -.. code-block:: mysql - - (OwnerLastName, OwnerFirstName) -> OwnerEmail - (OwnerLastName, OwnerFirstName) -> OwnerPhone - PetBreed -> PetType - -Which says, OwnerEmail depends on OwnerLastName and OwnerFirstName. -OwnerPhone depends on OwnerLastName and OwnerFirstName. -PetType depends on PetBreed. - -.. _faq6_38: - -6.38 How can I reassign auto-incremented values? ------------------------------------------------- - -Some users prefer their AUTO_INCREMENT values to be consecutive; this is not -always the case after row deletion. - -Here are the steps to accomplish this. These are manual steps because they -involve a manual verification at one point. - -* Ensure that you have exclusive access to the table to rearrange - -* On your :term:`primary key` column (i.e. id), remove the AUTO_INCREMENT setting - -* Delete your primary key in Structure > indexes - -* Create a new column future_id as primary key, AUTO_INCREMENT - -* Browse your table and verify that the new increments correspond to what - you're expecting - -* Drop your old id column - -* Rename the future_id column to id - -* Move the new id column via Structure > Move columns - -.. _faq6_39: - -6.39 What is the "Adjust privileges" option when renaming, copying, or moving a database, table, column, or procedure? ----------------------------------------------------------------------------------------------------------------------- - -When renaming/copying/moving a database/table/column/procedure, -MySQL does not adjust the original privileges relating to these objects -on its own. By selecting this option, phpMyAdmin will adjust the privilege -table so that users have the same privileges on the new items. - -For example: A user 'bob'@'localhost' has a 'SELECT' privilege on a -column named 'id'. Now, if this column is renamed to 'id_new', MySQL, -on its own, would **not** adjust the column privileges to the new column name. -phpMyAdmin can make this adjustment for you automatically. - -Notes: - -* While adjusting privileges for a database, the privileges of all - database-related elements (tables, columns and procedures) are also adjusted - to the database's new name. - -* Similarly, while adjusting privileges for a table, the privileges of all - the columns inside the new table are also adjusted. - -* While adjusting privileges, the user performing the operation **must** have the following - privileges: - - * SELECT, INSERT, UPDATE, DELETE privileges on following tables: - `mysql`.`db`, `mysql`.`columns_priv`, `mysql`.`tables_priv`, `mysql`.`procs_priv` - * FLUSH privilege (GLOBAL) - -Thus, if you want to replicate the database/table/column/procedure as it is -while renaming/copying/moving these objects, make sure you have checked this option. - -.. _faq6_40: - -6.40 I see "Bind parameters" checkbox in the "SQL" page. How do I write parameterized SQL queries? --------------------------------------------------------------------------------------------------- - -From version 4.5, phpMyAdmin allows users to execute parameterized queries in the "SQL" page. -Parameters should be prefixed with a colon(:) and when the "Bind parameters" checkbox is checked -these parameters will be identified and input fields for these parameters will be presented. -Values entered in these field will be substituted in the query before being executed. - -.. _faq6_41: - -6.41 I get import errors while importing the dumps exported from older MySQL versions (pre-5.7.6) into newer MySQL versions (5.7.7+), but they work fine when imported back on same older versions ? --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- - -If you get errors like *#1031 - Table storage engine for 'table_name' doesn't have this option* -while importing the dumps exported from pre-5.7.7 MySQL servers into new MySQL server versions 5.7.7+, -it might be because ROW_FORMAT=FIXED is not supported with InnoDB tables. Moreover, the value of -`innodb_strict_mode <https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_strict_mode>`_ would define if this would be reported as a warning or as an error. - -Since MySQL version 5.7.9, the default value for `innodb_strict_mode` is `ON` and thus would generate -an error when such a CREATE TABLE or ALTER TABLE statement is encountered. - -There are two ways of preventing such errors while importing: - -* Change the value of `innodb_strict_mode` to `OFF` before starting the import and turn it `ON` after - the import is successfully completed. -* This can be achieved in two ways: - - * Go to 'Variables' page and edit the value of `innodb_strict_mode` - * Run the query : `SET GLOBAL `innodb_strict_mode` = '[value]'` - -After the import is done, it is suggested that the value of `innodb_strict_mode` should be reset to the -original value. - -.. _faqproject: - -phpMyAdmin project -++++++++++++++++++ - -.. _faq7_1: - -7.1 I have found a bug. How do I inform developers? ---------------------------------------------------- - -Our issues tracker is located at <https://github.com/phpmyadmin/phpmyadmin/issues>. -For security issues, please refer to the instructions at <https://www.phpmyadmin.net/security> to email -the developers directly. - -.. _faq7_2: - -7.2 I want to translate the messages to a new language or upgrade an existing language, where do I start? ---------------------------------------------------------------------------------------------------------- - -Translations are very welcome and all you need to have are the -language skills. The easiest way is to use our `online translation -service <https://hosted.weblate.org/projects/phpmyadmin/>`_. You can check -out all the possibilities to translate in the `translate section on -our website <https://www.phpmyadmin.net/translate/>`_. - -.. _faq7_3: - -7.3 I would like to help out with the development of phpMyAdmin. How should I proceed? --------------------------------------------------------------------------------------- - -We welcome every contribution to the development of phpMyAdmin. You -can check out all the possibilities to contribute in the `contribute -section on our website -<https://www.phpmyadmin.net/contribute/>`_. - -.. seealso:: :ref:`developers` - -.. _faqsecurity: - -Security -++++++++ - -.. _faq8_1: - -8.1 Where can I get information about the security alerts issued for phpMyAdmin? --------------------------------------------------------------------------------- - -Please refer to <https://www.phpmyadmin.net/security/>. - -.. _faq8_2: - -8.2 How can I protect phpMyAdmin against brute force attacks? -------------------------------------------------------------- - -If you use Apache web server, phpMyAdmin exports information about -authentication to the Apache environment and it can be used in Apache -logs. Currently there are two variables available: - -``userID`` - User name of currently active user (he does not have to be logged in). -``userStatus`` - Status of currently active user, one of ``ok`` (user is logged in), - ``mysql-denied`` (MySQL denied user login), ``allow-denied`` (user denied - by allow/deny rules), ``root-denied`` (root is denied in configuration), - ``empty-denied`` (empty password is denied). - -``LogFormat`` directive for Apache can look like following: - -.. code-block:: apache - - LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %{userID}n %{userStatus}n" pma_combined - -You can then use any log analyzing tools to detect possible break-in -attempts. - -.. _faq8_3: - -8.3 Why are there path disclosures when directly loading certain files? ------------------------------------------------------------------------ - -This is a server configuration problem. Never enable ``display_errors`` on a production site. - -.. _faq8_4: - -8.4 CSV files exported from phpMyAdmin could allow a formula injection attack. ------------------------------------------------------------------------------- - -It is possible to generate a :term:`CSV` file that, when imported to a spreadsheet program such as Microsoft Excel, -could potentially allow the execution of arbitrary commands. - -The CSV files generated by phpMyAdmin could potentially contain text that would be interpreted by a spreadsheet program as -a formula, but we do not believe escaping those fields is the proper behavior. There is no means to properly escape and -differentiate between a desired text output and a formula that should be escaped, and CSV is a text format where function -definitions should not be interpreted anyway. We have discussed this at length and feel it is the responsibility of the -spreadsheet program to properly parse and sanitize such data on input instead. - -Google also has a `similar view <https://sites.google.com/site/bughunteruniversity/nonvuln/csv-excel-formula-injection>`_. - -.. _faqsynchronization: - -Synchronization -+++++++++++++++ - -.. _faq9_1: - -9.1 (withdrawn). ----------------- - -.. _faq9_2: - -9.2 (withdrawn). ----------------- diff --git a/srcs/phpmyadmin/doc/html/_sources/glossary.txt b/srcs/phpmyadmin/doc/html/_sources/glossary.txt deleted file mode 100644 index e117ff5..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/glossary.txt +++ /dev/null @@ -1,432 +0,0 @@ -.. _glossary: - -Glossary -======== - -From Wikipedia, the free encyclopedia - -.. glossary:: - - .htaccess - the default name of Apache's directory-level configuration file. - - .. seealso:: <https://en.wikipedia.org/wiki/.htaccess> - - ACL - Access Control List - - Blowfish - a keyed, symmetric block cipher, designed in 1993 by Bruce Schneier. - - .. seealso:: <https://en.wikipedia.org/wiki/Blowfish_(cipher)> - - Browser - a software application that enables a user to display and interact with text, images, and other information typically located on a web page at a website on the World Wide Web. - - .. seealso:: <https://en.wikipedia.org/wiki/Web_browser> - - bzip2 - a free software/open-source data compression algorithm and program developed by Julian Seward. - - .. seealso:: <https://en.wikipedia.org/wiki/Bzip2> - - CGI - Common Gateway Interface is an important World Wide Web technology that - enables a client web browser to request data from a program executed on - the Web server. - - .. seealso:: <https://en.wikipedia.org/wiki/Common_Gateway_Interface> - - Changelog - a log or record of changes made to a project. - - .. seealso:: <https://en.wikipedia.org/wiki/Changelog> - - Client - a computer system that accesses a (remote) service on another computer by some kind of network. - - .. seealso:: <https://en.wikipedia.org/wiki/Client_(computing)> - - column - a set of data values of a particularly simple type, one for each row of the table. - - .. seealso:: <https://en.wikipedia.org/wiki/Column_(database)> - - Cookie - a packet of information sent by a server to a World Wide Web browser and then sent back by the browser each time it accesses that server. - - .. seealso:: <https://en.wikipedia.org/wiki/HTTP_cookie> - - CSV - Comma-separated values - - .. seealso:: <https://en.wikipedia.org/wiki/Comma-separated_values> - - DB - look at :term:`database` - - database - an organized collection of data. - - .. seealso:: <https://en.wikipedia.org/wiki/Database> - - Engine - look at :term:`storage engines` - - extension - a PHP module that extends PHP with additional functionality. - - .. seealso:: <https://en.wikipedia.org/wiki/Software_extension> - - FAQ - Frequently Asked Questions is a list of commonly asked question and there - answers. - - .. seealso:: <https://en.wikipedia.org/wiki/FAQ> - - Field - one part of divided data/columns. - - .. seealso:: <https://en.wikipedia.org/wiki/Field_(computer_science)> - - foreign key - a column or group of columns in a database row that points to a key column - or group of columns forming a key of another database row in some - (usually different) table. - - .. seealso:: <https://en.wikipedia.org/wiki/Foreign_key> - - GD - Graphics Library by Thomas Boutell and others for dynamically manipulating images. - - .. seealso:: <https://en.wikipedia.org/wiki/GD_Graphics_Library> - - GD2 - look at :term:`gd` - - gzip - gzip is short for GNU zip, a GNU free software file compression program. - - .. seealso:: <https://en.wikipedia.org/wiki/Gzip> - - host - any machine connected to a computer network, a node that has a hostname. - - .. seealso:: <https://en.wikipedia.org/wiki/Host> - - hostname - the unique name by which a network-attached device is known on a network. - - .. seealso:: <https://en.wikipedia.org/wiki/Hostname> - - HTTP - HyperText Transfer Protocol is the primary method used to transfer or - convey information on the World Wide Web. - - .. seealso:: <https://en.wikipedia.org/wiki/HyperText_Transfer_Protocol> - - https - a :term:`HTTP`-connection with additional security measures. - - .. seealso:: <https://en.wikipedia.org/wiki/Https:_URI_scheme> - - IEC - International Electrotechnical Commission - - IIS - Internet Information Services is a set of Internet-based services for - servers using Microsoft Windows. - - .. seealso:: <https://en.wikipedia.org/wiki/Internet_Information_Services> - - Index - a feature that allows quick access to the rows in a table. - - .. seealso:: <https://en.wikipedia.org/wiki/Index_(database)> - - IP - Internet Protocol is a data-oriented protocol used by source and - destination hosts for communicating data across a packet-switched - internetwork. - - .. seealso:: <https://en.wikipedia.org/wiki/Internet_Protocol> - - IP Address - a unique number that devices use in order to identify and communicate with each other on a network utilizing the Internet Protocol standard. - - .. seealso:: <https://en.wikipedia.org/wiki/IP_Address> - - IPv6 - IPv6 (Internet Protocol version 6) is the latest revision of the - Internet Protocol (:term:`IP`), designed to deal with the - long-anticipated problem of its predecessor IPv4 running out of addresses. - - .. seealso:: <https://en.wikipedia.org/wiki/IPv6> - - ISAPI - Internet Server Application Programming Interface is the API of Internet Information Services (IIS). - - .. seealso:: <https://en.wikipedia.org/wiki/ISAPI> - - ISP - An Internet service provider is a business or organization that offers users - access to the Internet and related services. - - .. seealso:: <https://en.wikipedia.org/wiki/ISP> - - ISO - International Standards Organisation - - JPEG - a most commonly used standard method of lossy compression for photographic images. - - .. seealso:: <https://en.wikipedia.org/wiki/JPEG> - - JPG - look at :term:`jpeg` - - Key - look at :term:`index` - - LATEX - a document preparation system for the TEX typesetting program. - - .. seealso:: <https://en.wikipedia.org/wiki/LaTeX> - - Mac - Apple Macintosh is a line of personal computers is designed, developed, manufactured, and marketed by Apple Computer. - - .. seealso:: <https://en.wikipedia.org/wiki/Mac> - - Mac OS X - the operating system which is included with all currently shipping Apple Macintosh computers in the consumer and professional markets. - - .. seealso:: <https://en.wikipedia.org/wiki/Mac_OS_X> - - mbstring - The PHP `mbstring` functions provide support for languages represented by multi-byte character sets, most notably UTF-8. - - If you have troubles installing this extension, please follow :ref:`faqmysql`, it provides useful hints. - - .. seealso:: <https://www.php.net/manual/en/book.mbstring.php> - - MCrypt - a cryptographic library. - - .. seealso:: <https://en.wikipedia.org/wiki/MCrypt> - - mcrypt - the MCrypt PHP extension. - - .. seealso:: <https://www.php.net/mcrypt> - - Media type - A media type (formerly known as MIME type) is a two-part identifier - for file formats and format contents transmitted on the Internet. - - .. seealso:: <https://en.wikipedia.org/wiki/Media_type> - - MIME - Multipurpose Internet Mail Extensions is - an Internet Standard for the format of e-mail. - - .. seealso:: <https://en.wikipedia.org/wiki/MIME> - - module - some sort of extension for the Apache Webserver. - - .. seealso:: <https://en.wikipedia.org/wiki/Apache_HTTP_Server> - - mod_proxy_fcgi - an Apache module implementing a Fast CGI interface; PHP can be run as a CGI module, FastCGI, or - directly as an Apache module. - - MySQL - a multithreaded, multi-user, SQL (Structured Query Language) Database Management System (DBMS). - - .. seealso:: <https://en.wikipedia.org/wiki/MySQL> - - mysqli - the improved MySQL client PHP extension. - - .. seealso:: <https://www.php.net/manual/en/book.mysqli.php> - - mysql - the MySQL client PHP extension. - - .. seealso:: <https://www.php.net/manual/en/book.mysql.php> - - OpenDocument - an open standard for office documents. - - .. seealso:: <https://en.wikipedia.org/wiki/OpenDocument> - - OS X - look at :term:`Mac OS X`. - - .. seealso:: <https://en.wikipedia.org/wiki/OS_X> - - PDF - Portable Document Format is a file format developed by Adobe Systems for - representing two-dimensional documents in a device-independent and - resolution-independent format. - - .. seealso:: <https://en.wikipedia.org/wiki/Portable_Document_Format> - - PEAR - the PHP Extension and Application Repository. - - .. seealso:: <https://pear.php.net/> - - PCRE - Perl Compatible Regular Expressions is the perl-compatible regular - expression functions for PHP - - .. seealso:: <https://www.php.net/pcre> - - PHP - short for "PHP: Hypertext Preprocessor", is an open-source, reflective - programming language used mainly for developing server-side applications - and dynamic web content, and more recently, a broader range of software - applications. - - .. seealso:: <https://en.wikipedia.org/wiki/PHP> - - port - a connection through which data is sent and received. - - .. seealso:: <https://en.wikipedia.org/wiki/Port_(computing)> - - primary key - A primary key is an index over one or more fields in a table with - unique values for every single row in this table. Every table should have - a primary key for easier accessing/identifying data in this table. There - can only be one primary key per table and it is named always **PRIMARY**. - In fact, a primary key is just an :term:`unique key` with the name - **PRIMARY**. If no primary key is defined MySQL will use first *unique - key* as primary key if there is one. - - You can create the primary key when creating the table (in phpMyAdmin - just check the primary key radio buttons for each field you wish to be - part of the primary key). - - You can also add a primary key to an existing table with `ALTER` `TABLE` - or `CREATE` `INDEX` (in phpMyAdmin you can just click on 'add index' on - the table structure page below the listed fields). - - RFC - Request for Comments (RFC) documents are a series of memoranda - encompassing new research, innovations, and methodologies applicable to - Internet technologies. - - .. seealso:: <https://en.wikipedia.org/wiki/Request_for_Comments> - - RFC 1952 - GZIP file format specification version 4.3 - - .. seealso:: :rfc:`1952` - - Row (record, tuple) - represents a single, implicitly structured data item in a table. - - .. seealso:: <https://en.wikipedia.org/wiki/Row_(database)> - - Server - a computer system that provides services to other computing systems over a network. - - .. seealso:: <https://en.wikipedia.org/wiki/Server_(computing)> - - Storage Engines - MySQL can use several different formats for storing data on disk, these - are called storage engines or table types. phpMyAdmin allows a user to - change their storage engine for a particular table through the operations - tab. - - Common table types are InnoDB and MyISAM, though many others exist and - may be desirable in some situations. - - .. seealso:: <https://dev.mysql.com/doc/refman/5.7/en/storage-engines.html> - - socket - a form of inter-process communication. - - .. seealso:: <https://en.wikipedia.org/wiki/Unix_domain_socket> - - SSL - Secure Sockets Layer is a cryptographic protocol which provides secure - communication on the Internet. - - .. seealso:: <https://en.wikipedia.org/wiki/Secure_Sockets_Layer> - - Stored procedure - a subroutine available to applications accessing a relational database system - - .. seealso:: <https://en.wikipedia.org/wiki/Stored_procedure> - - SQL - Structured Query Language - - .. seealso:: <https://en.wikipedia.org/wiki/SQL> - - table - a set of data elements (cells) that is organized, defined and stored as - horizontal rows and vertical columns where each item can be uniquely - identified by a label or key or by it's position in relation to other - items. - - .. seealso:: <https://en.wikipedia.org/wiki/Table_(database)> - - tar - a type of archive file format: the Tape ARchive format. - - .. seealso:: <https://en.wikipedia.org/wiki/Tar_(file_format)> - - TCP - Transmission Control Protocol is one of the core protocols of the - Internet protocol suite. - - .. seealso:: <https://en.wikipedia.org/wiki/TCP> - - TCPDF - PHP library to generate PDF files. - - .. seealso:: <https://tcpdf.org/> - - trigger - a procedural code that is automatically executed in response to certain events on a particular table or view in a database - - .. seealso:: <https://en.wikipedia.org/wiki/Database_trigger> - - unique key - A unique key is an index over one or more fields in a table which has a - unique value for each row. The first unique key will be treated as - :term:`primary key` if there is no *primary key* defined. - - URL - Uniform Resource Locator is a sequence of characters, conforming to a - standardized format, that is used for referring to resources, such as - documents and images on the Internet, by their location. - - .. seealso:: <https://en.wikipedia.org/wiki/URL> - - Webserver - A computer (program) that is responsible for accepting HTTP requests from clients and serving them Web pages. - - .. seealso:: <https://en.wikipedia.org/wiki/Webserver> - - XML - Extensible Markup Language is a W3C-recommended general-purpose markup - language for creating special-purpose markup languages, capable of - describing many different kinds of data. - - .. seealso:: <https://en.wikipedia.org/wiki/XML> - - ZIP - a popular data compression and archival format. - - .. seealso:: <https://en.wikipedia.org/wiki/ZIP_(file_format)> - - zlib - an open-source, cross-platform data compression library by Jean-loup Gailly and Mark Adler. - - .. seealso:: <https://en.wikipedia.org/wiki/Zlib> diff --git a/srcs/phpmyadmin/doc/html/_sources/import_export.txt b/srcs/phpmyadmin/doc/html/_sources/import_export.txt deleted file mode 100644 index 31f2fa9..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/import_export.txt +++ /dev/null @@ -1,350 +0,0 @@ -Import and export -================= - -Import -++++++ - -To import data, go to the "Import" tab in phpMyAdmin. To import data into a -specific database or table, open the database or table before going to the -"Import" tab. - -In addition to the standard Import and Export tab, you can also import an SQL -file directly by dragging and dropping it from your local file manager to the -phpMyAdmin interface in your web browser. - -If you are having troubles importing big files, please consult :ref:`faq1_16`. - -You can import using following methods: - -Form based upload - - Can be used with any supported format, also (b|g)zipped files, e.g., mydump.sql.gz . - -Form based SQL Query - - Can be used with valid SQL dumps. - -Using upload directory - - You can specify an upload directory on your web server where phpMyAdmin is installed, after uploading your file into this directory you can select this file in the import dialog of phpMyAdmin, see :config:option:`$cfg['UploadDir']`. - -phpMyAdmin can import from several various commonly used formats. - -CSV ---- - -Comma separated values format which is often used by spreadsheets or various other programs for export/import. - -.. note:: - - When importing data into a table from a CSV file where the table has an - 'auto_increment' field, make the 'auto_increment' value for each record in - the CSV field to be '0' (zero). This allows the 'auto_increment' field to - populate correctly. - -It is now possible to import a CSV file at the server or database level. -Instead of having to create a table to import the CSV file into, a best-fit -structure will be determined for you and the data imported into it, instead. -All other features, requirements, and limitations are as before. - -CSV using LOAD DATA -------------------- - -Similar to CSV, only using the internal MySQL parser and not the phpMyAdmin one. - -ESRI Shape File ---------------- - -The ESRI shapefile or simply a shapefile is a popular geospatial vector data -format for geographic information systems software. It is developed and -regulated by Esri as a (mostly) open specification for data interoperability -among Esri and other software products. - -MediaWiki ---------- - -MediaWiki files, which can be exported by phpMyAdmin (version 4.0 or later), -can now also be imported. This is the format used by Wikipedia to display -tables. - -Open Document Spreadsheet (ODS) -------------------------------- - -OpenDocument workbooks containing one or more spreadsheets can now be directly imported. - -When importing an ODS speadsheet, the spreadsheet must be named in a specific way in order to make the -import as simple as possible. - -Table name -~~~~~~~~~~ - -During import, phpMyAdmin uses the sheet name as the table name; you should rename the -sheet in your spreadsheet program in order to match your existing table name (or the table you wish to create, -though this is less of a concern since you could quickly rename the new table from the Operations tab). - -Column names -~~~~~~~~~~~~ - -You should also make the first row of your spreadsheet a header with the names of the columns (this can be -accomplished by inserting a new row at the top of your spreadsheet). When on the Import screen, select the -checkbox for "The first line of the file contains the table column names;" this way your newly imported -data will go to the proper columns. - -.. note:: - - Formulas and calculations will NOT be evaluated, rather, their value from - the most recent save will be loaded. Please ensure that all values in the - spreadsheet are as needed before importing it. - -SQL ---- - -SQL can be used to make any manipulation on data, it is also useful for restoring backed up data. - -XML ---- - -XML files exported by phpMyAdmin (version 3.3.0 or later) can now be imported. -Structures (databases, tables, views, triggers, etc.) and/or data will be -created depending on the contents of the file. - -The supported xml schemas are not yet documented in this wiki. - -Export -++++++ - -phpMyAdmin can export into text files (even compressed) on your local disk (or -a special the webserver :config:option:`$cfg['SaveDir']` folder) in various -commonly used formats: - -CodeGen -------- - -`NHibernate <https://en.wikipedia.org/wiki/NHibernate>`_ file format. Planned -versions: Java, Hibernate, PHP PDO, JSON, etc. So the preliminary name is -codegen. - -CSV ---- - -Comma separated values format which is often used by spreadsheets or various -other programs for export/import. - -CSV for Microsoft Excel ------------------------ - -This is just preconfigured version of CSV export which can be imported into -most English versions of Microsoft Excel. Some localised versions (like -"Danish") are expecting ";" instead of "," as field separator. - -Microsoft Word 2000 -------------------- - -If you're using Microsoft Word 2000 or newer (or compatible such as -OpenOffice.org), you can use this export. - -JSON ----- - -JSON (JavaScript Object Notation) is a lightweight data-interchange format. It -is easy for humans to read and write and it is easy for machines to parse and -generate. - -.. versionchanged:: 4.7.0 - - The generated JSON structure has been changed in phpMyAdmin 4.7.0 to - produce valid JSON data. - -The generated JSON is list of objects with following attributes: - -.. js:data:: type - - Type of given object, can be one of: - - ``header`` - Export header containing comment and phpMyAdmin version. - ``database`` - Start of a database marker, containing name of database. - ``table`` - Table data export. - -.. js:data:: version - - Used in ``header`` :js:data:`type` and indicates phpMyAdmin version. - -.. js:data:: comment - - Optional textual comment. - -.. js:data:: name - - Object name - either table or database based on :js:data:`type`. - -.. js:data:: database - - Database name for ``table`` :js:data:`type`. - -.. js:data:: data - - Table content for ``table`` :js:data:`type`. - -Sample output: - -.. code-block:: json - - [ - { - "comment": "Export to JSON plugin for PHPMyAdmin", - "type": "header", - "version": "4.7.0-dev" - }, - { - "name": "cars", - "type": "database" - }, - { - "data": [ - { - "car_id": "1", - "description": "Green Chrysler 300", - "make_id": "5", - "mileage": "113688", - "price": "13545.00", - "transmission": "automatic", - "yearmade": "2007" - } - ], - "database": "cars", - "name": "cars", - "type": "table" - }, - { - "data": [ - { - "make": "Chrysler", - "make_id": "5" - } - ], - "database": "cars", - "name": "makes", - "type": "table" - } - ] - -LaTeX ------ - -If you want to embed table data or structure in LaTeX, this is right choice for you. - -LaTeX is a typesetting system that is very suitable for producing scientific -and mathematical documents of high typographical quality. It is also suitable -for producing all sorts of other documents, from simple letters to complete -books. LaTeX uses TeX as its formatting engine. Learn more about TeX and -LaTeX on `the Comprehensive TeX Archive Network <https://www.ctan.org/>`_ -also see the `short description od TeX <https://www.ctan.org/tex/>`_. - -The output needs to be embedded into a LaTeX document before it can be -rendered, for example in following document: - -.. code-block:: latex - - \documentclass{article} - \title{phpMyAdmin SQL output} - \author{} - \usepackage{longtable,lscape} - \date{} - \setlength{\parindent}{0pt} - \usepackage[left=2cm,top=2cm,right=2cm,nohead,nofoot]{geometry} - \pdfpagewidth 210mm - \pdfpageheight 297mm - \begin{document} - \maketitle - - % insert phpMyAdmin LaTeX Dump here - - \end{document} - -MediaWiki ---------- - -Both tables and databases can be exported in the MediaWiki format, which is -used by Wikipedia to display tables. It can export structure, data or both, -including table names or headers. - -OpenDocument Spreadsheet ------------------------- - -Open standard for spreadsheet data, which is being widely adopted. Many recent -spreadsheet programs, such as LibreOffice, OpenOffice, Microsoft Office or -Google Docs can handle this format. - -OpenDocument Text ------------------ - -New standard for text data which is being widely addopted. Most recent word -processors (such as LibreOffice, OpenOffice, Microsoft Word, AbiWord or KWord) -can handle this. - -PDF ---- - -For presentation purposes, non editable PDF might be best choice for you. - -PHP Array ---------- - -You can generate a php file which will declare a multidimensional array with -the contents of the selected table or database. - -SQL ---- - -Export in SQL can be used to restore your database, thus it is useful for -backing up. - -The option 'Maximal length of created query' seems to be undocumented. But -experiments has shown that it splits large extended INSERTS so each one is no -bigger than the given number of bytes (or characters?). Thus when importing the -file, for large tables you avoid the error "Got a packet bigger than -'max_allowed_packet' bytes". - -.. seealso:: - - https://dev.mysql.com/doc/refman/5.7/en/packet-too-large.html - -Data Options -~~~~~~~~~~~~ - -**Complete inserts** adds the column names to the SQL dump. This parameter -improves the readability and reliability of the dump. Adding the column names -increases the size of the dump, but when combined with Extended inserts it's -negligible. - -**Extended inserts** combines multiple rows of data into a single INSERT query. -This will significantly decrease filesize for large SQL dumps, increases the -INSERT speed when imported, and is generally recommended. - -.. seealso:: - - http://www.scriptalicious.com/blog/2009/04/complete-inserts-or-extended-inserts-in-phpmyadmin/ - -Texy! ------ - -`Texy! <https://texy.info/>`_ markup format. You can see example on `Texy! demo -<https://texy.info/en/try/4q5we>`_. - -XML ---- - -Easily parsable export for use with custom scripts. - -.. versionchanged:: 3.3.0 - - The XML schema used has changed as of version 3.3.0 - -YAML ----- - -YAML is a data serialization format which is both human readable and -computationally powerful ( <https://yaml.org> ). diff --git a/srcs/phpmyadmin/doc/html/_sources/index.txt b/srcs/phpmyadmin/doc/html/_sources/index.txt deleted file mode 100644 index f337241..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/index.txt +++ /dev/null @@ -1,32 +0,0 @@ -.. phpMyAdmin documentation master file, created by - sphinx-quickstart on Wed Sep 26 14:04:48 2012. - You can adapt this file completely to your liking, but it should at least - contain the root `toctree` directive. - -Welcome to phpMyAdmin's documentation! -====================================== - -Contents: - -.. toctree:: - :maxdepth: 2 - - intro - require - setup - config - user - faq - developers - security - vendors - copyright - credits - glossary - -Indices and tables -================== - -* :ref:`genindex` -* :ref:`search` -* :ref:`glossary` diff --git a/srcs/phpmyadmin/doc/html/_sources/intro.txt b/srcs/phpmyadmin/doc/html/_sources/intro.txt deleted file mode 100644 index d81b00e..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/intro.txt +++ /dev/null @@ -1,79 +0,0 @@ -.. _intro: - -Introduction -============ - -phpMyAdmin is a free software tool written in PHP that is intended to handle the -administration of a MySQL or MariaDB database server. You can use phpMyAdmin to -perform most administration tasks, including creating a database, running queries, -and adding user accounts. - -Supported features ------------------- - -Currently phpMyAdmin can: - -* create, browse, edit, and drop databases, tables, views, columns, and indexes -* display multiple results sets through stored procedures or queries -* create, copy, drop, rename and alter databases, tables, columns and - indexes -* maintenance server, databases and tables, with proposals on server - configuration -* execute, edit and bookmark any :term:`SQL`-statement, even batch-queries -* load text files into tables -* create [#f1]_ and read dumps of tables -* export [#f1]_ data to various formats: :term:`CSV`, :term:`XML`, :term:`PDF`, - :term:`ISO`/:term:`IEC` 26300 - :term:`OpenDocument` Text and Spreadsheet, Microsoft - Word 2000, and LATEX formats -* import data and :term:`MySQL` structures from :term:`OpenDocument` spreadsheets, as - well as :term:`XML`, :term:`CSV`, and :term:`SQL` files -* administer multiple servers -* add, edit, and remove MySQL user accounts and privileges -* check referential integrity in MyISAM tables -* using Query-by-example (QBE), create complex queries automatically - connecting required tables -* create :term:`PDF` graphics of your - database layout -* search globally in a database or a subset of it -* transform stored data into any format using a set of predefined - functions, like displaying BLOB-data as image or download-link -* track changes on databases, tables and views -* support InnoDB tables and foreign keys -* support mysqli, the improved MySQL extension see :ref:`faq1_17` -* create, edit, call, export and drop stored procedures and functions -* create, edit, export and drop events and triggers -* communicate in `80 different languages - <https://www.phpmyadmin.net/translations/>`_ - -Shortcut keys -------------- - -Currently phpMyAdmin supports following shortcuts: - -* k - Toggle console -* h - Go to home page -* s - Open settings -* d + s - Go to database structure (Provided you are in database related page) -* d + f - Search database (Provided you are in database related page) -* t + s - Go to table structure (Provided you are in table related page) -* t + f - Search table (Provided you are in table related page) -* backspace - Takes you to older page. - -A word about users ------------------- - -Many people have difficulty understanding the concept of user -management with regards to phpMyAdmin. When a user logs in to -phpMyAdmin, that username and password are passed directly to MySQL. -phpMyAdmin does no account management on its own (other than allowing -one to manipulate the MySQL user account information); all users must -be valid MySQL users. - -.. rubric:: Footnotes - -.. [#f1] - - phpMyAdmin can compress (:term:`Zip`, :term:`GZip` or :term:`RFC 1952` - formats) dumps and :term:`CSV` exports if you use PHP with - :term:`Zlib` support (``--with-zlib``). - Proper support may also need changes in :file:`php.ini`. diff --git a/srcs/phpmyadmin/doc/html/_sources/other.txt b/srcs/phpmyadmin/doc/html/_sources/other.txt deleted file mode 100644 index 98d1dca..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/other.txt +++ /dev/null @@ -1,32 +0,0 @@ -Other sources of information -============================ - -Printed Book ------------- - -The definitive guide to using phpMyAdmin is the book Mastering phpMyAdmin for -Effective MySQL Management by Marc Delisle. You can get information on that -book and other officially endorsed `books at the phpMyAdmin site`_. - -.. _books at the phpMyAdmin site: https://www.phpmyadmin.net/docs/ - -Tutorials ---------- - -Third party tutorials and articles which you might find interesting: - -Česky (Czech) -+++++++++++++ - -- `Seriál o phpMyAdminovi <https://cihar.com/publications/linuxsoft/>`_ - -English -+++++++ - -- `Having fun with phpMyAdmin's MIME-transformations & PDF-features <https://garv.in/tops/texte/mimetutorial>`_ -- `Learning SQL Using phpMyAdmin (old tutorial) <http://www.php-editors.com/articles/sql_phpmyadmin.php>`_ - -Русский (Russian) -+++++++++++++++++ - -* `Russian server about phpMyAdmin <https://php-myadmin.ru/>`_ diff --git a/srcs/phpmyadmin/doc/html/_sources/privileges.txt b/srcs/phpmyadmin/doc/html/_sources/privileges.txt deleted file mode 100644 index f3b1779..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/privileges.txt +++ /dev/null @@ -1,74 +0,0 @@ -User management -=============== - -User management is the process of controlling which users are allowed to -connect to the MySQL server and what permissions they have on each database. -phpMyAdmin does not handle user management, rather it passes the username and -password on to MySQL, which then determines whether a user is permitted to -perform a particular action. Within phpMyAdmin, administrators have full -control over creating users, viewing and editing privileges for existing users, -and removing users. - -Within phpMyAdmin, user management is controlled via the :guilabel:`Users` link -from the main page. Users can be created, edited, and removed. - -Creating a new user -------------------- - -To create a new user, click the :guilabel:`Add a new user` link near the bottom -of the :guilabel:`Users` page (you must be a "superuser", e.g., user "root"). -Use the textboxes and drop-downs to configure the user to your particular -needs. You can then select whether to create a database for that user and grant -specific global privileges. Once you've created the user (by clicking Go), you -can define that user's permissions on a specific database (don't grant global -privileges in that case). In general, users do not need any global privileges -(other than USAGE), only permissions for their specific database. - -Editing an existing user ------------------------- - -To edit an existing user, simply click the pencil icon to the right of that -user in the :guilabel:`Users` page. You can then edit their global- and -database-specific privileges, change their password, or even copy those -privileges to a new user. - -Deleting a user ---------------- - -From the :guilabel:`Users` page, check the checkbox for the user you wish to -remove, select whether or not to also remove any databases of the same name (if -they exist), and click Go. - -Assigning privileges to user for a specific database ----------------------------------------------------- - -Users are assigned to databases by editing the user record (from the -:guilabel:`User accounts` link on the home page). -If you are creating a user specifically for a given table -you will have to create the user first (with no global privileges) and then go -back and edit that user to add the table and privileges for the individual -table. - -.. _configurablemenus: - -Configurable menus and user groups ----------------------------------- - -By enabling :config:option:`$cfg['Servers'][$i]['usergroups']` and -:config:option:`$cfg['Servers'][$i]['usergroups']` you can customize what users -will see in the phpMyAdmin navigation. - -.. warning:: - - This feature only limits what a user sees, he is still able to use all the - functions. So this can not be considered as a security limitation. Should - you want to limit what users can do, use MySQL privileges to achieve that. - -With this feature enabled, the :guilabel:`User accounts` management interface gains -a second tab for managing :guilabel:`User groups`, where you can define what each -group will view (see image below) and you can then assign each user to one of -these groups. Users will be presented with a simplified user interface, which might be -useful for inexperienced users who could be overwhelmed by all the features -phpMyAdmin provides. - -.. image:: images/usergroups.png diff --git a/srcs/phpmyadmin/doc/html/_sources/relations.txt b/srcs/phpmyadmin/doc/html/_sources/relations.txt deleted file mode 100644 index 96643de..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/relations.txt +++ /dev/null @@ -1,84 +0,0 @@ -.. _relations: - -Relations -========= - -phpMyAdmin allows relationships (similar to foreign keys) using MySQL-native -(InnoDB) methods when available and falling back on special phpMyAdmin-only -features when needed. There are two ways of editing these relations, with the -*relation view* and the drag-and-drop *designer* -- both of which are explained -on this page. - -.. note:: - - You need to have configured the :ref:`linked-tables` for using phpMyAdmin - only relations. - -Technical info --------------- - -Currently the only MySQL table type that natively supports relationships is -InnoDB. When using an InnoDB table, phpMyAdmin will create real InnoDB -relations which will be enforced by MySQL no matter which application accesses -the database. In the case of any other table type, phpMyAdmin enforces the -relations internally and those relations are not applied to any other -application. - -Relation view -------------- - -In order to get it working, you first have to properly create the -[[pmadb|pmadb]]. Once that is setup, select a table's "Structure" page. Below -the table definition, a link called "Relation view" is shown. If you click that -link, a page will be shown that offers you to create a link to another table -for any (most) fields. Only PRIMARY KEYS are shown there, so if the field you -are referring to is not shown, you most likely are doing something wrong. The -drop-down at the bottom is the field which will be used as the name for a -record. - -Relation view example -+++++++++++++++++++++ - -.. image:: images/pma-relations-relation-view-link.png - -.. image:: images/pma-relations-relation-link.png - -Let's say you have categories and links and one category can contain several links. Your table structure would be something like this: - -- `category.category_id` (must be unique) -- `category.name` -- `link.link_id` -- `link.category_id` -- `link.uri`. - -Open the relation view (below the table structure) page for the `link` table and for `category_id` field, you select `category.category_id` as master record. - -If you now browse the link table, the `category_id` field will be a clickable hyperlink to the proper category record. But all you see is just the `category_id`, not the name of the category. - -.. image:: images/pma-relations-relation-name.png - -To fix this, open the relation view of the `category` table and in the drop down at the bottom, select "name". If you now browse the link table again and hover the mouse over the `category_id` hyperlink, the value from the related category will be shown as tooltip. - -.. image:: images/pma-relations-links.png - -Designer --------- - -The Designer feature is a graphical way of creating, editing, and displaying -phpMyAdmin relations. These relations are compatible with those created in -phpMyAdmin's relation view. - -To use this feature, you need a properly configured :ref:`linked-tables` and -must have the :config:option:`$cfg['Servers'][$i]['table_coords']` configured. - -To use the designer, select a database's structure page, then look for the -:guilabel:`Designer` tab. - -To export the view into PDF, you have to create PDF pages first. The Designer -creates the layout, how the tables shall be displayed. To finally export the -view, you have to create this with a PDF page and select your layout, which you -have created with the designer. - -.. seealso:: - - :ref:`faqpdf` diff --git a/srcs/phpmyadmin/doc/html/_sources/require.txt b/srcs/phpmyadmin/doc/html/_sources/require.txt deleted file mode 100644 index 254d1ea..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/require.txt +++ /dev/null @@ -1,60 +0,0 @@ -.. _require: - -Requirements -============ - -Web server ----------- - -Since phpMyAdmin's interface is based entirely in your browser, you'll need a -web server (such as Apache, nginx, :term:`IIS`) to install phpMyAdmin's files into. - -PHP ---- - -* You need PHP 7.1.3 or newer, with ``session`` support, the Standard PHP Library - (SPL) extension, hash, ctype, and JSON support. - -* The ``mbstring`` extension (see :term:`mbstring`) is strongly recommended - for performance reasons. - -* To support uploading of ZIP files, you need the PHP ``zip`` extension. - -* You need GD2 support in PHP to display inline thumbnails of JPEGs - ("image/jpeg: inline") with their original aspect ratio. - -* When using the cookie authentication (the default), the `openssl - <https://www.php.net/openssl>`_ extension is strongly suggested. - -* To support upload progress bars, see :ref:`faq2_9`. - -* To support XML and Open Document Spreadsheet importing, you need the - `libxml <https://www.php.net/libxml>`_ extension. - -* To support reCAPTCHA on the login page, you need the - `openssl <https://www.php.net/openssl>`_ extension. - -* To support displaying phpMyAdmin's latest version, you need to enable - ``allow_url_open`` in your :file:`php.ini` or to have the - `curl <https://www.php.net/curl>`_ extension. - -.. seealso:: :ref:`faq1_31`, :ref:`authentication_modes` - -Database --------- - -phpMyAdmin supports MySQL-compatible databases. - -* MySQL 5.5 or newer -* MariaDB 5.5 or newer - -.. seealso:: :ref:`faq1_17` - -Web browser ------------ - -To access phpMyAdmin you need a web browser with cookies and JavaScript -enabled. - -You need browser which is supported by jQuery 2.0, see -<https://jquery.com/browser-support/>. diff --git a/srcs/phpmyadmin/doc/html/_sources/security.txt b/srcs/phpmyadmin/doc/html/_sources/security.txt deleted file mode 100644 index d6d93ec..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/security.txt +++ /dev/null @@ -1,113 +0,0 @@ -Security policy -=============== - -The phpMyAdmin developer team is putting lot of effort to make phpMyAdmin as -secure as possible. But still web application like phpMyAdmin can be vulnerable -to a number of attacks and new ways to exploit are still being explored. - -For every reported vulnerability we issue a phpMyAdmin Security Announcement -(PMASA) and it get's assigne CVE ID as well. We might group similar -vulnerabilities to one PMASA (eg. multiple XSS vulnerabilities can be announced -under one PMASA). - -If you think you've found a vulnerability, please see :ref:`reporting-security`. - -Typical vulnerabilities ------------------------ - -In this secion, we will describe typical vulnerabilities, which can appear in -our code base. This list is by no means complete, it is intended to show -typical attack surface. - -Cross-site scripting (XSS) -++++++++++++++++++++++++++ - -When phpMyAdmin shows a piece of user data, e.g. something inside a user's -database, all html special chars have to be escaped. When this escaping is -missing somewhere a malicious user might fill a database with specially crafted -content to trick an other user of that database into executing something. This -could for example be a piece of JavaScript code that would do any number of -nasty things. - -phpMyAdmin tries to escape all userdata before it is rendered into html for the -browser. - -.. seealso:: - - `Cross-site scripting on Wikipedia <https://en.wikipedia.org/wiki/Cross-site_scripting>`_ - -Cross-site request forgery (CSRF) -+++++++++++++++++++++++++++++++++ - -An attacker would trick a phpMyAdmin user into clicking on a link to provoke -some action in phpMyAdmin. This link could either be sent via email or some -random website. If successful this the attacker would be able to perform some -action with the users privileges. - -To mitigate this phpMyAdmin requires a token to be sent on sensitive requests. -The idea is that an attacker does not poses the currently valid token to -include in the presented link. - -The token is regenerated for every login, so it's generally valid only for -limited time, what makes it harder for attacker to obtain valid one. - -.. seealso:: - - `Cross-site request forgery on Wikipedia <https://en.wikipedia.org/wiki/Cross-site_request_forgery>`_ - -SQL injection -+++++++++++++ - -As the whole purpose of phpMyAdmin is to preform sql queries, this is not our -first concern. SQL injection is sensitive to us though when it concerns the -mysql control connection. This controlconnection can have additional privileges -which the logged in user does not poses. E.g. access the :ref:`linked-tables`. - -User data that is included in (administrative) queries should always be run -through DatabaseInterface::escapeSring(). - -.. seealso:: - - `SQL injection on Wikipedia <https://en.wikipedia.org/wiki/SQL_injection>`_ - -Brute force attack -++++++++++++++++++ - -phpMyAdmin on its own does not rate limit authentication attempts in any way. -This is caused by need to work in stateless environment, where there is no way -to protect against such kind of things. - -To mitigate this, you can use Captcha or utilize external tools such as -fail2ban, this is more details described in :ref:`securing`. - -.. seealso:: - - `Brute force attack on Wikipedia <https://en.wikipedia.org/wiki/Brute-force_attack>`_ - -.. _reporting-security: - -Reporting security issues -------------------------- - -Should you find a security issue in the phpMyAdmin programming code, please -contact the `phpMyAdmin security team <mailto:security@phpmyadmin.net>`_ in -advance before publishing it. This way we can prepare a fix and release the fix together with your -announcement. You will be also given credit in our security announcement. -You can optionally encrypt your report with PGP key ID -``DA68AB39218AB947`` with following fingerprint: - -.. code-block:: console - - pub 4096R/DA68AB39218AB947 2016-08-02 - Key fingerprint = 5BAD 38CF B980 50B9 4BD7 FB5B DA68 AB39 218A B947 - uid phpMyAdmin Security Team <security@phpmyadmin.net> - sub 4096R/5E4176FB497A31F7 2016-08-02 - -The key can be either obtained from the keyserver or is available in -`phpMyAdmin keyring <https://files.phpmyadmin.net/phpmyadmin.keyring>`_ -available on our download server or using `Keybase <https://keybase.io/phpmyadmin_sec>`_. - -Should you have suggestion on improving phpMyAdmin to make it more secure, please -report that to our `issue tracker <https://github.com/phpmyadmin/phpmyadmin/issues>`_. -Existing improvement suggestions can be found by -`hardening label <https://github.com/phpmyadmin/phpmyadmin/labels/hardening>`_. diff --git a/srcs/phpmyadmin/doc/html/_sources/settings.txt b/srcs/phpmyadmin/doc/html/_sources/settings.txt deleted file mode 100644 index be36b80..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/settings.txt +++ /dev/null @@ -1,21 +0,0 @@ -Configuring phpMyAdmin ----------------------- - -There are many configuration settings that can be used to customize the -interface. Those settings are described in -:ref:`config`. There are several layers of the configuration. - -The global settings can be configured in :file:`config.inc.php` as described in -:ref:`config`. This is only way to configure connections to databases and other -system wide settings. - -On top of this there are user settings which can be persistently stored in -:ref:`linked-tables`, possibly automatically configured through -:ref:`zeroconf`. If the :ref:`linked-tables` are not configured, the settings -are temporarily stored in the session data; these are valid only until you -logout. - -You can also save the user configuration for further use, either download them -as a file or to the browser local storage. You can find both those options in -the :guilabel:`Settings` tab. The settings stored in browser local storage will -be automatically offered for loading upon your login to phpMyAdmin. diff --git a/srcs/phpmyadmin/doc/html/_sources/setup.txt b/srcs/phpmyadmin/doc/html/_sources/setup.txt deleted file mode 100644 index cb517e3..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/setup.txt +++ /dev/null @@ -1,1148 +0,0 @@ -.. _setup: - -Installation -============ - -phpMyAdmin does not apply any special security methods to the MySQL -database server. It is still the system administrator's job to grant -permissions on the MySQL databases properly. phpMyAdmin's :guilabel:`Users` -page can be used for this. - -.. warning:: - - :term:`Mac` users should note that if you are on a version before - :term:`Mac OS X`, StuffIt unstuffs with :term:`Mac` formats. So you'll have - to resave as in BBEdit to Unix style ALL phpMyAdmin scripts before - uploading them to your server, as PHP seems not to like :term:`Mac`-style - end of lines character ("``\r``"). - -Linux distributions -+++++++++++++++++++ - -phpMyAdmin is included in most Linux distributions. It is recommended to use -distribution packages when possible - they usually provide integration to your -distribution and you will automatically get security updates from your distribution. - -.. _debian-package: - -Debian and Ubuntu ------------------ - -Debian's package repositories include a phpMyAdmin package, but be aware that -the configuration file is maintained in ``/etc/phpmyadmin`` and may differ in -some ways from the official phpMyAdmin documentation. Specifically, it does: - -* Configuration of a web server (works for Apache and lighttpd). -* Creating of :ref:`linked-tables` using dbconfig-common. -* Securing setup script, see :ref:`debian-setup`. - -.. seealso:: - - More information can be found in `README.Debian <https://salsa.debian.org/phpmyadmin-team/phpmyadmin/blob/master/debian/README.Debian>`_ - (it is installed as :file:`/usr/share/doc/phmyadmin/README.Debian` with the package). - -OpenSUSE --------- - -OpenSUSE already comes with phpMyAdmin package, just install packages from -the `openSUSE Build Service <https://software.opensuse.org/package/phpMyAdmin>`_. - -Gentoo ------- - -Gentoo ships the phpMyAdmin package, both in a near-stock configuration as well -as in a ``webapp-config`` configuration. Use ``emerge dev-db/phpmyadmin`` to -install. - -Mandriva --------- - -Mandriva ships the phpMyAdmin package in their ``contrib`` branch and can be -installed via the usual Control Center. - -Fedora ------- - -Fedora ships the phpMyAdmin package, but be aware that the configuration file -is maintained in ``/etc/phpMyAdmin/`` and may differ in some ways from the -official phpMyAdmin documentation. - -Red Hat Enterprise Linux ------------------------- - -Red Hat Enterprise Linux itself and thus derivatives like CentOS don't -ship phpMyAdmin, but the Fedora-driven repository -`Extra Packages for Enterprise Linux (EPEL) <https://fedoraproject.org/wiki/EPEL>`_ -is doing so, if it's -`enabled <https://fedoraproject.org/wiki/EPEL/FAQ#howtouse>`_. -But be aware that the configuration file is maintained in -``/etc/phpMyAdmin/`` and may differ in some ways from the -official phpMyAdmin documentation. - -Installing on Windows -+++++++++++++++++++++ - -The easiest way to get phpMyAdmin on Windows is using third party products -which include phpMyAdmin together with a database and web server such as -`XAMPP <https://www.apachefriends.org/index.html>`_. - -You can find more of such options at `Wikipedia <https://en.wikipedia.org/wiki/List_of_AMP_packages>`_. - -Installing from Git -+++++++++++++++++++ - -In order to install from Git, you'll need a few supporting applications: - -* `Git <https://git-scm.com/downloads>`_ to download the source, or you can download the most recent source directly from `Github <https://codeload.github.com/phpmyadmin/phpmyadmin/zip/master>`_ -* `Composer <https://getcomposer.org/download/>`__ -* `Node.js <https://nodejs.org/en/download/>`_ (version 8 or higher) -* `Yarn <https://yarnpkg.com/lang/en/docs/install>`_ - -You can clone current phpMyAdmin source from -``https://github.com/phpmyadmin/phpmyadmin.git``: - -.. code-block:: sh - - git clone https://github.com/phpmyadmin/phpmyadmin.git - -Additionally you need to install dependencies using `Composer <https://getcomposer.org>`__: - -.. code-block:: sh - - composer update - -If you do not intend to develop, you can skip the installation of developer tools -by invoking: - -.. code-block:: sh - - composer update --no-dev - -Finally, you'll need to use `Yarn`_ to install some JavaScript dependencies: - -.. code-block:: sh - - yarn install - -.. _composer: - -Installing using Composer -+++++++++++++++++++++++++ - -You can install phpMyAdmin using the `Composer tool`_, since 4.7.0 the releases -are automatically mirrored to the default `Packagist`_ repository. - -.. note:: - - The content of the Composer repository is automatically generated - separately from the releases, so the content doesn't have to be - 100% same as when you download the tarball. There should be no - functional differences though. - -To install phpMyAdmin simply run: - -.. code-block:: sh - - composer create-project phpmyadmin/phpmyadmin - -Alternatively you can use our own composer repository, which contains -the release tarballs and is available at -<https://www.phpmyadmin.net/packages.json>: - -.. code-block:: sh - - composer create-project phpmyadmin/phpmyadmin --repository-url=https://www.phpmyadmin.net/packages.json --no-dev - -.. _docker: - -Installing using Docker -+++++++++++++++++++++++ - -phpMyAdmin comes with a `Docker image`_, which you can easily deploy. You can -download it using: - -.. code-block:: sh - - docker pull phpmyadmin/phpmyadmin - -The phpMyAdmin server will listen on port 80. It supports several ways of -configuring the link to the database server, either by Docker's link feature -by linking your database container to ``db`` for phpMyAdmin (by specifying -``--link your_db_host:db``) or by environment variables (in this case it's up -to you to set up networking in Docker to allow the phpMyAdmin container to access -the database container over the network). - -.. _docker-vars: - -Docker environment variables ----------------------------- - -You can configure several phpMyAdmin features using environment variables: - -.. envvar:: PMA_ARBITRARY - - Allows you to enter a database server hostname on login form. - - .. seealso:: :config:option:`$cfg['AllowArbitraryServer']` - -.. envvar:: PMA_HOST - - Hostname or IP address of the database server to use. - - .. seealso:: :config:option:`$cfg['Servers'][$i]['host']` - -.. envvar:: PMA_HOSTS - - Comma-separated hostnames or IP addresses of the database servers to use. - - .. note:: Used only if :envvar:`PMA_HOST` is empty. - -.. envvar:: PMA_VERBOSE - - Verbose name of the database server. - - .. seealso:: :config:option:`$cfg['Servers'][$i]['verbose']` - -.. envvar:: PMA_VERBOSES - - Comma-separated verbose name of the database servers. - - .. note:: Used only if :envvar:`PMA_VERBOSE` is empty. - -.. envvar:: PMA_USER - - User name to use for :ref:`auth_config`. - -.. envvar:: PMA_PASSWORD - - Password to use for :ref:`auth_config`. - -.. envvar:: PMA_PORT - - Port of the database server to use. - -.. envvar:: PMA_PORTS - - Comma-separated ports of the database server to use. - - .. note:: Used only if :envvar:`PMA_PORT` is empty. - -.. envvar:: PMA_ABSOLUTE_URI - - The fully-qualified path (``https://pma.example.net/``) where the reverse - proxy makes phpMyAdmin available. - - .. seealso:: :config:option:`$cfg['PmaAbsoluteUri']` - -By default, :ref:`cookie` is used, but if :envvar:`PMA_USER` and -:envvar:`PMA_PASSWORD` are set, it is switched to :ref:`auth_config`. - -.. note:: - - The credentials you need to log in are stored in the MySQL server, in case - of Docker image, there are various ways to set it (for example - :samp:`MYSQL_ROOT_PASSWORD` when starting the MySQL container). Please check - documentation for `MariaDB container <https://hub.docker.com/_/mariadb>`_ - or `MySQL container <https://hub.docker.com/_/mysql>`_. - -.. _docker-custom: - -Customizing configuration -------------------------- - -Additionally configuration can be tweaked by :file:`/etc/phpmyadmin/config.user.inc.php`. If -this file exists, it will be loaded after configuration is generated from above -environment variables, so you can override any configuration variable. This -configuration can be added as a volume when invoking docker using -`-v /some/local/directory/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php` parameters. - -Note that the supplied configuration file is applied after :ref:`docker-vars`, -but you can override any of the values. - -For example to change the default behavior of CSV export you can use the following -configuration file: - -.. code-block:: php - - <?php - $cfg['Export']['csv_columns'] = true; - -You can also use it to define server configuration instead of using the -environment variables listed in :ref:`docker-vars`: - -.. code-block:: php - - <?php - /* Override Servers array */ - $cfg['Servers'] = [ - 1 => [ - 'auth_type' => 'cookie', - 'host' => 'mydb1', - 'port' => 3306, - 'verbose' => 'Verbose name 1', - ], - 2 => [ - 'auth_type' => 'cookie', - 'host' => 'mydb2', - 'port' => 3306, - 'verbose' => 'Verbose name 2', - ], - ]; - -.. seealso:: - - See :ref:`config` for detailed description of configuration options. - -Docker Volumes --------------- - -You can use the following volumes to customize image behavior: - -:file:`/etc/phpmyadmin/config.user.inc.php` - - Can be used for additional settings, see the previous chapter for more details. - -:file:`/sessions/` - - Directory where PHP sessions are stored. You might want to share this - for example when using :ref:`auth_signon`. - -:file:`/www/themes/` - - Directory where phpMyAdmin looks for themes. By default only those shipped - with phpMyAdmin are included, but you can include additional phpMyAdmin - themes (see :ref:`themes`) by using Docker volumes. - -Docker Examples ---------------- - -To connect phpMyAdmin to a given server use: - -.. code-block:: sh - - docker run --name myadmin -d -e PMA_HOST=dbhost -p 8080:80 phpmyadmin/phpmyadmin - -To connect phpMyAdmin to more servers use: - -.. code-block:: sh - - docker run --name myadmin -d -e PMA_HOSTS=dbhost1,dbhost2,dbhost3 -p 8080:80 phpmyadmin/phpmyadmin - -To use arbitrary server option: - -.. code-block:: sh - - docker run --name myadmin -d --link mysql_db_server:db -p 8080:80 -e PMA_ARBITRARY=1 phpmyadmin/phpmyadmin - -You can also link the database container using Docker: - -.. code-block:: sh - - docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 phpmyadmin/phpmyadmin - -Running with additional configuration: - -.. code-block:: sh - - docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php phpmyadmin/phpmyadmin - -Running with additional themes: - -.. code-block:: sh - - docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /custom/phpmyadmin/theme/:/www/themes/theme/ phpmyadmin/phpmyadmin - -Using docker-compose --------------------- - -Alternatively, you can also use docker-compose with the docker-compose.yml from -<https://github.com/phpmyadmin/docker>. This will run phpMyAdmin with an -arbitrary server - allowing you to specify MySQL/MariaDB server on the login page. - -.. code-block:: sh - - docker-compose up -d - -Customizing configuration file using docker-compose ---------------------------------------------------- - -You can use an external file to customize phpMyAdmin configuration and pass it -using the volumes directive: - -.. code-block:: yaml - - phpmyadmin: - image: phpmyadmin/phpmyadmin - container_name: phpmyadmin - environment: - - PMA_ARBITRARY=1 - restart: always - ports: - - 8080:80 - volumes: - - /sessions - - ~/docker/phpmyadmin/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php - - /custom/phpmyadmin/theme/:/www/themes/theme/ - -.. seealso:: :ref:`docker-custom` - -Running behind haproxy in a subdirectory ----------------------------------------- - -When you want to expose phpMyAdmin running in a Docker container in a -subdirectory, you need to rewrite the request path in the server proxying the -requests. - -For example, using haproxy it can be done as: - -.. code-block:: text - - frontend http - bind *:80 - option forwardfor - option http-server-close - - ### NETWORK restriction - acl LOCALNET src 10.0.0.0/8 192.168.0.0/16 172.16.0.0/12 - - # /phpmyadmin - acl phpmyadmin path_dir /phpmyadmin - use_backend phpmyadmin if phpmyadmin LOCALNET - - backend phpmyadmin - mode http - - reqirep ^(GET|POST|HEAD)\ /phpmyadmin/(.*) \1\ /\2 - - # phpMyAdmin container IP - server localhost 172.30.21.21:80 - -When using traefik, something like following should work: - -.. code-block:: text - - defaultEntryPoints = ["http"] - [entryPoints] - [entryPoints.http] - address = ":80" - [entryPoints.http.redirect] - regex = "(http:\\/\\/[^\\/]+\\/([^\\?\\.]+)[^\\/])$" - replacement = "$1/" - - [backends] - [backends.myadmin] - [backends.myadmin.servers.myadmin] - url="http://internal.address.to.pma" - - [frontends] - [frontends.myadmin] - backend = "myadmin" - passHostHeader = true - [frontends.myadmin.routes.default] - rule="PathPrefixStrip:/phpmyadmin/;AddPrefix:/" - -You then should specify :envvar:`PMA_ABSOLUTE_URI` in the docker-compose -configuration: - -.. code-block:: yaml - - version: '2' - - services: - phpmyadmin: - restart: always - image: phpmyadmin/phpmyadmin - container_name: phpmyadmin - hostname: phpmyadmin - domainname: example.com - ports: - - 8000:80 - environment: - - PMA_HOSTS=172.26.36.7,172.26.36.8,172.26.36.9,172.26.36.10 - - PMA_VERBOSES=production-db1,production-db2,dev-db1,dev-db2 - - PMA_USER=root - - PMA_PASSWORD= - - PMA_ABSOLUTE_URI=http://example.com/phpmyadmin/ - -.. _quick_install: - -Quick Install -+++++++++++++ - -#. Choose an appropriate distribution kit from the phpmyadmin.net - Downloads page. Some kits contain only the English messages, others - contain all languages. We'll assume you chose a kit whose name - looks like ``phpMyAdmin-x.x.x -all-languages.tar.gz``. -#. Ensure you have downloaded a genuine archive, see :ref:`verify`. -#. Untar or unzip the distribution (be sure to unzip the subdirectories): - ``tar -xzvf phpMyAdmin_x.x.x-all-languages.tar.gz`` in your - webserver's document root. If you don't have direct access to your - document root, put the files in a directory on your local machine, - and, after step 4, transfer the directory on your web server using, - for example, FTP. -#. Ensure that all the scripts have the appropriate owner (if PHP is - running in safe mode, having some scripts with an owner different from - the owner of other scripts will be a problem). See :ref:`faq4_2` and - :ref:`faq1_26` for suggestions. -#. Now you must configure your installation. There are two methods that - can be used. Traditionally, users have hand-edited a copy of - :file:`config.inc.php`, but now a wizard-style setup script is provided - for those who prefer a graphical installation. Creating a - :file:`config.inc.php` is still a quick way to get started and needed for - some advanced features. - -Manually creating the file --------------------------- - -To manually create the file, simply use your text editor to create the -file :file:`config.inc.php` (you can copy :file:`config.sample.inc.php` to get -a minimal configuration file) in the main (top-level) phpMyAdmin -directory (the one that contains :file:`index.php`). phpMyAdmin first -loads :file:`libraries/config.default.php` and then overrides those values -with anything found in :file:`config.inc.php`. If the default value is -okay for a particular setting, there is no need to include it in -:file:`config.inc.php`. You'll probably need only a few directives to get going; a -simple configuration may look like this: - -.. code-block:: xml+php - - <?php - // use here a value of your choice at least 32 chars long - $cfg['blowfish_secret'] = '1{dd0`<Q),5XP_:R9UK%%8\"EEcyH#{o'; - - $i=0; - $i++; - $cfg['Servers'][$i]['auth_type'] = 'cookie'; - // if you insist on "root" having no password: - // $cfg['Servers'][$i]['AllowNoPassword'] = true; - -Or, if you prefer to not be prompted every time you log in: - -.. code-block:: xml+php - - <?php - - $i=0; - $i++; - $cfg['Servers'][$i]['user'] = 'root'; - $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password - $cfg['Servers'][$i]['auth_type'] = 'config'; - -.. warning:: - - Storing passwords in the configuration is insecure as anybody can then - manipulate your database. - -For a full explanation of possible configuration values, see the -:ref:`config` of this document. - -.. index:: Setup script - -.. _setup_script: - -Using the Setup script ----------------------- - -Instead of manually editing :file:`config.inc.php`, you can use phpMyAdmin's -setup feature. The file can be generated using the setup and you can download it -for upload to the server. - -Next, open your browser and visit the location where you installed phpMyAdmin, -with the ``/setup`` suffix. The changes are not saved to the server, you need to -use the :guilabel:`Download` button to save them to your computer and then upload -to the server. - -Now the file is ready to be used. You can choose to review or edit the -file with your favorite editor, if you prefer to set some advanced -options that the setup script does not provide. - -#. If you are using the ``auth_type`` "config", it is suggested that you - protect the phpMyAdmin installation directory because using config - does not require a user to enter a password to access the phpMyAdmin - installation. Use of an alternate authentication method is - recommended, for example with HTTP–AUTH in a :term:`.htaccess` file or switch to using - ``auth_type`` cookie or http. See the :ref:`faqmultiuser` - for additional information, especially :ref:`faq4_4`. -#. Open the main phpMyAdmin directory in your browser. - phpMyAdmin should now display a welcome screen and your databases, or - a login dialog if using :term:`HTTP` or - cookie authentication mode. - -.. _debian-setup: - -Setup script on Debian, Ubuntu and derivatives -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Debian and Ubuntu have changed the way in which the setup script is enabled and disabled, in a way -that single command has to be executed for either of these. - -To allow editing configuration invoke: - -.. code-block:: sh - - /usr/sbin/pma-configure - -To block editing configuration invoke: - -.. code-block:: sh - - /usr/sbin/pma-secure - -Setup script on openSUSE -~~~~~~~~~~~~~~~~~~~~~~~~ - -Some openSUSE releases do not include setup script in the package. In case you -want to generate configuration on these you can either download original -package from <https://www.phpmyadmin.net/> or use setup script on our demo -server: <https://demo.phpmyadmin.net/master/setup/>. - -.. _verify: - -Verifying phpMyAdmin releases -+++++++++++++++++++++++++++++ - -Since July 2015 all phpMyAdmin releases are cryptographically signed by the -releasing developer, who through January 2016 was Marc Delisle. His key id is -0xFEFC65D181AF644A, his PGP fingerprint is: - -.. code-block:: console - - 436F F188 4B1A 0C3F DCBF 0D79 FEFC 65D1 81AF 644A - -and you can get more identification information from <https://keybase.io/lem9>. - -Beginning in January 2016, the release manager is Isaac Bennetch. His key id is -0xCE752F178259BD92, and his PGP fingerprint is: - -.. code-block:: console - - 3D06 A59E CE73 0EB7 1B51 1C17 CE75 2F17 8259 BD92 - -and you can get more identification information from <https://keybase.io/ibennetch>. - -Some additional downloads (for example themes) might be signed by Michal Čihař. His key id is -0x9C27B31342B7511D, and his PGP fingerprint is: - -.. code-block:: console - - 63CB 1DF1 EF12 CF2A C0EE 5A32 9C27 B313 42B7 511D - -and you can get more identification information from <https://keybase.io/nijel>. - -You should verify that the signature matches the archive you have downloaded. -This way you can be sure that you are using the same code that was released. -You should also verify the date of the signature to make sure that you -downloaded the latest version. - -Each archive is accompanied by ``.asc`` files which contain the PGP signature -for it. Once you have both of them in the same folder, you can verify the signature: - -.. code-block:: console - - $ gpg --verify phpMyAdmin-4.5.4.1-all-languages.zip.asc - gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92 - gpg: Can't check signature: public key not found - -As you can see gpg complains that it does not know the public key. At this -point, you should do one of the following steps: - -* Download the keyring from `our download server <https://files.phpmyadmin.net/phpmyadmin.keyring>`_, then import it with: - -.. code-block:: console - - $ gpg --import phpmyadmin.keyring - -* Download and import the key from one of the key servers: - -.. code-block:: console - - $ gpg --keyserver hkp://pgp.mit.edu --recv-keys 3D06A59ECE730EB71B511C17CE752F178259BD92 - gpg: requesting key 8259BD92 from hkp server pgp.mit.edu - gpg: key 8259BD92: public key "Isaac Bennetch <bennetch@gmail.com>" imported - gpg: no ultimately trusted keys found - gpg: Total number processed: 1 - gpg: imported: 1 (RSA: 1) - -This will improve the situation a bit - at this point, you can verify that the -signature from the given key is correct but you still can not trust the name used -in the key: - -.. code-block:: console - - $ gpg --verify phpMyAdmin-4.5.4.1-all-languages.zip.asc - gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92 - gpg: Good signature from "Isaac Bennetch <bennetch@gmail.com>" - gpg: aka "Isaac Bennetch <isaac@bennetch.org>" - gpg: WARNING: This key is not certified with a trusted signature! - gpg: There is no indication that the signature belongs to the owner. - Primary key fingerprint: 3D06 A59E CE73 0EB7 1B51 1C17 CE75 2F17 8259 BD92 - -The problem here is that anybody could issue the key with this name. You need to -ensure that the key is actually owned by the mentioned person. The GNU Privacy -Handbook covers this topic in the chapter `Validating other keys on your public -keyring`_. The most reliable method is to meet the developer in person and -exchange key fingerprints, however, you can also rely on the web of trust. This way -you can trust the key transitively though signatures of others, who have met -the developer in person. For example, you can see how `Isaac's key links to -Linus's key`_. - -Once the key is trusted, the warning will not occur: - -.. code-block:: console - - $ gpg --verify phpMyAdmin-4.5.4.1-all-languages.zip.asc - gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92 - gpg: Good signature from "Isaac Bennetch <bennetch@gmail.com>" [full] - -Should the signature be invalid (the archive has been changed), you would get a -clear error regardless of the fact that the key is trusted or not: - -.. code-block:: console - - $ gpg --verify phpMyAdmin-4.5.4.1-all-languages.zip.asc - gpg: Signature made Fri 29 Jan 2016 08:59:37 AM EST using RSA key ID 8259BD92 - gpg: BAD signature from "Isaac Bennetch <bennetch@gmail.com>" [unknown] - -.. _Validating other keys on your public keyring: https://www.gnupg.org/gph/en/manual.html#AEN335 - -.. _Isaac's key links to Linus's key: https://pgp.cs.uu.nl/paths/79be3e4300411886/to/ce752f178259bd92.html - -.. index:: - single: Configuration storage - single: phpMyAdmin configuration storage - single: pmadb - -.. _linked-tables: - -phpMyAdmin configuration storage -++++++++++++++++++++++++++++++++ - -.. versionchanged:: 3.4.0 - - Prior to phpMyAdmin 3.4.0 this was called Linked Tables Infrastructure, but - the name was changed due to the extended scope of the storage. - -For a whole set of additional features (:ref:`bookmarks`, comments, :term:`SQL`-history, -tracking mechanism, :term:`PDF`-generation, :ref:`transformations`, :ref:`relations` -etc.) you need to create a set of special tables. Those tables can be located -in your own database, or in a central database for a multi-user installation -(this database would then be accessed by the controluser, so no other user -should have rights to it). - -.. _zeroconf: - -Zero configuration ------------------- - -In many cases, this database structure can be automatically created and -configured. This is called “Zero Configuration” mode and can be particularly -useful in shared hosting situations. “Zeroconf” mode is on by default, to -disable set :config:option:`$cfg['ZeroConf']` to false. - -The following three scenarios are covered by the Zero Configuration mode: - -* When entering a database where the configuration storage tables are not - present, phpMyAdmin offers to create them from the Operations tab. -* When entering a database where the tables do already exist, the software - automatically detects this and begins using them. This is the most common - situation; after the tables are initially created automatically they are - continually used without disturbing the user; this is also most useful on - shared hosting where the user is not able to edit :file:`config.inc.php` and - usually the user only has access to one database. -* When having access to multiple databases, if the user first enters the - database containing the configuration storage tables then switches to - another database, - phpMyAdmin continues to use the tables from the first database; the user is - not prompted to create more tables in the new database. - -Manual configuration --------------------- - -Please look at your ``./sql/`` directory, where you should find a -file called *create\_tables.sql*. (If you are using a Windows server, -pay special attention to :ref:`faq1_23`). - -If you already had this infrastructure and: - -* upgraded to MySQL 4.1.2 or newer, please use - :file:`sql/upgrade_tables_mysql_4_1_2+.sql`. -* upgraded to phpMyAdmin 4.3.0 or newer from 2.5.0 or newer (<= 4.2.x), - please use :file:`sql/upgrade_column_info_4_3_0+.sql`. -* upgraded to phpMyAdmin 4.7.0 or newer from 4.3.0 or newer, - please use :file:`sql/upgrade_tables_4_7_0+.sql`. - -and then create new tables by importing :file:`sql/create_tables.sql`. - -You can use your phpMyAdmin to create the tables for you. Please be -aware that you may need special (administrator) privileges to create -the database and tables, and that the script may need some tuning, -depending on the database name. - -After having imported the :file:`sql/create_tables.sql` file, you -should specify the table names in your :file:`config.inc.php` file. The -directives used for that can be found in the :ref:`config`. - -You will also need to have a controluser -(:config:option:`$cfg['Servers'][$i]['controluser']` and -:config:option:`$cfg['Servers'][$i]['controlpass']` settings) -with the proper rights to those tables. For example you can create it -using following statement: - -And for any MariaDB version: - -.. code-block:: mysql - - CREATE USER 'pma'@'localhost' IDENTIFIED VIA mysql_native_password USING 'pmapass'; - GRANT SELECT, INSERT, UPDATE, DELETE ON `<pma_db>`.* TO 'pma'@'localhost'; - -For MySQL 8.0 and newer: - -.. code-block:: mysql - - CREATE USER 'pma'@'localhost' IDENTIFIED WITH caching_sha2_password BY 'pmapass'; - GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost'; - -For MySQL older than 8.0: - -.. code-block:: mysql - - CREATE USER 'pma'@'localhost' IDENTIFIED WITH mysql_native_password AS 'pmapass'; - GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost'; - -Note that MySQL installations with PHP older than 7.4 and MySQL newer than 8.0 may require -using the mysql_native_password authentication as a workaround, see -:ref:`faq1_45` for details. - -.. _upgrading: - -Upgrading from an older version -+++++++++++++++++++++++++++++++ - -.. warning:: - - **Never** extract the new version over an existing installation of - phpMyAdmin, always first remove the old files keeping just the - configuration. - - This way, you will not leave any old or outdated files in the directory, - which can have severe security implications or can cause various breakages. - -Simply copy :file:`config.inc.php` from your previous installation into -the newly unpacked one. Configuration files from old versions may -require some tweaking as some options have been changed or removed. -For compatibility with PHP 5.3 and later, remove a -``set_magic_quotes_runtime(0);`` statement that you might find near -the end of your configuration file. - -You should **not** copy :file:`libraries/config.default.php` over -:file:`config.inc.php` because the default configuration file is version- -specific. - -The complete upgrade can be performed in a few simple steps: - -1. Download the latest phpMyAdmin version from <https://www.phpmyadmin.net/downloads/>. -2. Rename existing phpMyAdmin folder (for example to ``phpmyadmin-old``). -3. Unpack freshly downloaded phpMyAdmin to the desired location (for example ``phpmyadmin``). -4. Copy :file:`config.inc.php`` from old location (``phpmyadmin-old``) to the new one (``phpmyadmin``). -5. Test that everything works properly. -6. Remove backup of a previous version (``phpmyadmin-old``). - -If you have upgraded your MySQL server from a version previous to 4.1.2 to -version 5.x or newer and if you use the phpMyAdmin configuration storage, you -should run the :term:`SQL` script found in -:file:`sql/upgrade_tables_mysql_4_1_2+.sql`. - -If you have upgraded your phpMyAdmin to 4.3.0 or newer from 2.5.0 or -newer (<= 4.2.x) and if you use the phpMyAdmin configuration storage, you -should run the :term:`SQL` script found in -:file:`sql/upgrade_column_info_4_3_0+.sql`. - -Do not forget to clear the browser cache and to empty the old session by -logging out and logging in again. - -.. index:: Authentication mode - -.. _authentication_modes: - -Using authentication modes -++++++++++++++++++++++++++ - -:term:`HTTP` and cookie authentication modes are recommended in a **multi-user -environment** where you want to give users access to their own database and -don't want them to play around with others. Nevertheless, be aware that MS -Internet Explorer seems to be really buggy about cookies, at least till version -6. Even in a **single-user environment**, you might prefer to use :term:`HTTP` -or cookie mode so that your user/password pair are not in clear in the -configuration file. - -:term:`HTTP` and cookie authentication -modes are more secure: the MySQL login information does not need to be -set in the phpMyAdmin configuration file (except possibly for the -:config:option:`$cfg['Servers'][$i]['controluser']`). -However, keep in mind that the password travels in plain text unless -you are using the HTTPS protocol. In cookie mode, the password is -stored, encrypted with the AES algorithm, in a temporary cookie. - -Then each of the *true* users should be granted a set of privileges -on a set of particular databases. Normally you shouldn't give global -privileges to an ordinary user unless you understand the impact of those -privileges (for example, you are creating a superuser). -For example, to grant the user *real_user* with all privileges on -the database *user_base*: - -.. code-block:: mysql - - GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password'; - -What the user may now do is controlled entirely by the MySQL user management -system. With HTTP or cookie authentication mode, you don't need to fill the -user/password fields inside the :config:option:`$cfg['Servers']`. - -.. seealso:: - - :ref:`faq1_32`, - :ref:`faq1_35`, - :ref:`faq4_1`, - :ref:`faq4_2`, - :ref:`faq4_3` - -.. index:: pair: HTTP; Authentication mode - -.. _auth_http: - -HTTP authentication mode ------------------------- - -* Uses :term:`HTTP` Basic authentication - method and allows you to log in as any valid MySQL user. -* Is supported with most PHP configurations. For :term:`IIS` (:term:`ISAPI`) - support using :term:`CGI` PHP see :ref:`faq1_32`, for using with Apache - :term:`CGI` see :ref:`faq1_35`. -* When PHP is running under Apache's :term:`mod_proxy_fcgi` (e.g. with PHP-FPM), - ``Authorization`` headers are not passed to the underlying FCGI application, - such that your credentials will not reach the application. In this case, you can - add the following configuration directive: - - .. code-block:: apache - - SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1 - -* See also :ref:`faq4_4` about not using the :term:`.htaccess` mechanism along with - ':term:`HTTP`' authentication mode. - -.. note:: - - There is no way to do proper logout in HTTP authentication, most browsers - will remember credentials until there is no different successful - authentication. Because of this, this method has a limitation that you can not - login with the same user after logout. - -.. index:: pair: Cookie; Authentication mode - -.. _cookie: - -Cookie authentication mode --------------------------- - -* Username and password are stored in cookies during the session and password - is deleted when it ends. -* With this mode, the user can truly log out of phpMyAdmin and log - back in with the same username (this is not possible with :ref:`auth_http`). -* If you want to allow users to enter any hostname to connect (rather than only - servers that are configured in :file:`config.inc.php`), - see the :config:option:`$cfg['AllowArbitraryServer']` directive. -* As mentioned in the :ref:`require` section, having the ``openssl`` extension - will speed up access considerably, but is not required. - -.. index:: pair: Signon; Authentication mode - -.. _auth_signon: - -Signon authentication mode --------------------------- - -* This mode is a convenient way of using credentials from another - application to authenticate to phpMyAdmin to implement a single signon - solution. -* The other application has to store login information into session - data (see :config:option:`$cfg['Servers'][$i]['SignonSession']` and - :config:option:`$cfg['Servers'][$i]['SignonCookieParams']`) or you - need to implement script to return the credentials (see - :config:option:`$cfg['Servers'][$i]['SignonScript']`). -* When no credentials are available, the user is being redirected to - :config:option:`$cfg['Servers'][$i]['SignonURL']`, where you should handle - the login process. - -The very basic example of saving credentials in a session is available as -:file:`examples/signon.php`: - -.. literalinclude:: ../examples/signon.php - :language: php - -Alternatively, you can also use this way to integrate with OpenID as shown -in :file:`examples/openid.php`: - -.. literalinclude:: ../examples/openid.php - :language: php - -If you intend to pass the credentials using some other means than, you have to -implement wrapper in PHP to get that data and set it to -:config:option:`$cfg['Servers'][$i]['SignonScript']`. There is a very minimal example -in :file:`examples/signon-script.php`: - -.. literalinclude:: ../examples/signon-script.php - :language: php - -.. seealso:: - :config:option:`$cfg['Servers'][$i]['auth_type']`, - :config:option:`$cfg['Servers'][$i]['SignonSession']`, - :config:option:`$cfg['Servers'][$i]['SignonCookieParams']`, - :config:option:`$cfg['Servers'][$i]['SignonScript']`, - :config:option:`$cfg['Servers'][$i]['SignonURL']`, - :ref:`example-signon` - -.. index:: pair: Config; Authentication mode - -.. _auth_config: - -Config authentication mode --------------------------- - -* This mode is sometimes the less secure one because it requires you to fill the - :config:option:`$cfg['Servers'][$i]['user']` and - :config:option:`$cfg['Servers'][$i]['password']` - fields (and as a result, anyone who can read your :file:`config.inc.php` - can discover your username and password). -* In the :ref:`faqmultiuser` section, there is an entry explaining how - to protect your configuration file. -* For additional security in this mode, you may wish to consider the - Host authentication :config:option:`$cfg['Servers'][$i]['AllowDeny']['order']` - and :config:option:`$cfg['Servers'][$i]['AllowDeny']['rules']` configuration directives. -* Unlike cookie and http, does not require a user to log in when first - loading the phpMyAdmin site. This is by design but could allow any - user to access your installation. Use of some restriction method is - suggested, perhaps a :term:`.htaccess` file with the HTTP-AUTH directive or disallowing - incoming HTTP requests at one’s router or firewall will suffice (both - of which are beyond the scope of this manual but easily searchable - with Google). - -.. _securing: - -Securing your phpMyAdmin installation -+++++++++++++++++++++++++++++++++++++ - -The phpMyAdmin team tries hard to make the application secure, however there -are always ways to make your installation more secure: - -* Follow our `Security announcements <https://www.phpmyadmin.net/security/>`_ and upgrade - phpMyAdmin whenever new vulnerability is published. -* Serve phpMyAdmin on HTTPS only. Preferably, you should use HSTS as well, so that - you're protected from protocol downgrade attacks. -* Ensure your PHP setup follows recommendations for production sites, for example - `display_errors <https://www.php.net/manual/en/errorfunc.configuration.php#ini.display-errors>`_ - should be disabled. -* Remove the ``test`` directory from phpMyAdmin, unless you are developing and need a test suite. -* Remove the ``setup`` directory from phpMyAdmin, you will probably not - use it after the initial setup. -* Properly choose an authentication method - :ref:`cookie` - is probably the best choice for shared hosting. -* Deny access to auxiliary files in :file:`./libraries/` or - :file:`./templates/` subfolders in your webserver configuration. - Such configuration prevents from possible path exposure and cross side - scripting vulnerabilities that might happen to be found in that code. For the - Apache webserver, this is often accomplished with a :term:`.htaccess` file in - those directories. -* Deny access to temporary files, see :config:option:`$cfg['TempDir']` (if that - is placed inside your web root, see also :ref:`web-dirs`. -* It is generally a good idea to protect a public phpMyAdmin installation - against access by robots as they usually can not do anything good there. You - can do this using ``robots.txt`` file in the root of your webserver or limit - access by web server configuration, see :ref:`faq1_42`. -* In case you don't want all MySQL users to be able to access - phpMyAdmin, you can use :config:option:`$cfg['Servers'][$i]['AllowDeny']['rules']` to limit them - or :config:option:`$cfg['Servers'][$i]['AllowRoot']` to deny root user access. -* Enable :ref:`2fa` for your account. -* Consider hiding phpMyAdmin behind an authentication proxy, so that - users need to authenticate prior to providing MySQL credentials - to phpMyAdmin. You can achieve this by configuring your web server to request - HTTP authentication. For example in Apache this can be done with: - - .. code-block:: apache - - AuthType Basic - AuthName "Restricted Access" - AuthUserFile /usr/share/phpmyadmin/passwd - Require valid-user - - Once you have changed the configuration, you need to create a list of users which - can authenticate. This can be done using the :program:`htpasswd` utility: - - .. code-block:: sh - - htpasswd -c /usr/share/phpmyadmin/passwd username - -* If you are afraid of automated attacks, enabling Captcha by - :config:option:`$cfg['CaptchaLoginPublicKey']` and - :config:option:`$cfg['CaptchaLoginPrivateKey']` might be an option. -* Failed login attemps are logged to syslog (if available, see - :config:option:`$cfg['AuthLog']`). This can allow using a tool such as - fail2ban to block brute-force attempts. Note that the log file used by syslog - is not the same as the Apache error or access log files. -* In case you're running phpMyAdmin together with other PHP applications, it is - generally advised to use separate session storage for phpMyAdmin to avoid - possible session-based attacks against it. You can use - :config:option:`$cfg['SessionSavePath']` to achieve this. - -.. _ssl: - -Using SSL for connection to database server -+++++++++++++++++++++++++++++++++++++++++++ - -It is recommended to use SSL when connecting to remote database server. There -are several configuration options involved in the SSL setup: - -:config:option:`$cfg['Servers'][$i]['ssl']` - Defines whether to use SSL at all. If you enable only this, the connection - will be encrypted, but there is not authentication of the connection - you - can not verify that you are talking to the right server. -:config:option:`$cfg['Servers'][$i]['ssl_key']` and :config:option:`$cfg['Servers'][$i]['ssl_cert']` - This is used for authentication of client to the server. -:config:option:`$cfg['Servers'][$i]['ssl_ca']` and :config:option:`$cfg['Servers'][$i]['ssl_ca_path']` - The certificate authorities you trust for server certificates. - This is used to ensure that you are talking to a trusted server. -:config:option:`$cfg['Servers'][$i]['ssl_verify']` - This configuration disables server certificate verification. Use with - caution. - -.. seealso:: - - :ref:`example-google-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']` - -Known issues -++++++++++++ - -Users with column-specific privileges are unable to "Browse" ------------------------------------------------------------- - -If a user has only column-specific privileges on some (but not all) columns in a table, "Browse" -will fail with an error message. - -As a workaround, a bookmarked query with the same name as the table can be created, this will -run when using the "Browse" link instead. `Issue 11922 <https://github.com/phpmyadmin/phpmyadmin/issues/11922>`_. - -Trouble logging back in after logging out using 'http' authentication ----------------------------------------------------------------------- - -When using the 'http' ``auth_type``, it can be impossible to log back in (when the logout comes -manually or after a period of inactivity). `Issue 11898 <https://github.com/phpmyadmin/phpmyadmin/issues/11898>`_. - -.. _Composer tool: https://getcomposer.org/ -.. _Packagist: https://packagist.org/ -.. _Docker image: https://hub.docker.com/r/phpmyadmin/phpmyadmin/ diff --git a/srcs/phpmyadmin/doc/html/_sources/themes.txt b/srcs/phpmyadmin/doc/html/_sources/themes.txt deleted file mode 100644 index 1f22521..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/themes.txt +++ /dev/null @@ -1,100 +0,0 @@ -.. _themes: - -Custom Themes -============= - -phpMyAdmin comes with support for third party themes. You can download -additonal themes from our website at <https://www.phpmyadmin.net/themes/>. - -Configuration -------------- - -Themes are configured with :config:option:`$cfg['ThemeManager']` and -:config:option:`$cfg['ThemeDefault']`. Under :file:`./themes/`, you should not -delete the directory ``pmahomme`` or its underlying structure, because this is -the system theme used by phpMyAdmin. ``pmahomme`` contains all images and -styles, for backwards compatibility and for all themes that would not include -images or css-files. If :config:option:`$cfg['ThemeManager']` is enabled, you -can select your favorite theme on the main page. Your selected theme will be -stored in a cookie. - -Creating custom theme ---------------------- - -To create a theme: - -* make a new subdirectory (for example "your\_theme\_name") under :file:`./themes/`. -* copy the files and directories from ``pmahomme`` to "your\_theme\_name" -* edit the css-files in "your\_theme\_name/css" -* put your new images in "your\_theme\_name/img" -* edit :file:`layout.inc.php` in "your\_theme\_name" -* edit :file:`theme.json` in "your\_theme\_name" to contain theme metadata (see below) -* make a new screenshot of your theme and save it under - "your\_theme\_name/screen.png" - -Theme metadata -++++++++++++++ - -.. versionchanged:: 4.8.0 - - Before 4.8.0 the theme metadata was passed in the :file:`info.inc.php` file. - It has been replaced by :file:`theme.json` to allow easier parsing (without - need to handle PHP code) and to support additional features. - -In theme directory there is file :file:`theme.json` which contains theme -metadata. Currently it consists of: - -.. describe:: name - - Display name of the theme. - - **This field is required.** - -.. describe:: version - - Theme version, can be quite arbirary and does not have to match phpMyAdmin version. - - **This field is required.** - -.. describe:: desciption - - Theme description. this will be shown on the website. - - **This field is required.** - -.. describe:: author - - Theme author name. - - **This field is required.** - -.. describe:: url - - Link to theme author website. It's good idea to have way for getting - support there. - -.. describe:: supports - - Array of supported phpMyAdmin major versions. - - **This field is required.** - -For example, the definition for Original theme shipped with phpMyAdnin 4.8: - -.. code-block:: json - - { - "name": "Original", - "version": "4.8", - "description": "Original phpMyAdmin theme", - "author": "phpMyAdmin developers", - "url": "https://www.phpmyadmin.net/", - "supports": ["4.8"] - } - -Sharing images -++++++++++++++ - -If you do not want to use your own symbols and buttons, remove the -directory "img" in "your\_theme\_name". phpMyAdmin will use the -default icons and buttons (from the system-theme ``pmahomme``). diff --git a/srcs/phpmyadmin/doc/html/_sources/transformations.txt b/srcs/phpmyadmin/doc/html/_sources/transformations.txt deleted file mode 100644 index 9eeb754..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/transformations.txt +++ /dev/null @@ -1,143 +0,0 @@ -.. _transformations: - -Transformations -=============== - -.. note:: - - You need to have configured the :ref:`linked-tables` for using transformations - feature. - -.. _transformationsintro: - -Introduction -++++++++++++ - -To enable transformations, you have to setup the ``column_info`` -table and the proper directives. Please see the :ref:`config` on how to do so. - -You can apply different transformations to the contents of each -column. The transformation will take the content of each column and -transform it with certain rules defined in the selected -transformation. - -Say you have a column 'filename' which contains a filename. Normally -you would see in phpMyAdmin only this filename. Using transformations -you can transform that filename into a HTML link, so you can click -inside of the phpMyAdmin structure on the column's link and will see -the file displayed in a new browser window. Using transformation -options you can also specify strings to append/prepend to a string or -the format you want the output stored in. - -For a general overview of all available transformations and their -options, you can consult your *<www.your-host.com>/<your-install- -dir>/transformation\_overview.php* installation. - -For a tutorial on how to effectively use transformations, see our -`Link section <https://www.phpmyadmin.net/docs/>`_ on the -official phpMyAdmin homepage. - -.. _transformationshowto: - -Usage -+++++ - -Go to your *tbl\_structure.php* page (i.e. reached through clicking on -the 'Structure' link for a table). There click on "Change" (or change -icon) and there you will see three new fields at the end of the line. -They are called 'MIME-type', 'Browser transformation' and -'Transformation options'. - -* The field 'MIME-type' is a drop-down field. Select the MIME-type that - corresponds to the column's contents. Please note that transformations - are inactive as long as no MIME-type is selected. -* The field 'Browser transformation' is a drop-down field. You can - choose from a hopefully growing amount of pre-defined transformations. - See below for information on how to build your own transformation. - There are global transformations and mimetype-bound transformations. - Global transformations can be used for any mimetype. They will take - the mimetype, if necessary, into regard. Mimetype-bound - transformations usually only operate on a certain mimetype. There are - transformations which operate on the main mimetype (like 'image'), - which will most likely take the subtype into regard, and those who - only operate on a specific subtype (like 'image/jpeg'). You can use - transformations on mimetypes for which the function was not defined - for. There is no security check for you selected the right - transformation, so take care of what the output will be like. -* The field 'Transformation options' is a free-type textfield. You have - to enter transform-function specific options here. Usually the - transforms can operate with default options, but it is generally a - good idea to look up the overview to see which options are necessary. - Much like the ENUM/SET-Fields, you have to split up several options - using the format 'a','b','c',...(NOTE THE MISSING BLANKS). This is - because internally the options will be parsed as an array, leaving the - first value the first element in the array, and so forth. If you want - to specify a MIME character set you can define it in the - transformation\_options. You have to put that outside of the pre- - defined options of the specific mime-transform, as the last value of - the set. Use the format "'; charset=XXX'". If you use a transform, for - which you can specify 2 options and you want to append a character - set, enter "'first parameter','second parameter','charset=us-ascii'". - You can, however use the defaults for the parameters: "'','','charset - =us-ascii'". The default options can be configured using - :config:option:`$cfg['DefaultTransformations']` - -.. _transformationsfiles: - -File structure -++++++++++++++ - -All specific transformations for mimetypes are defined through class -files in the directory 'libraries/classes/Plugins/Transformations/'. Each of -them extends a certain transformation abstract class declared in -libraries/classes/Plugins/Transformations/Abs. - -They are stored in files to ease up customization and easy adding of -new transformations. - -Because the user cannot enter own mimetypes, it is kept sure that -transformations always work. It makes no sense to apply a -transformation to a mimetype the transform-function doesn't know to -handle. - -There is a file called '*transformations.lib.php*' that provides some -basic functions which can be included by any other transform function. - -The file name convention is ``[Mimetype]_[Subtype]_[Transformation -Name].class.php``, while the abtract class that it extends has the -name ``[Transformation Name]TransformationsPlugin``. All of the -methods that have to be implemented by a transformations plug-in are: - -#. getMIMEType() and getMIMESubtype() in the main class; -#. getName(), getInfo() and applyTransformation() in the abstract class - it extends. - -The getMIMEType(), getMIMESubtype() and getName() methods return the -name of the MIME type, MIME Subtype and transformation accordingly. -getInfo() returns the transformation's description and possible -options it may receive and applyTransformation() is the method that -does the actual work of the transformation plug-in. - -Please see the libraries/classes/Plugins/Transformations/TEMPLATE and -libraries/classes/Plugins/Transformations/TEMPLATE\_ABSTRACT files for adding -your own transformation plug-in. You can also generate a new -transformation plug-in (with or without the abstract transformation -class), by using -:file:`scripts/transformations_generator_plugin.sh` or -:file:`scripts/transformations_generator_main_class.sh`. - -The applyTransformation() method always gets passed three variables: - -#. **$buffer** - Contains the text inside of the column. This is the - text, you want to transform. -#. **$options** - Contains any user-passed options to a transform - function as an array. -#. **$meta** - Contains an object with information about your column. The - data is drawn from the output of the `mysql\_fetch\_field() - <https://www.php.net/mysql_fetch_field>`_ function. This means, all - object properties described on the `manual page - <https://www.php.net/mysql_fetch_field>`_ are available in this - variable and can be used to transform a column accordingly to - unsigned/zerofill/not\_null/... properties. The $meta->mimetype - variable contains the original MIME-type of the column (i.e. - 'text/plain', 'image/jpeg' etc.) diff --git a/srcs/phpmyadmin/doc/html/_sources/two_factor.txt b/srcs/phpmyadmin/doc/html/_sources/two_factor.txt deleted file mode 100644 index 0b5c1ed..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/two_factor.txt +++ /dev/null @@ -1,69 +0,0 @@ -.. _2fa: - -Two-factor authentication -========================= - -.. versionadded:: 4.8.0 - -Since phpMyAdmin 4.8.0 you can configure two-factor authentication to be -used when logging in. To use this, you first need to configure the -:ref:`linked-tables`. Once this is done, every user can opt-in for the second -authentication factor in the :guilabel:`Settings`. - -When running phpMyAdmin from the Git source repository, the dependencies must be installed -manually; the typical way of doing so is with the command: - -.. code-block:: sh - - composer require pragmarx/google2fa-qrcode - -Or when using a hardware security key with FIDO U2F: - -.. code-block:: sh - - composer require samyoul/u2f-php-server - -Authentication Application (2FA) --------------------------------- - -Using an application for authentication is a quite common approach based on HOTP and -`TOTP <https://en.wikipedia.org/wiki/Time-based_One-time_Password_Algorithm>`_. -It is based on transmitting a private key from phpMyAdmin to the authentication -application and the application is then able to generate one time codes based -on this key. The easiest way to enter the key in to the application from phpMyAdmin is -through scanning a QR code. - -There are dozens of applications available for mobile phones to implement these -standards, the most widely used include: - -* `FreeOTP for iOS, Android and Pebble <https://freeotp.github.io/>`_ -* `Authy for iOS, Android, Chrome, OS X <https://authy.com/>`_ -* `Google Authenticator for iOS <https://apps.apple.com/us/app/google-authenticator/id388497605>`_ -* `Google Authenticator for Android <https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2>`_ -* `LastPass Authenticator for iOS, Android, OS X, Windows <https://lastpass.com/auth/>`_ - -Hardware Security Key (FIDO U2F) --------------------------------- - -Using hardware tokens is considered to be more secure than a software based -solution. phpMyAdmin supports `FIDO U2F <https://en.wikipedia.org/wiki/Universal_2nd_Factor>`_ -tokens. - -There are several manufacturers of these tokens, for example: - -* `youbico FIDO U2F Security Key <https://www.yubico.com/fido-u2f/>`_ -* `HyperFIDO <https://www.hypersecu.com/tmp/products/hyperfido>`_ -* `Trezor Hardware Wallet <https://trezor.io/?offer_id=12&aff_id=1592&source=phpmyadmin>`_ can act as an `U2F token <https://wiki.trezor.io/User_manual:Two-factor_Authentication_with_U2F>`_ -* `List of Two Factor Auth (2FA) Dongles <https://www.dongleauth.info/dongles/>`_ - -.. _simple2fa: - -Simple two-factor authentication --------------------------------- - -This authentication is included for testing and demonstration purposes only as -it really does not provide two-factor authentication, it just asks the user to confirm login by -clicking on the button. - -It should not be used in the production and is disabled unless -:config:option:`$cfg['DBG']['simple2fa']` is set. diff --git a/srcs/phpmyadmin/doc/html/_sources/user.txt b/srcs/phpmyadmin/doc/html/_sources/user.txt deleted file mode 100644 index a98e2cb..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/user.txt +++ /dev/null @@ -1,16 +0,0 @@ -User Guide -========== - -.. toctree:: - :maxdepth: 2 - - settings - two_factor - transformations - bookmarks - privileges - relations - charts - import_export - themes - other diff --git a/srcs/phpmyadmin/doc/html/_sources/vendors.txt b/srcs/phpmyadmin/doc/html/_sources/vendors.txt deleted file mode 100644 index dfbff01..0000000 --- a/srcs/phpmyadmin/doc/html/_sources/vendors.txt +++ /dev/null @@ -1,32 +0,0 @@ -Distributing and packaging phpMyAdmin -===================================== - -This document is intended to give pieces of advice to people who want to -redistribute phpMyAdmin inside other software packages such as Linux -distribution or some all in one package including web server and MySQL -server. - -Generally, you can customize some basic aspects (paths to some files and -behavior) in :file:`libraries/vendor_config.php`. - -For example, if you want setup script to generate a config file in var, change -``SETUP_CONFIG_FILE`` to :file:`/var/lib/phpmyadmin/config.inc.php` and you -will also probably want to skip directory writable check, so set -``SETUP_DIR_WRITABLE`` to false. - -External libraries ------------------- - -phpMyAdmin includes several external libraries, you might want to -replace them with system ones if they are available, but please note -that you should test whether the version you provide is compatible with the -one we ship. - -Currently known list of external libraries: - -js/jquery - jQuery js framework and various jQuery based libraries. - -vendor/ - The download kit includes various Composer packages as - dependencies. |