session
support
(see
FAQ 1.31)
, the Standard PHP Library (SPL) extension and JSON support.
zip
extension.mcrypt
extension
is strongly suggested for most users and is required for
64–bit machines. Not using mcrypt will cause phpMyAdmin to
load pages significantly slower.
libxml
extension.phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as a single database. To accomplish the latter you'll need a properly set up MySQL user who can read/write only the desired database. It's up to you to look up the appropriate part in the MySQL manual.
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.
1) phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats)
dumps and CSV exports if you use
PHP with Zlib support (--with-zlib
) and/or Bzip2 support
(--with-bz2
). Proper support may also need changes in
php.ini
.
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 "Privileges" page can be used for this.
Warning for Mac users:
if you are on a Mac
OS version before
OS X, StuffIt unstuffs with
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
Mac-style end of lines character
("\r
").
phpMyAdmin-x.x.x-all-languages.tar.gz
.
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.config.inc.php
, but now a wizard-style setup script is
provided for those who prefer a graphical installation. Creating a
config.inc.php
is still a quick way to get started and needed for some advanced features.
config.inc.php
(you can copy
config.sample.inc.php
to get minimal configuration
file) in the main (top-level) phpMyAdmin directory (the one
that contains index.php
). phpMyAdmin first loads
libraries/config.default.php
and then overrides those
values with anything found in config.inc.php
. If the
default value is okay for a particular setting, there is no
need to include it in config.inc.php
. You'll need a
few directives to get going, a simple configuration may look
like this:
<?php $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice $i=0; $i++; $cfg['Servers'][$i]['auth_type'] = 'cookie'; ?>Or, if you prefer to not be prompted every time you log in:
<?php $i=0; $i++; $cfg['Servers'][$i]['user'] = 'root'; $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password $cfg['Servers'][$i]['auth_type'] = 'config'; ?>For a full explanation of possible configuration values, see the Configuration Section of this document.
config.inc.php
, you can use the
Setup Script. First you must
manually create a folder config
in the phpMyAdmin
directory. This is a security measure. On a Linux/Unix system you
can use the following commands:
cd phpMyAdmin mkdir config # create directory for saving chmod o+rw config # give it world writable permissionsAnd to edit an existing configuration, copy it over first:
cp config.inc.php config/ # copy current configuration for editing chmod o+w config/config.inc.php # give it world writable permissionsOn other platforms, simply create the folder and ensure that your web server has read and write access to it. FAQ 1.26 can help with this.
setup/
in your browser. Note that changes are not saved to
disk until explicitly choose Save
from the
Configuration area of the screen. Normally the script saves
the new config.inc.php to the config/
directory, but if
the webserver does not have the proper permissions you may see the
error "Cannot load or save configuration." Ensure that the
config/
directory exists and has the proper permissions -
or use the Download
link to save the config file locally
and upload (via FTP or some similar means) to the proper location.
config/
directory and the permissions must be reset, again
as a security measure:
mv config/config.inc.php . # move file to current directory chmod o-rw config.inc.php # remove world read and write permissions rm -rf config # remove not needed directoryNow 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 which the setup script does not provide.
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 .htaccess file or switch to using
auth_type
cookie or http. See the
multi–user sub–section of this
FAQ for additional
information, especially
FAQ 4.4../libraries
and
./setup/lib
subfolders in your webserver configuration. For
Apache you can use supplied .htaccess file in that folder, for other
webservers, you should configure this yourself. Such configuration
prevents from possible path exposure and cross side scripting
vulnerabilities that might happen to be found in that code.robots.txt
file in root of
your webserver or limit access by web server configuration, see
FAQ 1.42.
For a whole set of new features (bookmarks, comments, SQL-history, tracking mechanism, PDF-generation, column contents transformation, 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).
Please look at your ./examples/
directory, where you should find a
file called create_tables.sql. (If you are using a Windows server, pay
special attention to
FAQ 1.23).
If you already had this infrastructure and upgraded to MySQL 4.1.2 or newer, please use ./examples/upgrade_tables_mysql_4_1_2+.sql and then create new tables by importing ./examples/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 ./examples/create_tables.sql file, you should specify the table names in your ./config.inc.php file. The directives used for that can be found in the Configuration section. You will also need to have a controluser with the proper rights to those tables (see section Using authentication modes below).
Simply copy ./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 6, remove a set_magic_quotes_runtime(0);
statement that you might find near the end of your configuration file.
You should not copy libraries/config.default.php
over config.inc.php
because the default configuration file
is version-specific.
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 SQL script
found in examples/upgrade_tables_mysql_4_1_2+.sql
.
--skip-show-database
.SELECT
privilege on the `mysql`.`user` (all columns except
`Password`), `mysql`.`db` (all columns), `mysql`.`host`
(all columns) and `mysql`.`tables_priv` (all columns except
`Grantor` and `Timestamp`) tables.config.inc.php
file under the
$cfg['Servers'][$i]['controluser']
and
$cfg['Servers'][$i]['controlpass']
settings.pma
as the
controluser and pmapass
as the controlpass, but this is
only an example: use something else in your file! Input these
statements from the phpMyAdmin SQL
Query window or mysql command–line client.localhost
with the webserver's host
if it's not the same as the MySQL server's one.
GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass'; GRANT SELECT ( Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv, Grant_priv, References_priv, Index_priv, Alter_priv, Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv, Execute_priv, Repl_slave_priv, Repl_client_priv ) ON mysql.user TO 'pma'@'localhost'; GRANT SELECT ON mysql.db TO 'pma'@'localhost'; GRANT SELECT ON mysql.host TO 'pma'@'localhost'; GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv) ON mysql.tables_priv TO 'pma'@'localhost';If you want to use the many new relation and bookmark features:
GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost';(this of course requires that your phpMyAdmin configuration storage be set up).
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.
mcrypt
extension will speed up access considerably, but is
not required.
The Swekey is a low cost authentication USB key that can be used in
web applications.
When Swekey authentication is activated, phpMyAdmin requires the
users's Swekey to be plugged before entering the login page (currently
supported for cookie authentication mode only). Swekey Authentication is
disabled by default.
To enable it, add the following line to config.inc.php
:
$cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
You then have to create the swekey.conf
file that will associate
each user with their Swekey Id. It is important to place this file outside
of your web server's document root (in the example, it is located in /etc
). A self documented sample file is provided
in the examples
directory. Feel free to use it with your own
users' information.
If you want to purchase a Swekey please visit
http://phpmyadmin.net/auth_key
since this link provides funding for phpMyAdmin.
Warning for Mac
users: PHP does not seem to like
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.
Configuration note:
Almost all configurable data is placed in config.inc.php
. If this file
does not exist, please refer to the Quick install
section to create one. This file only needs to contain the parameters you want to
change from their corresponding default value in
libraries/config.default.php
.
The parameters which relate to design (like colors) are placed in
themes/themename/layout.inc.php
. You might also want to create
config.footer.inc.php and config.header.inc.php files to add
your site specific code to be included on start and end of each page.
http://www.your_web.net/path_to_your_phpMyAdmin_directory/
.
Note also that the URL on
some web servers are case–sensitive.
Don’t forget the trailing slash at the end.TRUE
to stop this message from appearing.TRUE
to stop this message
from appearing.TRUE
to stop this message
from appearing.true
allows a page located on a different
domain to call phpMyAdmin inside a frame, and is a potential security
hole allowing cross-frame scripting attacks../libraries/config.default.php
, there is only one section for
server definition, however you can put as many as you need in
./config.inc.php
, copy that block or needed parts (you don't
have to define all settings, just those you need to change).mysql
command–line client, issue the status
command.
Among the resulting information displayed will be the socket used.'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.mysql
:
The classic MySQL extension.mysqli
:
The improved MySQL extension. This extension became available
with PHP 5.0.0 and is the recommended way to connect to a server
running MySQL 4.1.x or newer.--skip-show-database
, to enable a multi-user installation
(HTTP or cookie
authentication mode).SELECT
privilege on the
mysql.user (all columns except "Password"),
mysql.db (all columns) and mysql.tables_priv (all columns
except "Grantor" and "Timestamp") tables.
This account is used to check what databases the user will see at
login.['HTTP'|'http'|'cookie'|'config'|'signon']
$auth_type = 'config'
)
is the plain old way: username and password are stored in
config.inc.php.$auth_type = 'cookie'
) as introduced in
2.2.3 allows you to log in as any valid MySQL user with the
help of cookies. Username and password are stored in
cookies during the session and password is deleted when it
ends. This can also allow you to log in in arbitrary server if
$cfg['AllowArbitraryServer']
enabled.
$auth_type = 'HTTP'
) as introduced in 1.3.0
allows you to log in as any valid MySQL user via HTTP-Auth.$auth_type = 'signon'
)
as introduced in 2.10.0 allows you to log in from prepared PHP
session data or using supplied PHP script. This is useful for implementing single signon
from another application.
Sample way how to seed session is in signon example: examples/signon.php
.
There is also alternative example using OpenID - examples/openid.php
and
example for scripts based solution - examples/signon-script.php
.
You need to
configure session name or script to be executed and signon
URL to use
this authentication method.'my\_db'
and not
'my_db'
).$cfg['Servers'][$i]['only_db'] = array('db1', 'db2');
$cfg['Servers'][$i]['only_db'] = array('db3', 'db4', '*');
instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
order.$cfg['Servers'][$i]['hide_db'] = '^a';and to hide both "db1" and "db2" use
$cfg['Servers'][$i]['hide_db'] = '^(db1|db2)$';More information on regular expressions can be found in the PCRE pattern syntax portion of the PHP reference manual.
$cfg['Servers'][$i]['pmadb']
. For a multi-user installation,
set this parameter to the name of your central database containing
the phpMyAdmin configuration storage.$cfg['Servers'][$i]['bookmarktable']
$cfg['Servers'][$i]['relation']
master_db
must be the same as foreign_db
. Those columns have been put in
future development of the cross-db relations.
$cfg['Servers'][$i]['table_info']
(e.g.
'pma_table_info')$cfg['Servers'][$i]['table_coords']
and
$cfg['Servers'][$i]['pdf_pages']
$cfg['Servers'][$i]['column_info']
(e.g.
'pma_column_info')ALTER TABLE `pma_column_comments` ADD `mimetype` VARCHAR( 255 ) NOT NULL, ADD `transformation` VARCHAR( 255 ) NOT NULL, ADD `transformation_options` VARCHAR( 255 ) NOT NULL;and remember that the Variable in config.inc.php has been renamed from
$cfg['Servers'][$i]['column_comments']
to
$cfg['Servers'][$i]['column_info']
$cfg['Servers'][$i]['history']
(e.g. 'pma_history')
$cfg['Servers'][$i]['recent']
(e.g. 'pma_recent')$cfg['Servers'][$i]['table_uiprefs']
(e.g. 'pma_table_uiprefs')$cfg['Servers'][$i]['tracking']
(e.g. 'pma_tracking')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
$cfg['Servers'][$i]['userconfig']
$cfg['Servers'][$i]['designer_coords']
(e.g. 'pma_designer_coords')
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.
'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. '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.<'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.'all' -> 0.0.0.0/0 'localhost' -> 127.0.0.1/8 'localnetA' -> SERVER_ADDRESS/8 'localnetB' -> SERVER_ADDRESS/16 'localnetC' -> SERVER_ADDRESS/24Having 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'
.xxx.xxx.xxx.xxx
(an exact IP address)xxx.xxx.xxx.[yyy-zzz]
(an IP address range)xxx.xxx.xxx.xxx/nn
(CIDR, Classless Inter-Domain Routing type IP addresses)xxx.xxx.xxx.xx[yyy-zzz]
(partial
IP address range)INFORMATION_SCHEMA
to retrieve information (use SHOW
commands instead), because of speed issues when many databases are present. Currently used in some parts of the code, more to come.
SHOW
DATABASES
command used to fetch the name of available databases will
probably be too slow, so it can be replaced by faster commands (see
libraries/config.default.php
for examples).
get_login_credentials
which returns list of username and
password, accepting single parameter of existing username (can be empty).
See examples/signon-script.php
for an example.
phpMyAdmin
, because
this is session which phpMyAdmin uses internally. Takes effect only if
SignonScript
is not configured.
TABLE STATUS
outputs for specific databases on this server (in some cases TABLE STATUS
can be very slow, so you may want to cache it). APC is used (if the PHP extension is available, if not, this setting is ignored silently). You have to provide StatusCacheLifetime.true
.
TABLE STATUS
cache if StatusCacheDatabases is used.
$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.$cfg['ServerDefault']
MUST be set to that server.$cfg['blowfish_secret']
.
session.gc_maxlifetime
not lower than the value of $cfg['LoginCookieValidity'].TRUE
.main.php
.main
)
or in a new one (new
). Note: use new
if you are
linking to phpmyadmin.net
.30
. To disable the filter completely some high number
can be used (e.g. 9999)$cfg['Servers'][$i]['verbose']
.
disable_functions = phpinfo()Also note that enabling the "Change password " link has no effect with "config" authentication mode: because of the hard coded password value in the configuration file, end users can't be allowed to change their passwords.
DESC
|ASC
|SMART
]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.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.TRUE
, will display icons instead of text for db and table
properties links (like 'Browse', 'Select', 'Insert', ...).'both'
if you want icons AND text.FALSE
, will only show text.'^(cs|en)'
.$cfg['Export']['charset']
and $cfg['Import']['charset']
.
//TRANSLIT
is
used, so that invalid characters will be transliterated.X-Forwarded-For
) header coming from the proxy 1.2.3.4:
$cfg['TrustedProxies'] = array('1.2.3.4' => 'HTTP_X_FORWARDED_FOR');The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the client's IP address as usual.
FALSE
. Default is TRUE
.
1000
.
true
prevents this kind
of multiple maintenance operation. Default is false
.
themes/themename/layout.inc.php
.
themes/themename/layout.inc.php
.themes/themename/layout.inc.php
.TRUE
activates the navi pointer (when LeftFrameLight
is FALSE
).themes/themename/layout.inc.php
.
themes/themename/layout.inc.php
.themes/themename/layout.inc.php
.
themes/themename/layout.inc.php
.
themes/themename/layout.inc.php
.arial, sans-serif
.themes/themename/layout.inc.php
.monospace
. This one is used in textarea.themes/themename/layout.inc.php
.TRUE
you can enable the
display of column comments in Browse or Property display. In browse
mode, the comments are shown inside the header. In property mode,
comments are displayed using a CSS-formatted dashed-line below the
name of the column. The comment is shown as a tool-tip for that column.
$cfg_SQLValidator
.open_basedir
for uploaded
files, see FAQ
1.11.
open_basedir
restriction, you need to create a
temporary directory in some directory accessible by the web
server. However for security reasons, this directory should be outside
the tree published by webserver. If you cannot avoid having this
directory published by webserver, place at least an empty
index.html
file there, so that directory listing is not
possible.
chown www-data:www-data tmp chmod 700 tmpIf you cannot change owner of the directory, you can achieve a similar setup using ACL:
chmod 700 tmp setfacl -m "g:www-data:rwx" tmp setfacl -d -m "g:www-data:rwx" tmpIf neither of above works for you, you can still make the directory
chmod 777
, but it might impose risk of other users on
system reading and writing data in this directory.
quick
to display the minimum number of options to configurecustom
to display every available option to configurecustom-no-form
same as custom
but does not display the option of using quick exportSQL
link
or icon is always displayed on the left panel. If JavaScript is enabled in
your browser, a click on this opens a distinct query window, which is
a direct interface to enter SQL queries. Otherwise, the right panel
changes to display a query box.$cfg['QueryWindowWidth']
and $cfg['QueryWindowHeight']
- both integers for the size in pixels. Note that normally, those
parameters will be modified in layout.inc.php
for the
theme you are using.$cfg['EditInWindow']
is set to true, a click on [Edit]
from the results page (in the "Showing Rows" section)
opens the query window and puts the current query
inside it. If set to false, clicking on the link puts the SQL
query in the right panel's query box.
$cfg['QueryHistoryDB']
is set to TRUE
, all your Queries are logged
to a table, which has to be created by you (see $cfg['Servers'][$i]['history']). If set to FALSE,
all your queries will be appended to the form, but only as long as
your window is opened they remain saved.
$cfg['QueryHistoryDB']
is set to TRUE
you can specify the amount of
saved history items using $cfg['QueryHistoryMax']
.
$cfg['QueryWindowDefTab']
you can specify the
default tab to be used when opening the query window. It can be set to
either 'sql', 'files', 'history' or 'full'.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.
SELECT COUNT ... LIMIT
. Setting this to 0 bypasses
any row counting.
'closed'
, the visual sliders are initially in a
closed state. A value of 'open'
does the reverse. To completely
disable all visual sliders, use 'disabled'
.$cfg
array)
that users can't set through user preferences. For possible values, refer
to libraries/config/user_preferences.forms.php
.cfg['ThemePath']
).html
|none
]'none'
.
em
|px
|pt
|ex
]$cfg['SQP']['fmtInd']
you can change the amount of this indent.
$cfg['SQP']['fmtIndUnit']
which
specifies the units of the indent amount that you specified. This is
used via stylesheets."#...\n"
"-- ...\n"
"/*...*/"
"("
")"
","
"."
";"
"@foo"
"
'
`
anonymous
and any password, so we use those by default. Instead, if
you have an account with them, you can put your login details
here, and it will be used in place of the anonymous login.first_timestamp
, which is used for first timestamp column
in table. To enable transformations, you have to setup the column_info
table
and the proper directives. Please see the Configuration
section 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 on the official phpMyAdmin homepage.
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'.
All mimetypes and their transformations are defined through single files in the directory 'libraries/transformations/'.
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.
One can, however, use empty mime-types and global transformations which should work for many mimetypes. You can also use transforms on a different mimetype than what they where built for, but pay attention to option usage as well as what the transformation does to your column.
There is a file called 'transformations.lib.php' that provides some basic functions which can be included by any other transform function.
There are 5 possible file names:
[mimetype]_[subtype]__[transform].inc.php
PMA_transform_[mimetype]_[subtype]__[transform]()
'.text_html__formatted.inc.php
PMA_transform_text_html__formatted()
[mimetype]__[transform].inc.php
PMA_transform_[mimetype]__[transform]()
'.text__formatted.inc.php
PMA_transform_text__formatted()
[mimetype]_[subtype].inc.php
text_plain.inc.php
[mimetype].inc.php
text.inc.php
global__[transform].inc.php
PMA_transform_global__[transform]()
'.global__formatted
PMA_transform_global__formatted()
So generally use '_' to split up mimetype and subtype, and '__' to provide a transform function.
All filenames containing no '__' in themselves are not shown as valid transform functions in the dropdown.
Please see the libraries/transformations/TEMPLATE file for adding your own transform function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype without a transform function.
To create a new transform function please see
libraries/transformations/template_generator.sh
.
To create a new, empty mimetype please see
libraries/transformations/template_generator_mimetype.sh
.
A transform function always gets passed three variables:
Additionally you should also provide additional function to provide
information about the transformation to the user. This function should
have same name as transformation function just with appended
_info
suffix. This function accepts no parameters and returns
array with information about the transformation. Currently following keys
can be used:
info
Please have a look at our Link section on the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's features and or interface.
Try to set the $cfg['OBGzip']
directive to FALSE
in your config.inc.php file and the
zlib.output_compression
directive to Off
in your php
configuration file.
You should first try the latest versions of Apache (and possibly MySQL).
See also the
FAQ 1.1
entry about PHP bugs with output buffering.
If your server keeps crashing, please ask for help in the various Apache
support groups.
You just forgot to read the install.txt file from the PHP distribution. Have a look at the last message in this bug report from the official PHP bug database.
This is a known problem with the PHP ISAPI filter: it's not so stable. Please use instead the cookie authentication mode.
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 libraries/Header.class.php
and index.php.
These features are based on the gzencode()
and bzcompress()
PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
or not, and so on). So, you must have Zlib/Bzip2
support (--with-zlib
and --with-bz2
).
Your uploaded file is saved by PHP in the "upload dir", as
defined in 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:
mkdir /tmp/php
chown apache.apache /tmp/php
chmod 600 /tmp/php
upload_tmp_dir = /tmp/php
in php.iniAs suggested by "Rob M" in the phpWizard forum, add this line to your httpd.conf:
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
It seems to clear up many problems between Internet Explorer and SSL.
Since version 2.2.4, phpMyAdmin supports servers with open_basedir restrictions. However you need to create temporary directory and configure it as $cfg['TempDir']. The uploaded files will be moved there, and after execution of your SQL commands, removed.
The MySQL manual explains how to reset the permissions.
In previous MySQL versions, the User
and Password
columns
were named user
and password
. Please modify your column
names to align with current standards.
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 upload_max_filesize
, memory_limit
and
post_max_size
in the php.ini configuration file.
All of these three settings limit the maximum size of data that can be
submitted and handled by PHP. One user also said that
post_max_size
and memory_limit
need 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:
source filename.sql
. Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
connect to your MySQL server using PHP's classic
MySQL extension as well as the
improved MySQL extension (MySQLi) that
is available in PHP 5.0. The latter one should be used unless you have a
good reason not to do so.
When compiling PHP, we strongly recommend that you manually link the MySQL
extension of your choice to a MySQL client library of at least the same
minor version since the one that is bundled with some PHP distributions is
rather old and might cause problems
(see FAQ 1.17a).
MariaDB is also supported
(versions 5.1 and 5.2 were tested).
Since phpMyAdmin 3.5 Drizzle is supported.
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
FAQ 1.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
with the proper client library to match your MySQL installation. Your
chosen extension is specified in $cfg['Servers'][$i]['extension'].
More information (and several workarounds) are located in the
MySQL Documentation.
The "FPDF" library we're using for this feature requires some
special files to use font faces.
Please refers to the FPDF manual to build
these files.
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 mysql.so or php_mysql.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.
In php.ini, set mysql.max_links
higher than 1.
This is most likely because in php.ini, your file_uploads
parameter is not set to "on".
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]:
set-variable = lower_case_table_names=0
Next, save the file and restart the MySQL service. You can always check the value of this directive using the query
SHOW VARIABLES LIKE 'lower_case_table_names';
A tip from Jose Fandos: put a comment on the following two lines in httpd.conf, like this:
# 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.
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.
This is a PHP bug that occur when GZIP output buffering is enabled. If you turn off it (by $cfg['OBGzip'] = false in config.inc.php), it should work. This bug will be fixed in PHP 5.0.0.
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.
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:
SetOutputFilter PHP SetInputFilter PHP
and
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:
#SetOutputFilter PHP #SetInputFilter PHP
This problem is known to happen when the server is running Turck MMCache but upgrading MMCache to version 2.3.21 solves the problem.
Yes.
Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch is still maintained.
Yes. This procedure was tested with phpMyAdmin 2.6.1, PHP 4.3.9 in ISAPI mode under IIS 5.1.
php.ini
file, set cgi.rfc2616_headers = 0
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
.Custom Errors
, select the range of 401;1
through
401;5
and click the Set to Default
button. Yes. Out of the box, you can use URLs like
http://server/phpMyAdmin/index.php?server=X&db=database&table=table&target=script. For server
you use the server number which refers to
the order of the server paragraph in config.inc.php
.
Table and script parts are optional. If you want
http://server/phpMyAdmin/database[/table][/script] URLs, you need to do
some configuration. Following lines apply only for Apache web server. First make sure,
that you have enabled some features within global configuration. You need
Options FollowSymLinks
and AllowOverride
FileInfo
enabled for directory where phpMyAdmin is installed and
you need mod_rewrite to be enabled. Then you just need to create following
.htaccess file in root folder of phpMyAdmin installation
(don't forget to change directory name inside of it):
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]
Yes. However you need to pass authentication variable to CGI using following rewrite rule:
RewriteEngine On RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
There can be many explanations to this and a look at your server's error log file might give a clue.
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.
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 primary key or with textual 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:
You can also disable the warning using the
SuhosinDisableWarning
directive.
Be sure that you have enabled SSLOptions
and StdEnvVars
in your Apache configuration. See http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions.
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:
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://host/~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.
ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin ProxyPassReverse /mirror/foo/ http://backend.example.com/%7Euser/phpmyadmin ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
See http://httpd.apache.org/docs/2.2/mod/mod_proxy.html for more details.
The MySQL server's privilege tables are not up to date, you need to run
the mysql_upgrade
command on the server.
You can add various rules to .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.
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]
Edit your 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. We also got a report from a user under
IIS, that used
a zipped distribution kit: the file libraries/Config.class.php
contained an end-of-line character (hex 0A) at the end; removing this character
cleared his errors.
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.
For RedHat users, Harald Legner suggests this on the mailing list:
On my RedHat-Box the socket of MySQL is /var/lib/mysql/mysql.sock. In your php.ini you will find a line
mysql.default_socket = /tmp/mysql.sock
change it to
mysql.default_socket = /var/lib/mysql/mysql.sock
Then restart apache and it will work.
Here is a fix suggested by Brad Ummer:
./mysqladmin variables
, and this should give you a bunch of
info about your MySQL server, including the socket
(/tmp/mysql.sock, for example).Have also a look at the corresponding section of the MySQL documentation.
Try to set the $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.
Check the value you set for the $cfg['PmaAbsoluteUri'] directive in the phpMyAdmin configuration file.
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 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
TCP connection.
Themes are configured with
$cfg['ThemePath'],
$cfg['ThemeManager'] and
$cfg['ThemeDefault'].
Under $cfg['ThemePath'], 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 $cfg['ThemeManager']
is enabled, you can select your favorite theme on the main page. Your
selected theme will be stored in a cookie.
To create a theme:
themes
)layout.inc.php
in "your_theme_name"info.inc.php
in "your_theme_name" to
contain your chosen theme name, that will be visible in user interface In theme directory there is file info.inc.php
which contains
theme verbose name, theme generation and theme version. These versions and
generations are enumerated from 1 and do not have any direct dependence on
phpMyAdmin version. Themes within same generation should be backwards
compatible - theme with version 2 should work in phpMyAdmin requiring
version 1. Themes with different generation are incompatible.
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").
Here are a few points to check:
config.inc.php
, try to leave the
$cfg['PmaAbsoluteUri']
directive empty. See also
FAQ 4.7.
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).
php.ini
directive arg_separator.input
, a value
of ";" will cause this error. Replace it with "&;".
php.ini
directive session.save_path
does not exist or is read-only.
To be able to see a progress bar during your uploads, your server must have the APC extension, the 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 php.ini.
If using PHP 5.4.0 or higher, you must set session.upload_progress.enabled
to 1
in your php.ini.
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.
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 $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.
This is an InnoDB bug, see http://bugs.mysql.com/bug.php?id=21704.
The problem is that older versions of mysqldump
created invalid comments like this:
-- 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
#---------------------------------------------------------
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
In Relation view, being able to choose a table in another database,
or having more than one index column in the foreign key.
In Query-by-example (Query), automatic generation of the query
LEFT JOIN from the foreign table.
Your table neither have a primary key nor an unique one, so we must use a
long expression to identify this row. This causes problems to parse_url
function. The workaround is to create a primary or unique key.
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 on the official phpMyAdmin-homepage.
When MySQL is running in ANSI-compatibility mode, there are some major differences in how SQL is structured (see http://dev.mysql.com/doc/mysql/en/ansi-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 SQL statements. There is no workaround to this behaviour. News to this item will be posted in Bug report #816858
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 primary key, so that phpMyAdmin can use it for the Edit and Delete links.
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 $cfg['MaxExactCount'] for a way to modify those results, but this could have a serious impact on performance.
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.
This has been a known limitation of phpMyAdmin since the beginning and it's not likely to be solved in the future.
There is no reliable way to differentiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.
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.
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 HTTP or cookie authentication. See the install section on "Using HTTP authentication".
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 .htaccess files, for example).
If other people have telnet access to your server, you should use
phpMyAdmin's HTTP or cookie authentication features.
Suggestions:
chmod 660
.
Check 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.
This could happen for several reasons:
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).
If you have existing rules from an old .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
$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 IP blocks.
//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', );
This happens if you are using a URL to start phpMyAdmin which is different than the one set in your $cfg['PmaAbsoluteUri']. For example, a missing "www", or entering with an IP address while a domain name is defined in the config file.
When starting phpMyAdmin, you can use the db
, pma_username
, pma_password
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. Using pma_username
and pma_password
has been tested along with the usage of 'cookie' auth_type
.
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.
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.
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'. 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.
MS Internet Explorer seems to be really buggy about cookies, at least till version 6.
Upgrade to at least Internet Explorer 5.5 SP2.
Your table neither have a primary key nor an unique one, so we must use a
long URL to identify this row. There is a limit on the length of the URL in
those browsers, and this not happen in Netscape, for example. The
workaround is to create a primary or unique key, or use another browser.
Some browsers support right-clicking into the frame you want to refresh,
just do this in the right frame.
Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
Mozilla versions.
This is a Mozilla bug (see bug #26882 at
BugZilla).
This is a known Netscape 4.75 bug: it adds some line feeds when exporting data in octet-stream mode. Since we can't detect the specific Netscape version, we cannot workaround this bug.
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.
This issue has been reported by a OS X user, who adds that Chimera, Netscape and Mozilla do not have this problem.
This is a bug in Internet Explorer, other browsers do not behave this way.
Please upgrade to Opera7 at least.
Please upgrade to at least version 1.2.3.
Please check the following points:
PmaAbsoluteUri
setting
in config.inc.php
to an IP
address and you are starting
phpMyAdmin with a URL
containing a domain name, or the reverse situation.Many users have confirmed that the Tabbrowser Extensions plugin they installed in their Firefox is causing the problem.
LIMIT
clause is generated when I browse a table. This happens only when both of these conditions are met: using the
http
authentication mode and register_globals
being set
to On
on the server. It seems to be a browser-specific problem;
meanwhile use the cookie
authentication mode.
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.
Examine the SQL error with care. Often the problem is caused by
specifying a wrong column-type.
Common errors include:
VARCHAR
without a size argumentTEXT
or BLOB
with a size argumentAlso, look at the syntax chapter in the MySQL manual to confirm that your syntax is correct.
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.
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).
Click on a database or table name in the left frame, the properties will be
displayed. Then on the menu, click "Export", you can dump
the structure, the data, or both. This will generate standard 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
$cfg['ExecTimeLimit']
configuration variable.
For additional help on this subject, look for the word "dump" in
this document.
Click on a database name in the left frame, the properties will be
displayed. Select "Import" from the list
of tabs in the right–hand frame (or "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.
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:
CREATE TABLE REL_countries ( country_code char(1) NOT NULL default '', description varchar(10) NOT NULL default '', PRIMARY KEY (country_code) ) TYPE=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) ) TYPE=MyISAM; INSERT INTO REL_persons VALUES (11, 'Marc', 'S', ''); 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) ) TYPE=MyISAM; INSERT INTO REL_towns VALUES ('S', 'Sherbrooke'); INSERT INTO REL_towns VALUES ('M', 'Montréal');
To setup appropriate links and display information:
Then test like this:
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 FAQ 6.21 for an additional feature that "display column"
enables: drop-down list of possible values.
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?
No, it's MySQL that is doing silent column type changing.
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.
It means "average".
Structure:
Data:
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.
To use SQL Validator, you need PHP with XML, PCRE and PEAR support. In addition you need a SOAP support, either as a PHP extension or as a PEAR SOAP module.
To install PEAR SOAP module, run "pear install Net_Socket Net_URL
HTTP_Request Mail_Mime Net_DIME SOAP"
to get the necessary PEAR modules for
usage.
If you use the Validator, you should be aware that any SQL statement you submit will be stored anonymously (database/table/column names, strings, numbers replaced with generic values). The Mimer SQL Validator itself, is © 2001 Upright Database Technology. We utilize it as free SOAP service.
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.
You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages with many editing fields (table structure changes, row editing, etc.).
Slow down :). 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?
Any query you have executed can be stored as a bookmark on the page where the
results are displayed. You will find a button labeled 'Bookmark this query'
just at the end of the page.
As soon as you have stored a bookmark, it is related to the database you run
the query on. You can now access a bookmark dropdown on each page, the query
box appears on for that database.
Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
Just use the string /*[VARIABLE]*/ anywhere in your query. Everything
which is put into the value input box on the query box page will
replace the string "/*[VARIABLE]*/" in your stored query. Just be
aware of that you HAVE to create a valid query, otherwise your query won't be
even able to be stored in the database.
Also remember, that everything else inside the /*[VARIABLE]*/ string
for your query will remain the way it is, but will be stripped of the /**/
chars. So you can use:
/*, [VARIABLE] AS myname */
which will be expanded to
, VARIABLE as myname
in your query, where VARIABLE is the string you entered in the input box. If
an empty string is provided, no replacements are made.
A more complex example. Say you have stored this query:
SELECT Name, Address FROM addresses WHERE 1 /* AND Name LIKE '%[VARIABLE]%' */
Say, you now enter "phpMyAdmin" as the variable for the stored query,
the full query will be:
SELECT Name, Address FROM addresses WHERE 1 AND Name LIKE '%phpMyAdmin%'
You can use multiple occurrences of /*[VARIABLE]*/ in a single query (that is, multiple occurrences of the same variable).
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.
Your initial query which is going to be stored as a bookmark has to yield at
least one result row so
you can store the bookmark. You may have that to work around using well
positioned "/**/" comments.
You can simply include table in your LATEX documents, minimal sample
document should look like following one (assuming you have table
exported in file table.tex
):
\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
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.
See this bug report.
So if your users do not need those privileges, you can remove them and their
databases list will shorten.
You have to setup appropriate links between the tables, and also
setup the "display column" in the foreign table. See
FAQ
6.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
$cfg['ForeignKeyMaxLimit']
.
Yes. If a bookmark has the same label as a table name and it's not a public bookmark, it will be executed.
You can use
CSV for Microsoft Excel,
which works out of the box.
Since phpMyAdmin 3.4.5 support for direct export to Microsoft Excel
version 97 and newer was dropped.
Automatic migration of a table's pmadb-style column comments to the native ones is done whenever you enter Structure page for this table.
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.
In all places where phpMyAdmin accepts format strings, you can use
@VARIABLE@
expansion and
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@
@SERVER@
@VERBOSE@
@VSERVER@
@DATABASE@
@TABLE@
@COLUMNS@
@PHPMYADMIN@
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.
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 the wiki.
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 $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 $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:
cd phpMyAdmin mkdir tmp chmod o+rwx tmp
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.
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 'Search' tab. One of the sub-tabs in the 'Table Search' page is
'Zoom Search'.
Consider the table REL_persons in
FAQ 6.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 FAQ 6.7), 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 certail 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.
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.
Our Bug Tracker is located at
http://sf.net/projects/phpmyadmin/
under the Bugs section.
But please first discuss your bug with other users:
https://sourceforge.net/projects/phpmyadmin/forums.
Translations are very welcome and all you need to have are the language skills. The easiest way is to use our online translation service. You can check out all the possibilities to translate in the translate section on our website.
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.
Please refer to http://www.phpmyadmin.net/home_page/security.php
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
userStatus
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:
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.
You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature. It allows you to connect to local as well as remote servers. This requires you to enter server host name, username, password, port and the name of the database. Therefore you can now synchronize your databases placed on the same server or some remote server.
This feature is helpful for developers who need to replicate their database’s structure as well as data. Moreover, this feature not only helps replication but also facilitates the user to keep his/her database in sync with another database. Other than the full database, certain tables of the databases can also be synchronized.
You need to fill in the host name of the server, the username and password of an user account already there in MySQL. Port is by default populated with 3306 (MySQL default port). Then the name of the database should be mentioned at the end. All the information other than the port needs to be filled explicitly for the source as well as target servers.
After successfully passing through the authentication phase, the source and target database table names will be displayed. It will be a tabular representation.
On the left, are listed the source database table names. Some of the
names have a +
plus sign preceding them. This shows that these tables
are only present in source database and they need to be added to the
target database in order to synchronize the target database. The tables
whose names are not preceded by a +
sign are already present in the
target database.
On the right, are listed the target database table names. There are few
table names that have (not present)
appended after their names. This
means that these tables are to be created in target database in order to
synchronize target database with source database. Some table names
have a -
minus sign preceding them. This shows that these tables are
only present in target database and they will remain unchanged in the
target database. The column in the middle shows the difference between
the source and target corresponding tables.
The difference is depicted by the red and green buttons with S
and D
letters, indicating that either Structure or Data are not up to date. By
clicking on them, they will turn grey, what means that they will be synchronized.
Yes. This aspect of synchronization is currently limited to small tables, and they must have a primary key.
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.
Copyright (C) 1998-2000 Tobias Ratschiller <tobias_at_ratschiller.com> Copyright (C) 2001-2012 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 http://www.gnu.org/licenses/.
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".
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
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.
From Wikipedia, the free encyclopedia