| blob | 1ec1a56231640767b9366ada675c20638fb88625 |
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
16 </head>
20 <!-- TOP MENU -->
34 </ul>
39 phpMyAdmin homepage</a></li>
41 SourceForge phpMyAdmin project page</a></li>
42 <li>Local documents:
46 </ul>
47 </li>
48 <li>Documentation version:
50 </li>
51 </ul>
53 <!-- REQUIREMENTS -->
60 </li>
61 <li>You need GD2 support in PHP to display inline
63 original aspect ratio</li>
66 </ul>
67 </li>
71 PHP extension on your web server accelerates not only the login
72 phase but every other action that you do in phpMyAdmin.</li>
74 </ul>
76 <!-- INTRODUCTION -->
79 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
80 a single database. To accomplish the latter you'll need a properly set up
81 MySQL user who can read/write only the desired database. It's up to you to
82 look up the appropriate part in the MySQL manual.
83 </p>
88 <li>create, copy, drop, rename and alter databases, tables, fields and
89 indexes</li>
90 <li>maintenance server, databases and tables, with proposals on server
91 configuration</li>
92 <li>execute, edit and bookmark any
94 batch-queries</li>
97 </li>
104 OpenDocument Text and Spreadsheet,
107 </li>
111 <li>using Query-by-example (QBE), create complex queries automatically
112 connecting required tables</li>
114 your Database layout</li>
116 <li>transform stored data into any format using a set of predefined
117 functions, like displaying BLOB-data as image or download-link
118 </li>
124 </li>
125 </ul>
133 <!-- INSTALLATION -->
141 </ol>
144 phpMyAdmin does not apply any special security methods to the MySQL database
145 server. It is still the system administrator's job to grant permissions on
147 be used for this.
148 </p>
156 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
157 before uploading them to your server, as PHP seems not to like
163 <ol><li>Untar or unzip the distribution (be sure to unzip the subdirectories):
165 document root. If you don't have direct access to your document root,
166 put the files in a directory on your local machine, and, after step 3,
167 transfer the directory on your web server using, for example, ftp.</li>
168 <li>Ensure that all the scripts have the appropriate owner (if PHP is
169 running in safe mode, having some scripts with an owner different
170 from the owner of other scripts will be a
177 You can use the setup script provided in <tt><a
179 config file which should be sufficient for most users.
181 details. If you don’t like setup or want to fine tune your
182 configuration, open (or create in case of starting from scratch)
184 values for host, user, password and authentication mode to fit your
188 for an explanation of all values. Please also read the remainder
189 this Installation section for information about authentication modes
190 and the linked-tables infrastructure.</li>
191 <li>If you are using the
193 protect the phpMyAdmin installation directory because using
194 config does not require a user to
195 enter a password to access the phpMyAdmin installation. Use of an alternate
196 authentication method is recommended, for example with
203 <li>Open the file
205 in your browser. phpMyAdmin should now display a welcome screen
206 and your databases, or a login dialog if using
208 authentication mode.</li>
210 webserver configuration. For Apache you can use supplied .htaccess file
211 in that folder, for other webservers, you should configure this yourself.
212 Such configuration prevents from possible path exposure and cross side
213 scripting vulnerabilities that might happen to be found in that code.</li>
214 </ol>
221 simple. You follow the dialogs and this script prepares in memory the
222 configuration directives. You then have two choices for saving the
223 configuration file:</p>
225 <ol><li>Download it to your local workstation, then upload (for example with ftp)
226 to your main phpMyAdmin directory. In this case, you don't have to
228 necessary.</li>
230 </ol>
232 <p> For saving file on webserver, or loading
234 phpMyAdmin's top level directory and make it writable to web server. For
235 loading previous configuration, place it there (and make sure it has write
236 permissions for webserver). On a Linux/UNIX server you can use the
237 following commands:</p>
239 <pre>
240 cd phpMyAdmin
241 mkdir config # create directory for saving
242 chmod o+rw config # give it world writable permissions
243 # if you want to edit existing configuration:
244 cp config.inc.php config/ # copy current configuration
245 chmod o+w config/config.inc.php # give it world writable permissions
246 </pre>
249 directory and ensure that your web server has read/write access to it.
256 setup. After saving your configuration move the generated configuration to the top
261 <pre>
262 chmod o-rw config.inc.php # remove world read and write permissions
263 </pre>
265 <p> Please note that it does not allow to configure everything, so for some
266 additional features you still need to manually edit the configuration file.
267 </p>
271 <p> For a whole set of new features (bookmarks, comments,
274 transformation, etc.) you need to create a set of special tables. Those
275 tables can be located in your own database, or in a central database for a
276 multi-user installation (this database would then be accessed by the
277 controluser, so no other user should have rights to it).</p>
286 installation.</p>
291 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
292 that you may need special (administrator) privileges to create the database
293 and tables, and that the script may need some tuning, depending on the
294 database name.</p>
299 section</a>. You will also need to have a controluser with the proper rights
306 unpacked one. If your previous phpMyAdmin version was 2.3.0 or older, some
307 tweaking may be required because, as of 2.7.0, using those old config files
308 is no longer supported.</p>
312 is version-specific.</p>
318 where you want to give users access to their own database and don't want
319 them to play around with others.<br />
320 Nevertheless be aware that MS Internet Explorer seems to be really buggy
322 in this area!<br />
325 that your user/password pair are not in clear in the configuration file.
326 </li>
329 authentication modes are more secure: the MySQL login information does
330 not need to be set in the phpMyAdmin configuration file (except possibly
332 However, keep in mind that the password travels in plain text, unless
333 you are using the HTTPS protocol.<br />
334 In cookie mode, the password is stored, encrypted with the blowfish
335 algorithm, in a temporary cookie.</li>
338 your MySQL server is older than 4.1.2, or is running with
348 file under the
350 $cfg['Servers'][$i]['controluser']</a></tt> and
355 only an example: use something else in your file!</b> Input these
356 statements from the phpMyAdmin SQL Query window or mysql command–line
357 client.<br />
359 if it's not the same as the MySQL server's one.
361 <pre>
362 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
363 GRANT SELECT (
364 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
365 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
366 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
367 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
368 Execute_priv, Repl_slave_priv, Repl_client_priv
369 ) ON mysql.user TO 'pma'@'localhost';
370 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
371 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
372 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
373 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
375 If you are using an old MySQL version (below 4.0.2), please replace
376 the first GRANT SELECT query by this one:
378 <pre>
379 GRANT SELECT (
380 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
381 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
382 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
383 ) ON mysql.user TO 'pma'@'localhost';</pre>
385 ... and if you want to use the many new relation and bookmark features:
387 <pre>
389 </pre>
393 Of course, the above queries only work if your MySQL version supports
397 on a set of particular databases. Normally you shouldn't give global
398 privileges to an ordinary user, unless you understand the impact of those
399 privileges (for example, you are creating a superuser).<br />
403 <pre>
404 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
405 </pre>
407 What the user may now do is controlled entirely by the MySQL user
408 management system.<br />
410 authentication mode, you don't need to fill the user/password fields
412 array.</li>
413 </ul>
418 method and allows you to login as any valid MySQL user.</li>
419 <li>Is supported with most PHP configurations. For
432 mode.</li>
433 </ul>
437 <ul><li>You can use this method as a replacement for the
439 (for example, if you're running
442 <li>With this mode, the user can truly logout of phpMyAdmin and login back
443 with the same username.</li>
444 <li>If you want to login to arbitrary server see
449 not required.</li>
450 </ul>
454 <ul><li>This mode is the less secure one because it requires you to fill the
456 $cfg['Servers'][$i]['user']</a> and
458 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
459 can read your config.inc.php can discover your username and password).
460 <br />
467 is an entry explaining how to protect your configuration file.</li>
468 <li>For additional security in this mode, you may wish to consider the Host
469 authentication
471 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
473 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
474 directives.</li>
475 <li>Unlike cookie and http, does not require a user to log in when first
476 loading the phpMyAdmin site. This is by design but could allow any
477 user to access your installation. Use of some restriction method is
479 HTTP-AUTH directive or disallowing incoming HTTP requests at
480 one’s router or firewall will suffice (both of which
481 are beyond the scope of this manual but easily searchable with Google).
482 </ul>
484 <!-- CONFIGURATION -->
488 users:</span> PHP does not seem to like
492 before saving a script you have modified.</p>
497 section to create one. This file only needs to contain the parameters you want to
498 change from their corresponding default value in
501 <p> The parameters which relate to design (like colors) are placed in
504 your site specific code to be included on start and end of each page.</p>
508 (with full path) to your phpMyAdmin installation's directory.
511 some web servers are case–sensitive.
514 Starting with version 2.3.0, it is advisable to try leaving this
515 blank. In most cases phpMyAdmin automatically detects the proper
516 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
517 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
518 A good test is to browse a table, edit a row and save it. There should
519 be an error message if phpMyAdmin is having trouble auto–detecting
520 the correct value. If you get an error that this must be set or if
521 the autodetect code fails to detect your path, please post a bug
522 report on our bug tracker so we can improve the code.</dd>
526 with master / foreign – tables (see
528 <br />
529 If you tried to set this up and it does not work for you, have a look on
531 use it. You will find a link that will analyze why those features have
532 been disabled.<br />
533 If you do not want to use those features set this variable to
538 algorithm to encrypt the password.<br />
540 passphrase of your choice. It will be used internally by the blowfish
541 algorithm: you won’t be prompted for this passphrase. The maximum
546 MySQL servers. Therefore, a
548 been added which contains the login information for the different servers.
549 The first
551 contains the hostname of the first server, the second
553 the hostname of the second server, etc. In
555 server definition, however you can put as many as you need in
557 have to define all settings, just those you need to change).</dd>
561 $i-th MySQL-server. E.g. localhost.</dd>
566 ignores this port number and connects with the socket, so if you want
567 to connect to a port different from the default port, use
570 </dd>
574 To determine the correct socket, check your MySQL configuration or, using the
576 Among the resulting information displayed will be the socket used.</dd>
579 <dd>What type connection to use with the MySQL server. Your options are
581 is nearly guaranteed to be available on all MySQL servers, while
582 sockets are not supported on some platforms.<br /><br />
584 To use the socket mode, your MySQL server must be on the same machine
585 as the Web server.</dd>
588 <dd>What php MySQL extension to use for the connection. Valid options are:
589 <br /><br />
592 The classic MySQL extension. This is the recommended and default
593 method at this time.<br /><br />
596 The improved MySQL extension. This extension became available
597 with php 5.0.0 and is the recommended way to connect to a server
601 <dd>Whether to use a compressed protocol for the MySQL server connection
602 or not (experimental).<br />
608 </dt>
610 all relational features (see
612 and, for a MySQL server older than 4.1.2 or running with
615 authentication mode).<br /><br />
618 cookie authentication modes (or 'config'
619 authentication mode since phpMyAdmin 2.2.1), you need to supply the
624 This account is used to check what databases the user will see at
625 login.<br />
629 In phpMyAdmin versions before 2.2.5, those were called
634 <dd>Whether config or cookie or
636 should be used for this server.
638 is the plain old way: username and password are stored in
640 <li>'cookie' authentication mode
642 2.2.3 allows you to log in as any valid MySQL user with the
643 help of cookies. Username and password are stored in
644 cookies during the session and password is deleted when it
645 ends. This can also allow you to login in arbitrary server if
646 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
647 </li>
648 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in older versions)
649 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
650 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
651 </ul>
654 for more information.
655 </dd>
659 </dt>
660 <dd>
661 When using auth_type = 'config', this is the user/password-pair
662 which phpMyAdmin will use to connect to the
663 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
664 cookie authentication is used and should be empty.</dd>
666 <span
668 </dt>
669 <dd>
670 Allow attempt to login without password when login with password
671 fails. This can be used together with http authentication, when
672 authentication is done some other way and phpMyAdmin gets user name
673 from auth and uses empty password for connecting to MySQL. Password
674 login is still tried first, but as fallback, no password method is
675 tried.</dd>
678 </dt>
679 <dd>
680 If set to a (an array of) database name(s), only this (these) database(s)
681 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
682 database(s) name(s) may contain MySQL wildcards characters
686 This setting is an efficient way to lower the server load since the
687 latter does not need to send MySQL requests to build the available
689 privileges rules of the MySQL database server</span>. If set, it just
690 means only these databases will be displayed but
692 <br /><br />
694 An example of using more that one database:
696 <br /><br />
698 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
699 databases in the left frame, so that you can individually arrange your databases.<br />
700 If you want to have certain databases at the top, but don't care about the others, you do not
701 need to specify all other databases. Use:
703 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
704 order.</dd>
707 </dt>
708 <dd>Regular expression for hiding some databases. This only hides them
709 from listing, but a user is still able to access them (using, for example,
710 the SQL query area). To limit access, use the MySQL privilege system.
711 <br /><br />
716 More information on regular expressions can be found in the
718 PCRE pattern syntax</a> portion of the PHP reference manual.
719 </dd>
722 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
723 this string will be displayed instead of the hostname in the pull-down
724 menu on the main page. This can be useful if you want to show only
725 certain databases on your system, for example.</dd>
729 </dt>
730 <dd>The name of the database containing the linked-tables infrastructure.
731 <br /><br />
734 section in this document to see the benefits of this infrastructure,
735 and for a quick way of creating this database and the needed tables.
736 <br /><br />
738 If you are the only user of this phpMyAdmin installation, you can
739 use your current database to store those special tables; in this
740 case, just put your current database name in
742 set this parameter to the name of your central database containing
743 the linked-tables infrastructure.</dd>
747 </dt>
749 useful for queries you often run.<br /><br />
751 To allow the usage of this functionality:
753 <li>enter the table name in
755 </ul>
756 </dd>
760 </dt>
762 which field is a key in another table (a foreign key). phpMyAdmin
763 currently uses this to
764 <ul><li>make clickable, when you browse the master table, the data values
765 that point to the foreign table;</li>
767 when browsing the master table, if you move the mouse to a column
768 containing a foreign key (use also the 'table_info' table);<br />
771 <li>in edit/insert mode, display a drop-down list of possible foreign
775 <li>display links on the table properties page, to check referential
776 integrity (display missing foreign keys) for each described key;
777 </li>
781 schema of your database (also uses the table_coords table).</li>
782 </ul>
784 The keys can be numeric or character.<br /><br />
786 To allow the usage of this functionality:
789 infrastructure</li>
790 <li>put the relation table name in
792 <li>now as normal user open phpMyAdmin and for each one of your
793 tables where you want to use this feature, click
795 </li>
796 </ul>
800 future development of the cross-db relations.
801 </dd>
805 </dt>
806 <dd>
807 Since release 2.3.0 you can describe, in a special 'table_info'
808 table, which field is to be displayed as a tool-tip when moving the
809 cursor over the corresponding key.<br />
810 This configuration variable will hold the name of this special
811 table. To allow the usage of this functionality:
813 <li>put the table name in
815 <li>then for each table where you want to use this feature,
817 to choose the field.</li>
818 </ul>
820 </dd>
824 </dt>
827 the relations between your tables. To do this it needs two tables
832 schema output).<br /><br />
836 To allow the usage of this functionality:
839 infrastructure</li>
840 <li>put the correct table names in
843 </ul>
846 </dd>
850 </dt>
852 Since release 2.3.0 you can store comments to describe each column for
854 <br /><br />
856 Starting with release 2.5.0, comments are consequently used on the table
857 property pages and table browse view, showing up as tool-tips above the
858 column name (properties page) or embedded within the header of table in
859 browse view. They can also be shown in a table dump. Please see the
860 relevant configuration directives later on.<br /><br />
862 Also new in release 2.5.0 is a MIME-transformation system which is also
864 Transformations</a> for further information. To use the
865 MIME-transformation system, your column_info table has to have the three
866 new fields 'mimetype', 'transformation', 'transformation_options'.
867 <br /><br />
869 To allow the usage of this functionality:
871 infrastructure</li>
872 <li>put the table name in
876 <pre>
877 ALTER TABLE `pma_column_comments`
878 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
879 ADD `transformation` VARCHAR( 255 ) NOT NULL,
880 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
881 </pre>
884 renamed from<br />
887 </ul>
888 </dd>
892 </dt>
895 all queries you entered manually into the phpMyAdmin interface. If you
896 don't want to use a table-based history, you can use the JavaScript-based
897 history. Using that, all your history items are deleted when closing the
898 window.<br /><br />
900 Using
902 you can specify an amount of history items you want to have on hold. On
903 every login, this list gets cut to the maximum amount.<br /><br />
905 The query history is only available if JavaScript is enabled in your
906 browser.<br /><br />
908 To allow the usage of this functionality:
911 infrastructure</li>
913 </li>
914 </ul>
915 </dd>
918 </dt>
920 column_info table got enhanced with three new fields. If the above variable
922 latest table structure available. If not, it will emit a warning to the
923 superuser.<br /><br />
925 You can disable this checking behavior by setting the variable to false,
926 which should offer a performance increase.<br /><br />
928 Recommended to set to FALSE, when you are sure, your table structure is
929 up to date.</dd>
931 boolean</dt>
932 <dd>Whether to allow root access. This is just simplification of rules below.
933 </dd>
936 </dt>
938 authentication is disabled.<br /><br />
941 all deny rules followed by allow rules. Access is allowed by default. Any
942 client which does not match a Deny command or does match an Allow command
943 will be allowed access to the server. <br /><br />
946 applies all allow rules followed by deny rules. Access is denied by
947 default. Any client which does not match an Allow directive or does
948 match a Deny directive will be denied access to the server.<br /><br />
950 If your rule order is set to 'explicit', the authentication is
951 performed in a similar fashion to rule order 'deny,allow', with the
955 and was available in Apache by specifying allow and deny rules without
956 setting any order.
957 </dd>
959 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
960 </dt>
961 <dd>The general format for the rules is as such:
963 <pre>
965 </pre>
970 well (please note that those containing SERVER_ADDRESS might not be
971 available on all webservers):
972 <pre>
978 </pre>
980 Having an empty rule list is equivalent to either using
986 following work:<br />
988 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
989 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
990 But the following does not work:<br />
993 </dd>
996 <dd>If you have more than one server configured, you can set
998 that server when phpMyAdmin is started, or set it to 0 to be given a
999 list of servers without logging in.<br />
1001 MUST be set to that server.</dd>
1004 <dd>Defines whether to use GZip output buffering for increased
1006 Set to true/false for enabling/disabling. When set to 'auto' (string),
1007 phpMyAdmin tries to enable output buffering and will automatically disable
1008 it if your browser has some problems with buffering. IE6 with a certain patch
1009 is known to cause data corruption when having enabled buffering.</dd>
1012 <dd>Whether persistent connections should be used or not (mysql_connect or
1013 mysql_pconnect).</dd>
1019 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1020 to zero, no time limit is imposed.<br />
1021 This setting is used while importing/exporting dump files but has no
1022 effect when PHP is running in safe mode.</dd>
1025 <dd>Set the number of bytes a script is allowed to allocate. If number set
1026 to zero, no limit is imposed.<br />
1027 This setting is used while importing/exporting dump files but has no
1028 effect when PHP is running in safe mode.<br />
1032 <dd>Mark used tables and make it possible to show databases with locked
1037 generated by phpMyAdmin should be displayed or not.</dd>
1040 <dd>Defines whether normal users (non-administrator) are allowed to
1041 delete their own database or not. If set as FALSE, the link "Drop
1043 mydatabase" will be rejected. Quite practical for
1045 customers.<br />
1046 Please note that this limitation of SQL queries is not as strict as
1047 when using MySQL privileges. This is due to nature of SQL queries
1048 which might be quite complicated. So this choice should be viewed as
1049 help to avoid accidental dropping rather than strict privilege
1050 limitation.</dd>
1054 displayed when you're about to lose data.</dd>
1057 <dd>Define whether the previous login should be recalled or not in cookie
1058 authentication mode.</dd>
1065 means that it will be kept for existing session. This is recommended
1066 for not trusted environments.</dd>
1069 <dd>If enabled (default), logout deletes cookies for all servers,
1070 otherwise only for current one. Setting this to false makes it easy to
1071 forget to logout from other server, when you are using more of
1072 them.</dd>
1078 <dd>Define whether phpMyAdmin will continue executing a multi-query
1079 statement if one of the queries fails. Default is to abort execution.</dd>
1082 <dd>Define whether phpMyAdmin will output the results of each query of a
1083 multi-query statement embedded into the
1088 <dd>If enabled allows you to login to arbitrary servers using cookie auth.
1089 <br /><br />
1092 MySQL servers behind the firewall where your
1094 </dd>
1097 <dd>Defines whether to use a select-based menu and display only the current
1098 tables in the left frame (smaller page). Only in Non-Lightmode you can
1099 use the feature to display nested folders using
1101 </dd>
1104 <dd>In light mode, defines whether to display the names of databases (in the
1105 selector) using a tree, see also
1107 </dd>
1110 <dd>The string used to separate the parts of the database name when showing
1111 them in a tree.</dd>
1114 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1115 This means if you have tables like 'first__second__third' this will be
1117 If set to FALSE or empty, the feature is disabled. NOTE: You should
1118 not use this separator at the beginning or end of a
1119 table name or multiple times after another without any other
1120 characters in between.</dd>
1123 <dd>Defines how many sublevels should be displayed when splitting
1124 up tables by the above separator.</dd>
1127 <dd>Defines whether to display table comment as tool-tip in left frame or
1128 not.</dd>
1131 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1132 comment and the real name. That means that if you have a table called
1133 'user0001' and add the comment 'MyName' on it, you will see the name
1134 'MyName' used consequently in the left frame and the tool-tip shows
1135 the real name of the DB.</dd>
1138 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1140 When setting this to 'nested', the Alias of the Tablename is only used
1141 to split/nest the tables according to the
1143 directive. So only the folder is called like the Alias, the tablename itself
1144 stays the real tablename.</dd>
1147 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1150 <dd>Enter URL where logo in left frame will point to. For use especially
1151 with self made theme which changes this.</dd>
1153 <dd>Defines whether or not to display a server choice at the top of the left frame.
1154 Defaults to FALSE.</dd>
1156 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1157 Defaults to FALSE (drop-down).</dd>
1159 <dd>Defines whether or not to display space usage and statistics about databases
1160 and tables.<br />
1161 Note that statistics requires at least MySQL 3.23.3 and that, at this
1162 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1167 </dt>
1170 not for simple users at the starting main (right) frame. This setting
1171 does not check MySQL commands entered directly.<br /><br />
1173 Please note that to block the usage of phpinfo() in scripts, you
1180 hard coded password value in the configuration file, end users can't
1181 be allowed to change their passwords.</dd>
1184 <dd>Defines whether to suggest a database name on the
1189 content.</dd>
1192 <dd>Defines whether navigation bar buttons and the right panel top menu
1193 contain text or symbols only. A value of TRUE displays icons, FALSE
1194 displays text and 'both' displays both icons and text.</dd>
1197 <dd>Defines whether a user should be displayed a
1201 <dd>Number of rows displayed when browsing a result set. If the result set
1208 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1212 from editing when browsing a table's content. Valid values are:
1217 </ul>
1218 </dd>
1221 <dd>Defines whether or not MySQL functions fields should be displayed in
1222 edit/insert mode.</dd>
1225 <dd>Defines which type of editing controls should be used for CHAR and
1226 VARCHAR fields. Possible values are:
1227 <ul><li>input - this allows to limit size of text to size of field in
1228 MySQL, but has problems with newlines in fields</li>
1229 <li>textarea - no problems with newlines in fields, but also no
1230 length limitations</li>
1231 </ul>
1232 Default is old behavior so input.</dd>
1238 <dd>If there are fewer items than this in the set of foreign keys, then a
1239 drop-down box of foreign keys is presented, in the style described by the
1241 setting.</dd>
1244 <dd>For the foreign key drop-down fields, there are several methods of
1245 display, offering both the key and value data. The contents of the
1246 array should be one or both of the following strings:
1252 </dt>
1253 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1254 creating a dump file</dd>
1257 </dt>
1258 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1259 compressed exports. This doesn't affect smaller dumps and allows users to
1260 create larger dumps that won't otherwise fit in memory due to php
1261 memory limit. Produced files contain more GZip/BZip2 headers, but all
1262 normal programs handle this correctly.</dd>
1266 mainframe.</dd>
1270 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1275 <dd>How many columns will be utilized to display the tables on the
1276 database property view? Default is 1 column. When setting this to a
1277 value larger than 1, the type of the database will be omitted for more
1278 display space.</dd>
1282 <dd>Defines the tab displayed by default on server view. Possible
1289 <dd>Defines the tab displayed by default on database view. Possible
1294 <dd>Defines the tab displayed by default on table view. Possible
1301 points to the MySQL documentation (type depends
1302 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1303 generated.<br />
1305 for more information about MySQL manuals and their types.</dd>
1308 <dd>Type of MySQL documentation:
1314 </ul>
1315 </dd>
1318 <dd>Defines the default language to use, if not browser-defined or
1319 user-defined.<br />
1321 this setting.</dd>
1324 <dd>Defines the default connection collation to use, if not
1325 user-defined.<br />
1330 <dd>Force: always use this language (must be defined in the
1334 <dd>Limit list of available languages to those matching the given regular
1335 expression. For example if you want only Czech and English, you should
1339 <dd>Default character set to use for recoding of MySQL queries. This must be
1340 enabled and it's described by
1342 option.<br />
1343 You can give here any character set which is in
1345 array and this is just default choice, user can select any of them.</dd>
1348 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1349 support (compiled in or module) in PHP to allow MySQL queries recoding
1350 and used language file must have it enabled (by default only these
1351 which are in Unicode, just to avoid losing some characters).<br /><br />
1354 in the Export page, to choose the character set when exporting a file.
1355 </dd>
1358 <dd>You can select here which functions will be used for character set
1359 conversion. Possible values are:
1360 <ul><li>auto - automatically use available one (first is tested
1361 iconv, then recode)</li>
1364 </ul>
1365 Default is auto.</dd>
1368 <dd>Specify some parameters for iconv used in charset conversion. See
1371 used, so that invalid characters will be transliterated.</dd>
1374 <dd>Available character sets for MySQL conversion. You can add your own (any of
1375 supported by recode/iconv) or remove these which you don't use.
1376 Character sets will be shown in same order as here listed, so if you
1377 frequently use some of these move them to the top.</dd>
1381 MIME transformations.<br />
1382 Possible values are:
1383 <ul><li>auto - automatically detect, this is a bit expensive
1385 according to your server real possibilities</li>
1388 </ul>
1389 Default is auto.
1390 </dd>
1394 </dd>
1398 </dt>
1399 <dd>The background colors (HTML) used for both the frames.
1403 <dd>The URI of the background image used for the right frame. It must be
1407 <dd>The color (HTML) used for the pointer in the left frame (does not work
1416 </dd>
1419 <dd>The color (HTML) used for table headers. See
1424 </dd>
1428 </dd>
1430 <dt><span id="cfg_BrowsePointerColor">$cfg[BrowsePointerColor] </span>string [HTML color]<br />
1432 </dt>
1433 <dd>The colors (HTML) uses for the pointer and the marker in browse mode
1435 The former feature highlights the row over which your mouse is passing
1436 and the latter lets you visually mark/unmark rows by clicking on
1437 them.<br />
1450 </dt>
1452 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1454 The Char* values are used for CHAR and VARCHAR editing (if configured
1458 </dt>
1462 </dt>
1463 <dd>Defines if the whole textarea of the query box will be selected on
1464 click.</dd>
1467 </dt>
1468 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1469 editing.</dd>
1472 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1473 Can be turned off by a toggle button on the browse page.</dd>
1477 </dt>
1478 <dd>Defines the place where modify and delete links would be put when
1479 tables contents are displayed (you may have them displayed both at the
1480 left and at the right).
1486 </dt>
1488 Define which one is displayed by default. The first mode displays each
1489 row on a horizontal line, the second rotates the headers by 90
1490 degrees, so you can use descriptive headers even though fields only
1491 contain small values and still print them out. The vertical mode sorts
1492 each row on a vertical lineup.<br /><br />
1494 The HeaderFlipType can be set to 'css' or 'faked'. When using 'css'
1495 the rotation of the header for horizontalflipped is done via CSS. If
1496 set to 'faked' PHP does the transformation for you, but of course this
1497 does not look as good as CSS.</dd>
1501 <dd>When editing/creating new columns in a table all fields normally get
1502 lined up one field a line. (default: 'horizontal'). If you set this to
1503 'vertical' you can have each field lined up vertically beneath each
1504 other. You can save up a lot of place on the horizontal direction and
1505 no longer have to scroll.</dd>
1509 </dt>
1511 display of column comments in Browse or Property display. In browse
1512 mode, the comments are show inside the header. In property mode,
1513 comments are displayed using a CSS-formatted dashed-line below the
1514 name of the field. The comment is shown as a tool-tip for that field.
1515 </dd>
1518 <dd>
1519 The name of the directory where
1521 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1522 are available under a drop-down box when you click the database name,
1524 <br /><br />
1526 If you want different directory for each user, %u will be replaced
1527 with username.<br /><br />
1531 compressed formats is enabled).<br /><br />
1533 This feature is useful when your file is too big to be uploaded via
1535 uploads are disabled in PHP.<br /><br />
1537 Please note that if PHP is running in safe mode, this directory must
1538 be owned by the same user as the owner of the phpMyAdmin scripts.
1539 <br /><br />
1543 alternatives.
1544 </dd>
1547 <dd>
1548 The name of the directory where docSQL files can be uploaded for
1549 import into phpMyAdmin.
1550 <br /><br />
1551 Please note that if PHP is running in safe mode, this directory must
1552 be owned by the same user as the owner of the phpMyAdmin scripts.
1553 </dd>
1556 <dd>
1557 The name of the directory where dumps can be saved.<br /><br />
1559 If you want different directory for each user, %u will be replaced
1560 with username.<br /><br />
1562 Please note that the directory has to be writable for user running
1563 webserver.<br /><br />
1565 Please note that if PHP is running in safe mode, this directory must
1566 be owned by the same user as the owner of the phpMyAdmin scripts.
1567 </dd>
1570 <dd>
1571 The name of the directory where temporary files can be stored.
1572 <br /><br />
1573 This is needed for native MS Excel export, see
1576 </dd>
1579 <dd>
1580 In this array are defined default parameters for export, names of
1581 items are similar to texts seen on export page, so you can easily
1582 identify what they mean.
1583 </dd>
1586 <dd>
1587 In this array are defined default parameters for import, names of
1588 items are similar to texts seen on import page, so you can easily
1589 identify what they mean.
1590 </dd>
1593 <dd>
1594 Repeat the headers every X cells, or 0 to deactivate.
1595 </dd>
1603 </dt>
1604 <dd>
1605 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1606 or icon is always displayed on the left panel. If JavaScript is enabled in
1607 your browser, a click on this opens a distinct query window, which is
1608 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1609 changes to display a query box.<br /><br />
1611 The size of this query window can be customized with
1613 - both integers for the size in pixels. Note that normally, those
1615 theme you are using.<br /><br />
1619 opens the query window and puts the current query
1620 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1621 query in the right panel's query box.
1622 <br /><br />
1623 The usage of the JavaScript query window is recommended if you have a
1624 JavaScript enabled browser. Basic functions are used to exchange quite
1625 a few variables, so most 4th generation browsers should be capable to
1626 use that feature. It currently is only tested with Internet Explorer 6
1627 and Mozilla 1.x.
1628 <br /><br />
1630 to a table, which has to be created by you (see <a
1632 all your queries will be appended to the form, but only as long as
1633 your window is opened they remain saved.
1634 <br /><br />
1635 When using the JavaScript based query window, it will always get
1636 updated when you click on a new table/db to browse and will focus if
1637 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1638 the query window by checking the box "Do not overwrite this query from
1639 outside the window" below the query textarea. Then you can browse
1640 tables/databases in the background without losing the contents of the
1641 textarea, so this is especially useful when composing a query with
1642 tables you first have to look in. The checkbox will get automatically
1643 checked whenever you change the contents of the textarea. Please
1644 uncheck the button whenever you definitely want the query window to
1645 get updated even though you have made alterations.
1646 <br /><br />
1649 <br /><br />
1650 The query window also has a custom tabbed look to group the features.
1652 default tab to be used when opening the query window. It can be set to
1653 either 'sql', 'files', 'history' or 'full'.</dd>
1659 <dd><ul><li>For InnoDB tables, determines for how large tables phpMyAdmin
1661 If the approximate row count as returned by
1664 count will be used.</li>
1665 <li>For VIEWs, since obtaining the exact count could have an
1666 impact on performance, this value is the maximum to be displayed.
1667 </li>
1668 </ul>
1669 </dd>
1673 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1675 page. By clicking on the button 'toggle scratchboard' on the page
1676 where you edit x/y coordinates of those elements you can activate a
1677 scratchboard where all your elements are placed. By clicking on an
1678 element, you can move them around in the pre-defined area and the x/y
1679 coordinates will get updated dynamically. Likewise, when entering a
1680 new position directly into the input field, the new position in the
1681 scratchboard changes after your cursor leaves the input field.<br />
1682 You have to click on the 'OK'-button below the tables to save the new
1683 positions. If you want to place a new element, first add it to the
1684 table of elements and then you can drag the new element around.<br />
1685 By changing the paper size and the orientation you can change the size
1686 of the scratchboard as well. You can do so by just changing the
1687 dropdown field below, and the scratchboard will resize automatically,
1688 without interfering with the current placement of the elements.<br />
1689 If ever an element gets out of range you can either enlarge the paper
1690 size or click on the 'reset' button to place all elements below each
1691 other.<br />
1693 get this control to work. The basic Drag&Drop script functionality
1694 was kindly borrowed from www.youngpup.net and is underlying so
1695 specific license.</dd>
1698 <dd>Sorts database and table names according to natural order (for example,
1699 t1, t2, t10). Currently implemented in the left panel (Light mode)
1700 and in Database view, for the table list.</dd>
1706 <dd>Allows you to specify window's title bar. Following magic string can
1707 be used to get special values:
1708 <dl>
1714 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1723 </dl>
1724 </dd>
1734 </dd>
1737 <dd>If theme manager is active, use this as the path of the subdirectory
1738 containing all the themes.</dd>
1752 </dt>
1753 <dd>Default queries that will be displayed in query boxes when user didn't
1754 specify any. Use %d for database name, %t for table name and %f for a
1755 comma separated list of field names. Note that %t and %f are only
1759 <dd>
1760 The main use of the new <abbr title="structured query language">SQL</abbr> Parser is to pretty-print <abbr title="structured query language">SQL</abbr> queries. By
1761 default we use HTML to format the query, but you can disable this by
1763 </dd>
1766 <span id="cfg_SQP">$cfg[SQP]['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1767 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1768 query inside a bracket is indented. By changing
1771 specifies the units of the indent amount that you specified. This is
1772 used via stylesheets.</dd>
1775 <dd>This array is used to define the colours for each type of element of
1776 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1778 If you specify an empty string for the color of a class, it is ignored
1779 in creating the stylesheet.
1780 You should not alter the class names, only the colour strings.<br />
1801 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1805 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1806 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1807 </ul>
1808 </dd>
1812 <dd>phpMyAdmin now supports use of the <a href="http://developer.mimer.com/validator/index.htm">Mimer <abbr title="structured query language">SQL</abbr> Validator</a> service,
1813 as originally published on
1815 <br />
1816 For help in setting up your system to use the service, see the
1818 </dd>
1822 <dd>The SOAP service allows you to login with <tt>anonymous</tt>
1823 and any password, so we use those by default. Instead, if
1824 you have an account with them, you can put your login details
1825 here, and it will be used in place of the anonymous login.</dd>
1826 </dl>
1827 </dd>
1830 <dd><b>DEVELOPERS ONLY!</b></dd>
1833 <dd><b>DEVELOPERS ONLY!</b><br />
1834 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1835 the code.<br />
1836 For help in setting up your system to this, see the
1840 <dd><b>DEVELOPERS ONLY!</b><br />
1841 Enable profiling support for phpMyAdmin. This will append a chunk of data
1842 to the end of every page displayed in the main window with profiling
1843 statistics for that page.<br />
1844 You may need to increase the maximum execution time for this to
1845 complete successfully.</dd>
1847 <dt id="cfg_DBG_profile_threshold">$cfg[DBG]['profile']['threshold'] float (units in milliseconds)</dt>
1848 <dd><b>DEVELOPERS ONLY!</b><br />
1849 When profiling data is displayed, this variable controls the threshold of
1850 display for any profiling data, based on the average time each time has
1851 taken. If it is over the threshold it is displayed, otherwise it is not
1852 displayed. This takes a value in milliseconds. In most cases you don't need
1853 to edit this.</dd>
1856 <dd>All possible types of a MySQL column. In most cases you don't need to
1857 edit this.</dd>
1860 <dd>Possible attributes for fields. In most cases you don't need to edit
1861 this.</dd>
1864 <dd>A list of functions MySQL supports. In most cases you don't need to
1865 edit this.</dd>
1868 <dd>Mapping of column types to meta types used for preferring displayed
1869 functions. In most cases you don't need to edit this.</dd>
1872 <dd>Functions preferred for column meta types as defined in
1873 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
1874 to edit this.</dd>
1877 <dd>Functions selected by default when inserting/changing row, Functions
1878 are defined for meta types from
1880 <code>first_timestamp</code>, which is used for first timestamp column
1881 in table.</dd>
1884 <dd>Operators available for search operations on numeric and date fields.
1885 </dd>
1888 <dd>Operators available for search operations on character fields.
1889 Note that we put <code>LIKE</code> by default instead of
1890 <code>LIKE %...%</code>, to avoid unintended performance problems
1891 in case of huge tables.</dd>
1894 <dd>Operators available for search operations on enum fields.</dd>
1897 <dd>Additional operators available for search operations when the
1898 field can be null.</dd>
1900 </dl>
1902 <!-- TRANSFORMATIONS -->
1908 </ol>
1912 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
1914 section</a> on how to do so.</p>
1916 <p> You can apply different transformations to the contents of each field. The
1917 transformation will take the content of each field and transform it with
1918 certain rules defined in the selected transformation.</p>
1920 <p> Say you have a field 'filename' which contains a filename. Normally you would
1921 see in phpMyAdmin only this filename. Using transformations you can transform
1922 that filename into a HTML link, so you can click inside of the phpMyAdmin
1923 structure on the field's link and will see the file displayed in a new browser
1924 window. Using transformation options you can also specify strings to
1925 append/prepend to a string or the format you want the output stored in.</p>
1927 <p> For a general overview of all available transformations and their options,
1928 you can consult your
1929 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
1930 installation.</p>
1932 <p> For a tutorial on how to effectively use transformations, see our
1934 the official phpMyAdmin homepage.</p>
1938 <p> Go to your <i>tbl_properties_structure.php</i> page (i.e. reached through
1939 clicking on the 'Structure' link for a table). There click on
1940 "Change" (or change icon) and there you will see three new fields at
1941 the end of the line. They are called 'MIME-type', 'Browser transformation' and
1942 'Transformation options'.</p>
1944 <ul><li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
1945 empty or to use 'auto' [this feature is not yet available]. Please note that
1946 transformations are inactive as long as no MIME-type is selected.</li>
1948 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
1949 hopefully growing amount of pre-defined transformations. See below for information on
1950 how to build your own transformation.<br />
1952 There are global transformations and mimetype-bound transformations. Global transformations
1953 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
1954 Mimetype-bound transformations usually only operate on a certain mimetype. There are
1955 transformations which operate on the main mimetype (like 'image'), which will most likely
1956 take the subtype into regard, and those who only operate on a
1957 specific subtype (like 'image/jpeg').<br />
1959 You can use transformations on mimetypes for which the function was not defined for. There
1960 is no security check for you selected the right transformation, so take care of what the
1961 output will be like.</li>
1963 <li>The field 'Transformation options' is a free-type textfield. You have to enter
1964 transform-function specific options here. Usually the transforms can operate with default
1965 options, but it is generally a good idea to look up the overview to see which options are
1966 necessary.<br />
1968 Much like the ENUM/SET-Fields, you have to split up several options using the format
1969 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
1970 parsed as an array, leaving the first value the first element in the array, and so
1971 forth.<br />
1973 If you want to specify a MIME character set you can define it in the transformation_options.
1974 You have to put that outside of the pre-defined options of the specific mime-transform,
1976 for which you can specify 2 options and you want to append a character set, enter "'first
1977 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
1979 </ul>
1983 <p> All mimetypes and their transformations are defined through single files in
1984 the directory 'libraries/transformations/'.</p>
1986 <p> They are stored in files to ease up customization and easy adding of new
1987 transformations.</p>
1989 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
1990 always work. It makes no sense to apply a transformation to a mimetype, the
1991 transform-function doesn't know to handle.</p>
1993 <p> One can, however, use empty mime-types and global transformations which should work
1994 for many mimetypes. You can also use transforms on a different mimetype they where built
1995 for, but pay attention to option usage as well as what the transformation does to your
1996 field.</p>
1998 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
1999 any other transform function and provides some basic functions.</p>
2001 <p> There are 5 possible file names:</p>
2003 <ol><li>A mimetype+subtype transform:<br /><br />
2005 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2007 Please not that mimetype and subtype are separated via '_', which shall
2008 not be contained in their names. The transform function/filename may
2009 contain only characters which cause no problems in the file system as
2010 well as the PHP function naming convention.<br /><br />
2012 The transform function will the be called
2013 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2015 <b>Example:</b><br /><br />
2017 <tt>text_html__formatted.inc.php</tt><br />
2018 <tt>PMA_transform_text_html__formatted()</tt></li>
2020 <li>A mimetype (w/o subtype) transform:<br /><br />
2022 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2024 Please note that there are no single '_' characters.
2025 The transform function/filename may contain only characters which cause
2026 no problems in the file system as well as the PHP function naming
2027 convention.<br /><br />
2029 The transform function will the be called
2030 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2032 <b>Example:</b><br /><br />
2034 <tt>text__formatted.inc.php</tt><br />
2035 <tt>PMA_transform_text__formatted()</tt></li>
2037 <li>A mimetype+subtype without specific transform function<br /><br />
2039 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2041 Please note that there are no '__' characters in the filename. Do not
2042 use special characters in the filename causing problems with the file
2043 system.<br /><br />
2045 No transformation function is defined in the file itself.<br /><br />
2047 <b>Example:</b><br /><br />
2049 <tt>text_plain.inc.php</tt><br />
2050 (No function)</li>
2052 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2054 <tt>[mimetype].inc.php</tt><br /><br />
2056 Please note that there are no '_' characters in the filename. Do not use
2057 special characters in the filename causing problems with the file system.
2058 <br /><br />
2060 No transformation function is defined in the file itself.<br /><br />
2062 <b>Example:</b><br /><br />
2064 <tt>text.inc.php</tt><br />
2065 (No function)</li>
2067 <li>A global transform function with no specific mimetype<br /><br />
2069 <tt>global__[transform].inc.php</tt><br /><br />
2071 The transform function will the be called
2072 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2074 <b>Example:</b><br /><br />
2076 <tt>global__formatted</tt><br />
2077 <tt>PMA_transform_global__formatted()</tt></li>
2078 </ol>
2080 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2081 transform function.</p>
2083 <p> All filenames containing no '__' in themselves are not shown as valid transform
2084 functions in the dropdown.</p>
2086 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2087 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2088 without a transform function. Also note the introduction of a function description in
2089 the language files. For each function a $strTransformation_[filename without .inc.php]
2090 has to exist.</p>
2092 <p> You can use the template generator to generate new functions and entries in the
2093 language file.</p>
2095 <p> To create a new transform function please see
2096 <tt>libraries/transformations/template_generator.sh</tt>.
2097 To create a new, empty mimetype please see
2098 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2100 <p> A transform function always gets passed three variables:</p>
2102 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2103 you want to transform.</li>
2104 <li><b>$options</b> - Contains any user-passed options to a transform function
2105 as an array.</li>
2106 <li><b>$meta</b> - Contains an object with field information to your column.
2107 The data is drawn from the output of the
2109 function. This means, all object properties described on the
2111 available in this variable and can be used to transform a field accordingly
2112 to unsigned/zerofill/not_null/... properties.<br />
2113 The $meta->mimetype variable contains the original MIME-type of the
2114 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2115 </ol>
2117 <!-- FAQ -->
2124 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2128 </ol>
2130 <p> Please have a look at our
2132 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2133 features and or interface.</p>
2139 action is required or phpMyAdmin sends a blank page or a page full of
2140 cryptic characters to my browser, what can I do?</a></h4>
2142 <p> There are some known PHP bugs with output buffering and compression.<br />
2144 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2145 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2146 configuration file.<br />
2147 Furthermore, we know about such problems connected to the release
2148 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2149 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2154 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2155 See also the
2157 entry about PHP bugs with output buffering.<br />
2158 If your server keeps crashing, please ask for help in the various Apache
2159 support groups.</p>
2163 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2164 script: I'm always displayed the login screen.</a></h4>
2166 <p> This is a known PHP bug (see this
2168 official PHP bug database. It means there is and won't be any phpMyAdmin
2169 fix against it because there is no way to code a fix.</p>
2175 application misbehaved by not returning a complete set of
2177 </h4>
2179 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2180 Have a look at the last message in this
2182 official PHP bug database.</p>
2187 and/or many error messages with the
2189 mode.</a></h4>
2191 <p> This is a known problem with the PHP
2193 filter: it's not so stable. Please use instead the cookie authentication mode.
2194 </p>
2199 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2200 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2201 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2202 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2203 <i>left.php</i> and <i>libraries/common.lib.php</i>.</p>
2208 work.</a></h4>
2210 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2211 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2212 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2213 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2214 We faced PHP crashes when trying to download a dump with MS Internet
2215 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2216 this case you should switch to the release version of PHP 4.2.0.</p>
2220 an error about safe mode being in effect.</a></h4>
2222 <p> Your uploaded file is saved by PHP in the "upload dir", as
2223 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2224 the system default is <i>/tmp</i>).<br />
2225 We recommend the following setup for Apache servers running in safe mode,
2226 to enable uploads of files while being reasonably secure:</p>
2228 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2229 <li>give ownership to the Apache server's user.group:
2230 <tt>chown apache.apache /tmp/php</tt></li>
2231 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2232 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2233 <li>restart Apache</li>
2234 </ul>
2238 general file uploads don't work on my system and uploaded files have a
2239 <tt>Content-Type:</tt> header in the first line.</a></h4>
2241 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2242 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2243 So the problem is that this package has a serious bug that was corrected
2244 ages ago in PHP (2001-01-28: see
2246 for more details). The problem is that the bugged package is still
2247 available though it was corrected (see
2249 for more details).<br />
2250 So please download
2251 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2252 and the problem should go away.<br />
2253 And that fixes the \r\n problem with file uploads!</p>
2257 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2258 I'm using the Apache server.</a></h4>
2260 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2261 your <i>httpd.conf</i>:</p>
2265 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2269 uploading a file from the query box.</a></h4>
2271 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2272 restrictions. Assuming that the restriction allows you to open files in the
2273 current directory ('.'), all you have to do is create a 'tmp' directory
2274 under the phpMyAdmin install directory, with permissions 777 and the same
2275 owner as the owner of your phpMyAdmin directory. The uploaded files will
2276 be moved there, and after execution of your
2282 <p> The MySQL manual explains how to
2284 reset the permissions</a>.</p>
2289 execute a bookmark.</a></h4>
2291 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2292 cannot access the uploaded query.</p>
2297 submit a query from the convenient text area.</a></h4>
2299 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2300 and try to increase it.</p>
2304 </h4>
2306 <p> In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2307 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2308 names to align with current standards.</p>
2313 </h4>
2315 <p> Starting with version 2.7.0, the import engine has been re–written and these
2316 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2317 to take advantage of the new import features.</p>
2319 <p> The first things to check (or ask your host provider to check) are the
2320 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2321 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2322 All of these three settings limit the maximum size of data that can be
2323 submitted and handled by PHP. One user also said that post_max_size
2324 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2326 There exist several workarounds if your upload is too big or your
2327 hosting provider is unwilling to change the settings:</p>
2330 feature. This allows one to
2331 upload a file to the server via scp, ftp, or your favorite file transfer
2332 method. PhpMyAdmin is then able to import the files from the temporary
2334 section</a> of this document.</li>
2336 BigDump</a>) to split the files before uploading. We cannot support this
2337 or any third party applications, but are aware of users having success
2338 with it.</li>
2339 <li>If you have shell (command line) access, use MySQL to import the files
2340 directly. You can do this by issuing the "source" command from
2341 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2342 </ul>
2346 support?</a></h4>
2348 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2349 fully supported. Please note that the older your MySQL version is, the more
2350 limitations you will have to face.<br />
2351 phpMyAdmin may connect to your MySQL server using php's classic
2354 is available in php 5.0.<br />
2355 Either way, the developers of both extensions recommend to use the classic
2356 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2357 When compiling php, we strongly recommend that you manually link the MySQL
2358 extension of your choice to a MySQL client library of at least the same
2359 minor version since the one that is bundled with some php distributions is
2362 If your webserver is running on a windows system, you might want to try
2363 MySQL's
2365 instead of the MySQL / MySQLi extensions that are bundled with the official
2366 php Win32 builds.
2367 <br />
2368 MySQL 5.1 is not yet supported.</p>
2372 message, "Client does not support authentication protocol requested
2373 by server; consider upgrading MySQL client"</a></h5>
2375 <p> You tried to access MySQL with an old MySQL client library. The version of
2376 your MySQL client library can be checked in your phpinfo() output.
2377 In general, it should have at least the same minor version as your server
2381 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2382 changed the authentication hash and your PHP is trying to use the old method.
2384 with the proper client library to match your MySQL installation. Your
2385 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2386 More information (and several workarounds) are located in the
2388 </p>
2392 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2393 capital letter in its name it is changed to lowercase as it should. But
2394 if I try to DROP this table MySQL is unable to find the corresponding
2395 file.</a></h4>
2397 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2398 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2399 directive.</p>
2403 script seems not to know the font face I'm using!</a></h4>
2405 <p> The "FPDF" library we're using for this feature requires some
2406 special files to use font faces.<br />
2408 these files.</p>
2412 password encryption in cookie auth doesn't work.</a></h4>
2414 <p> If your cluster consist of different architectures, PHP code used for
2415 encryption/decryption won't work correct. This is caused by use of
2416 pack/unpack functions in code. Only solution is to use mcrypt extension
2417 which works fine in this case.</p>
2421 check PHP Configuration".</a></h4>
2423 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2424 "MySQL extension". This extension may be part of the PHP
2425 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2426 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2427 to load the extension but failed.<br /><br />
2429 Usually, the problem is solved by installing a software package called
2430 "PHP-MySQL" or something similar.</p>
2435 and I cannot login using cookie auth.</a></h4>
2437 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2441 so I cannot upload.</a></h4>
2443 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2444 parameter is not set to "on".</p>
2448 a new table the table and field names are changed to lowercase!</a></h4>
2450 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2451 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2452 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2453 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2454 directory and add the following line to the group [mysqld]:</p>
2456 <pre>set-variable = lower_case_table_names=0</pre>
2458 <p> Next, save the file and restart the MySQL service. You can always check the
2459 value of this directive using the query</p>
2461 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2465 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2468 </p>
2472 and I get problems, such as undefined variables when I run a
2475 <p> A tip from Jose Fandos: put a comment on the following two lines
2476 in httpd.conf, like this:</p>
2478 <pre>
2479 # mod_gzip_item_include file \.php$
2481 </pre>
2483 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2484 PHP scripts. Of course you have to restart Apache.</p>
2489 I get the error "No input file specified" when trying to
2490 run phpMyAdmin.</a></h4>
2492 <p> This is a permission problem. Right-click on the phpmyadmin folder
2493 and choose properties. Under the tab Security, click on "Add"
2494 and select the user "IUSR_machine" from the list. Now set his
2495 permissions and it should work.</p>
2499 db_details_structure.php with plenty of tables).</a></h4>
2502 GZIP output buffering is enabled. If you turn off it (by
2504 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2505 PHP 5.0.0.</p>
2509 message 'Errorcode: 13'. What does this mean?</a></h4>
2511 <p> This can happen due to a MySQL bug when having database / table names with
2512 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2513 To fix this, turn off this directive, convert all database and table names
2514 to lower case and turn it on again. Alternatively, there's a bug-fix
2515 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2519 and the fields are duplicated.</a></h4>
2521 <p> It is possible to configure Apache in such a way that PHP has problems
2522 interpreting .php files.</p>
2524 <p> The problems occur when two different (and conflicting) set of directives
2525 are used:</p>
2527 <pre>
2528 SetOutputFilter PHP
2529 SetInputFilter PHP
2530 </pre>
2532 <p> and</p>
2534 <pre>AddType application/x-httpd-php .php</pre>
2536 <p> In the case we saw, one set of directives was in
2537 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2538 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2539 The recommended way is with <tt>AddType</tt>, so just comment out
2540 the first set of lines and restart Apache:</p>
2542 <pre>
2543 #SetOutputFilter PHP
2544 #SetInputFilter PHP
2545 </pre>
2550 <p> This problem is known to happen when the server is running Turck MMCache
2551 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2556 <p> Yes.<br />
2557 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2558 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2559 <tt>error_reporting</tt> settings.
2560 </p>
2563 <a href="#faq1_32">Can I use <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication with <abbr title="Internet Information Services">IIS</abbr>?</a></h4>
2565 <p> Yes. This procedure was tested with phpMyAdmin 2.6.1, PHP 4.3.9 in <abbr title="Internet Server Application Programming Interface">ISAPI</abbr>
2568 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2569 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2570 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2571 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2572 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2573 enabled.) Click <tt>OK</tt>.</li>
2574 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2575 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2576 </ol>
2580 PHP 5.0.4 on 64-bit systems?</a></h4>
2582 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2583 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2589 http://server/phpMyAdmin/index.php?db=database&table=table&target=script.
2590 Table and script parts are optional. If you want
2591 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2592 some configuration. Following lines apply only for <a
2594 that you have enabled some features within global configuration. You need
2595 <code>Options FollowSymLinks</code> and <code>AllowOverride
2596 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2597 you need mod_rewrite to be enabled. Then you just need to create following
2598 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2599 (don't forget to change directory name inside of it):</p>
2601 <pre>
2602 RewriteEngine On
2603 RewriteBase /path_to_phpMyAdmin
2604 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2605 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2606 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2607 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2608 </pre>
2611 <a href="#faq1_35">Can I use <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication with Apache <abbr title="Common Gateway Interface">CGI</abbr>?</a></h4>
2613 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2614 following rewrite rule:</p>
2616 <pre>
2617 RewriteEngine On
2618 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2619 </pre>
2623 </h4>
2624 <p>
2625 There can be many explanations to this and a look at your server's
2626 error log file might give a clue.
2627 </p>
2634 headers already sent by ..." is displayed, what's the problem?</a></h4>
2636 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2637 (I.E. no blank lines, no spaces, no characters...) neither before the
2638 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2639 tag at the end.</p>
2644 <p> Either there is an error with your PHP setup or your username/password is
2645 wrong. Try to make a small script which uses mysql_connect and see if it
2646 works. If it doesn't, it may be you haven't even compiled MySQL support
2647 into PHP.</p>
2651 connect to local MySQL server through socket '/tmp/mysql.sock'
2652 (111) ..." is displayed. What can I do?</a></h4>
2654 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2656 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2657 In your <i>php.ini</i> you will find a line</p>
2659 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2661 <p> change it to</p>
2663 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2665 <p> Then restart apache and it will work.</p>
2667 <p> Here is a fix suggested by Brad Ummer:</p>
2669 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2670 To do this, telnet to your server and go to the MySQL bin directory. In
2671 this directory there should be a file named <i>mysqladmin</i>. Type
2672 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2673 info about your MySQL server, including the socket
2674 (<i>/tmp/mysql.sock</i>, for example).</li>
2675 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2676 phpMyAdmin, you need to complete the socket information in the
2677 <i>config.inc.php</i>.<br />
2678 For example:
2680 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2681 <br /><br />
2683 Please also make sure that the permissions of this file allow to be readable
2684 by your webserver (i.e. '0755').</li>
2685 </ul>
2687 <p> Have also a look at the
2689 corresponding section of the MySQL documentation</a>.</p>
2693 what can I do?</a></h4>
2696 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2697 sometime.<br />
2698 Also have a look at your PHP version number: if it contains "4.0b..."
2699 it means you're running a beta version of PHP. That's not a so good idea,
2700 please upgrade to a plain revision.</p>
2704 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2705 cookie authentication, I'm asked to login again. What's wrong?</a></h4>
2707 <p> Check the value you set for the
2709 directive in the phpMyAdmin configuration file.</p>
2713 password: YES)"-error when trying to access a MySQL-Server on a
2714 host which is port-forwarded for my localhost.</a></h4>
2716 <p> When you are using a port on your localhost, which you redirect via
2717 port-forwarding to another host, MySQL is not resolving the localhost
2718 as expected.<br />
2719 Erik Wasser explains: The solution is: if your host is "localhost"
2720 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2721 connection for speeding up things. And that doesn't work in this configuration
2722 with port forwarding.<br />
2728 <p> Themes are configured with
2732 <br />
2734 should not delete the directory "original" or its underlying
2735 structure, because this is the system theme used by phpMyAdmin.
2736 "original" contains all images and styles, for backwards
2737 compatibility and for all themes that would not include images or css-files.
2738 <br /><br />
2741 is enabled, you can select your favorite theme on the main page. Your
2742 selected theme will be stored in a cookie.<br /><br /></p>
2744 <p> To create a theme:</p>
2746 <ul><li>make a new subdirectory (for example "your_theme_name") under
2748 (by default <tt>themes</tt>)</li>
2749 <li>copy the files and directories from "original" to
2750 "your_theme_name"</li>
2751 <li>edit the css-files in "your_theme_name/css"</li>
2752 <li>put your new images in "your_theme_name/img"</li>
2753 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2754 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2755 contain your chosen theme name, that will be visible in user interface</li>
2756 <li>make a new screenshot of your theme and save it under
2757 "your_theme_name/screen.png"</li>
2758 </ul>
2760 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2761 theme verbose name, theme generation and theme version. These versions and
2762 generations are enumerated from 1 and do not have any direct dependence on
2763 phpMyAdmin version. Themes within same generation should be backwards
2764 compatible - theme with version 2 should work in phpMyAdmin requiring
2765 version 1. Themes with different generation are incompatible.</p>
2767 <p> If you do not want to use your own symbols and buttons, remove the
2768 directory "img" in "your_theme_name". phpMyAdmin will
2769 use the default icons and buttons (from the system-theme "original").
2770 </p>
2774 what can I do?</a></h4>
2776 <p> Here are a few points to check:</p>
2778 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2780 directive empty. See also
2782 </li>
2783 <li>Maybe you have a broken PHP installation or you need to upgrade
2784 your Zend Optimizer. See
2786 http://bugs.php.net/bug.php?id=31134</a>.
2787 </li>
2788 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2789 set to the default (200) or another low value, you could get this
2790 error if your table has a high number of columns. Adjust this setting
2791 accordingly. (Thanks to Klaus Dorninger for the hint).
2792 </li>
2793 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2794 of ";" will cause this error. Replace it with "&;".
2795 </li>
2796 </ul>
2803 who logged out can not relogin in with the same nick.</a></h4>
2805 <p> This is related to the authentication mechanism (protocol) used by
2806 phpMyAdmin. To bypass this problem: just close all the opened
2807 browser windows and then go back to phpMyAdmin. You should be able to
2808 log in again.</p>
2812 limit error or a time limit error.</a></h4>
2814 <p> Compressed dumps are built in memory and because of this are limited to
2815 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
2816 using
2818 (enabled by default). Zip exports can not be handled this way, so if you need
2819 Zip files for larger dump, you have to use another way.</p>
2823 or alter a table.</a></h4>
2825 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
2829 bundled with the MySQL server distribution.</a></h4>
2831 <p> The problem is that mysqldump creates invalid comments like this:</p>
2833 <pre>
2834 -- MySQL dump 8.22
2835 --
2836 -- Host: localhost Database: database
2837 ---------------------------------------------------------
2838 -- Server version 3.23.54
2839 </pre>
2841 <p> The invalid part of the code is the horizontal line made of dashes that
2842 appears once in every dump created with mysqldump. If you want to run your
2843 dump you have to turn it into valid MySQL. This means, you have to add a
2844 whitespace after the first two dashes of the line or add a # before it:
2845 <br />
2846 <code>
2847 -- -------------------------------------------------------<br />
2848 </code>
2849 or<br />
2850 <code>
2851 #---------------------------------------------------------
2852 </code>
2853 </p>
2860 <p> Please note that you should not use the separating string multiple times
2861 without any characters between them, or at the beginning/end of your table
2862 name. If you have to, think about using another TableSeparator or disabling
2863 that feature</p>
2868 <p> In Relation view, being able to choose a table in another database,
2869 or having more than one index field in the foreign key.<br /><br/>
2870 In Query-by-example (Query), automatic generation of the query
2871 LEFT JOIN from the foreign table.<br /><br/>
2873 </p>
2877 I get series of errors like "Warning: unable to parse url". How
2878 can this be fixed?</a></h4>
2879 <p>
2880 Your table neither have a primary key nor an unique one, so we must use a
2881 long expression to identify this row. This causes problems to parse_url
2882 function. The workaround is to create a primary or unique key.
2883 <br />
2884 </p>
2888 a MIME-Transformation onto!</a></h4>
2890 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
2891 nested forms can be put inside the table where phpMyAdmin displays the results.
2892 You can, however, use any form inside of a table if keep the parent
2893 form-container with the target to tbl_row_delete.php and just put your own
2894 input-elements inside. If you use a custom submit input field, the form will
2895 submit itself to the displaying page again, where you can validate the
2896 $HTTP_POST_VARS in a transformation.
2898 For a tutorial on how to effectively use transformations, see our
2900 on the official phpMyAdmin-homepage.</p>
2904 MySQL server</a></h4>
2906 <p> When MySQL is running in ANSI-compatibility mode, there are some major
2909 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
2910 the quote-character (") is interpreted as an identifier quote character and
2911 not as a string quote character, which makes many internal phpMyAdmin
2913 statements. There is no workaround to this behaviour. News to this item will
2914 be posted in Bug report
2915 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
2916 </p>
2920 more that one column with the same value
2921 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
2922 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
2924 <p> Please make sure that your table has a primary key, so that phpMyAdmin
2925 can use it for the Edit and Delete links.</p>
2930 <p> phpMyAdmin uses a quick method to get the row count, and this method
2931 only returns an approximate count in the case of InnoDB tables. See
2933 a way to modify those results, but
2934 this could have a serious impact on performance.</p>
2939 <p> The number of records in queries containing COUNT and GROUP BY is
2940 not correctly calculated. Also, sorting results of a query like
2945 containing an hyphen.
2946 </a></h4>
2947 <p>
2948 The tests I have made with current MySQL 4.1.11 API shows that the
2949 API does not accept this syntax for the USE command. Enclosing the
2950 db name with backquotes works. For further confusion, no backquotes
2951 are needed with command-line mysql.
2952 </p>
2954 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
2957 <a href="#faq4_1">I'm an <abbr title="Internet service provider">ISP</abbr>. Can I setup one central copy of phpMyAdmin or do I
2958 need to install it for each customer.
2959 </a></h4>
2960 <p>
2961 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
2962 your users. The development of this feature was kindly sponsored by
2963 NetCologne GmbH.
2964 This requires a properly setup MySQL user management and phpMyAdmin
2965 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
2967 </p>
2971 access.
2972 </a></h4>
2973 <p>
2974 This depends on your system.<br />
2975 If you're running a server which cannot be accessed by other people, it's
2976 sufficient to use the directory protection bundled with your webserver
2978 If other people have telnet access to your server, you should use
2979 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
2980 <br /><br />
2981 Suggestions:
2982 </p>
2983 <ul>
2984 <li>
2986 </li>
2987 <li>
2988 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
2989 is a user whose password is only known to you, and apache is the
2990 group under which Apache runs.
2991 </li>
2992 <li>
2993 You should use PHP safe mode, to protect from other users that try
2995 </li>
2996 </ul>
3001 </a></h4>
3002 <p>
3007 </p>
3010 <a href="#faq4_4">phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3011 authentication.
3012 </a></h4>
3016 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3017 and/or
3019 are wrong.</li>
3021 <li>You have already setup a security mechanism for the
3022 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3023 phpMyAdmin's authentication, so remove it.</li>
3024 </ul>
3031 and put the privileges you want. For example,
3033 would let a user create/manage his/her database(s).</p>
3038 <p> If you have existing rules from an old .htaccess file, you can take them
3041 be a major benefit here if your installation is suited to using it. Then
3042 you can just add those updated lines into the
3046 <p> If you want a pre-made sample, you can try this fragment. It stops the
3047 'root' user from logging in from any networks other than the private
3050 <pre>
3051 //block root from logging in except from the private networks
3052 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3053 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3054 'deny root from all',
3055 'allow root from localhost',
3059 );
3060 </pre>
3065 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3066 different than the one set in your
3068 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3069 while a domain name is defined in the config file.</p>
3075 when trying to create a table with more than 14 fields.
3076 </a></h4>
3077 <p>
3078 We could reproduce this problem only under Win98/98SE. Testing under
3079 WinNT4 or Win2K, we could easily create more than 60 fields.
3080 <br />
3081 A workaround is to create a smaller number of fields, then come back to
3082 your table properties and add the other fields.
3083 </p>
3087 <p>
3088 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3089 with each script/website that use forms.<br />
3090 Upgrade or downgrade your Xitami server.
3091 </p>
3095 <p>
3096 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3097 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3098 don't seem to work.<br />
3100 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3101 the user's temporary directory, so they must be moved before closing
3102 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3105 </p>
3109 Explorer never stores the cookies.
3110 </a></h4>
3111 <p>
3112 MS Internet Explorer seems to be really buggy about cookies, at least till
3114 in this area!
3115 <br />
3116 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3117 work!
3118 </p>
3122 rows.
3123 </a></h4>
3124 <p>
3126 </p>
3130 when trying to modify a row in a table with many fields, or with a text field
3131 </a></h4>
3132 <p>
3133 Your table neither have a primary key nor an unique one, so we must use a
3134 long <abbr title="Uniform Resource Locator">URL</abbr> to identify this row. There is a limit on the length of the <abbr title="Uniform Resource Locator">URL</abbr> in
3135 those browsers, and this not happen in Netscape, for example. The
3136 workaround is to create a primary or unique key, or use another browser.
3137 <br />
3138 </p>
3142 page.
3143 </a></h4>
3144 <p>
3145 Some browsers support right-clicking into the frame you want to refresh,
3146 just do this in the right frame.<br />
3147 </p>
3151 query box.
3152 </a></h4>
3153 <p>
3154 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3155 Mozilla versions.<br />
3156 </p>
3160 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3161 </a></h4>
3162 <p>
3163 This is a Mozilla bug (see bug #26882 at
3165 </p>
3170 </a></h4>
3171 <p>
3172 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3173 data in octet-stream mode. Since we can't detect the specific Netscape
3174 version, we cannot workaround this bug.
3175 </p>
3179 wrong.</a></h4>
3181 <p> Please ensure that you have set your browser's character set to the one of the
3182 language file you have selected on phpMyAdmin's start page.
3183 Alternatively, you can try the auto detection mode that is supported by the
3184 recent versions of the most browsers.</p>
3187 <a href="#faq5_12"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X: Safari browser changes special characters to
3190 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3191 Netscape and Mozilla do not have this problem.</p>
3194 <a href="#faq5_13">With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3195 I cannot manage two servers: I login to the first one, then the other one,
3196 but if I switch back to the first, I have to login on each operation.</a></h4>
3202 but nothing happens after that, only a blank screen.</a></h4>
3205 bug in Opera6, because it is not able to interpret frameset definitions
3206 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3207 Opera7 at least.</p>
3216 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3221 address and you are starting
3223 containing a domain name, or the reverse situation.</li>
3224 <li>Security settings in IE and/or Microsoft Security Center are
3225 too high, thus blocking scripts execution.</li>
3226 <li>The Windows Firewall is blocking Apache and MySQL. You must
3230 </ul>
3234 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3235 installed in their Firefox is causing the problem.</p>
3242 </a></h4>
3243 <p>
3244 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3245 specifying a wrong field-type.<br />
3246 Common errors include:
3247 </p>
3248 <ul>
3251 </ul>
3252 <p>
3253 Also, look at the syntax chapter in the MySQL manual to confirm that your
3254 syntax is correct.
3255 </p>
3259 phpMyAdmin generates only one index with those 2 fields.
3260 </a></h4>
3261 <p>
3263 index. If you want two indexes, create the first one when creating the
3264 table, save, then display the table properties and click the Index link to
3265 create the other index.
3266 </p>
3270 <p>
3271 Since version 2.2.3, you have a checkbox for each field that can be null.
3273 field's value. Since version 2.5.5, you have to use the checkbox to get
3275 a literal NULL in the field, and not a NULL value (this works in PHP4).
3276 </p>
3281 <p> Click on a database or table name in the left frame, the properties will be
3283 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3284 statements that can be used to recreate your database/table.
3285 <br /><br />
3287 transmit the resulting dump to your station. Depending on your PHP
3288 configuration, you will see options to compress the dump. See also the
3290 configuration variable.<br /><br />
3293 this document.</p>
3298 </a></h4>
3300 <p> Click on a database name in the left frame, the properties will be
3302 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3304 the path to your dump filename, or use the Browse button. Then click Go.
3305 <br /><br />
3307 that you upgrade to take advantage of the new features.
3308 <br /><br />
3310 in this document.
3311 </p>
3316 <p> Here is an example with the tables persons, towns and countries, all
3318 table, create it as explained in the configuration section. Then create the
3319 example tables:</p>
3321 <pre>
3322 CREATE TABLE REL_countries (
3323 country_code char(1) NOT NULL default '',
3324 description varchar(10) NOT NULL default '',
3325 PRIMARY KEY (country_code)
3326 ) TYPE=MyISAM;
3328 INSERT INTO REL_countries VALUES ('C', 'Canada');
3330 CREATE TABLE REL_persons (
3331 id tinyint(4) NOT NULL auto_increment,
3332 person_name varchar(32) NOT NULL default '',
3334 country_code char(1) NOT NULL default '',
3335 PRIMARY KEY (id)
3336 ) TYPE=MyISAM;
3338 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3339 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3341 CREATE TABLE REL_towns (
3343 description varchar(30) NOT NULL default '',
3344 PRIMARY KEY (town_code)
3345 ) TYPE=MyISAM;
3347 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3348 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3349 </pre>
3355 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3359 </ul>
3367 <li>In the fields row, choose persons.person_name and click the
3369 <li>Do the same for towns.description and countries.descriptions in the
3372 the correct joins have been generated</li>
3374 </ul>
3378 <p>
3379 Starting from the previous example, create the pma_table_info as explained
3380 in the configuration section, then browse your persons table,
3381 and move the mouse over a town code or country code.
3382 <br /><br />
3383 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3384 enables: drop-down list of possible values.
3385 </p>
3388 <a href="#faqpdf">How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3389 <p>
3392 <br /><br />
3393 Then you need to think about your schema layout. Which tables will go on
3394 which pages?
3395 </p>
3396 <ul>
3402 page and click Go. If you like, you
3404 linked tables onto the new page.</li>
3405 <li>Select the name of the new page (making sure the Edit radio button
3406 is selected) and click Go.</li>
3408 Coordinates are relative; your diagram will
3409 be automatically scaled to fit the page. When initially placing tables
3410 on the page, just pick any coordinates -- say, 50x50. After clicking
3412 position the element correctly.</li>
3414 first be sure to click the Save
3415 button beneath the list of tables and coordinates, to save any changes
3416 you made there. Then scroll all the way down, select the
3418 you want, and click Go.</li>
3419 <li>Internet Explorer for Windows may suggest an incorrect filename when
3424 browsers on Windows, do not have this problem.</li>
3425 </ul>
3429 columns!</a></h4>
3431 <p> No, it's MySQL that is doing
3437 underscores in the database name?</a></h4>
3439 <p> If you do not put a backslash before the underscore, this is a wildcard
3442 john2db ...<br /><br />
3444 If you put a backslash before the underscore, it means that the database
3445 name will have a real underscore.</p>
3449 statistics pages?</a></h4>
3460 if it already exists during the import. It does NOT drop the table after
3461 your export, it only affects the import file.</li>
3463 Otherwise, you may get an error if the table name exists but has a
3464 different structure.</li>
3466 (if any) will be included in backup.</li>
3468 field and table names formed with special characters are protected.</li>
3470 types set in the pmadb in the dump as
3472 </li>
3473 </ul>
3478 command, for better documentation (but resulting file is bigger).</li>
3480 once the INSERT verb and the table name.</li>
3483 </li>
3485 more info is provided in the
3487 but basically with this selected, invalid values are adjusted and
3488 inserted rather than causing the entire statement to fail.</li>
3489 </ul>
3493 in its name.</a></h4>
3496 is the normal way to reference a database and table name. Worse, MySQL
3497 will usually let you create a database with a dot, but then you cannot
3498 work with it, nor delete it.</p>
3511 for usage.<br />
3512 On a more recent pear version, I had problems with the state of Net_DIME
3513 being beta, so this single command
3515 needed modules.<br />
3516 If you use the Validator, you should be aware that any
3518 submit will be stored anonymously (database/table/column names,
3519 strings, numbers replaced with generic values). The Mimer
3522 We utilize it as free SOAP service.</p>
3526 it, but MySQL says "BLOB column '...' used in key specification without
3529 <p> The right way to do this, is to create the field without any indexes,
3531 dialog. On this page, you will be able to choose your BLOB field, and
3532 set a size to the index, which is the condition to create an index on
3533 a BLOB field.</p>
3537 editing fields?</a></h4>
3539 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3540 with many editing fields (table structure changes, row editing, etc.)
3541 (must be enabled in configuration - see.
3543 You can also have a look at the directive
3545 ('vertical') and see if this eases up editing for you.</p>
3549 WTF is this feature then useful for?</a></h4>
3551 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3552 on them. Otherwise you could just put a comment on the field. Because entering
3553 your own mimetype will cause serious syntax checking issues and validation,
3554 this introduces a high-risk false-user-input situation. Instead you have to
3555 initialize mimetypes using functions or empty mimetype definitions.<br />
3556 Plus, you have a whole overview of available mimetypes. Who knows all those
3557 mimetypes by heart so he/she can enter it at will?</p>
3561 can't I see any bookmarks below the query box? What is this variable for?
3562 </a></h4>
3564 <p> Any query you have executed can be stored as a bookmark on the page where the
3565 results are displayed. You will find a button labeled 'Bookmark this query'
3566 just at the end of the page.<br />
3567 As soon as you have stored a bookmark, it is related to the database you run
3568 the query on. You can now access a bookmark dropdown on each page, the query
3569 box appears on for that database.<br /><br />
3571 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3575 aware of that you HAVE to create a valid query, otherwise your query won't be
3576 even able to be stored in the database.<br />
3578 for your query will remain the way it is, but will be stripped of the /**/
3579 chars. So you can use:<br /><br />
3583 which will be expanded to<br /><br />
3587 in your query, where VARIABLE is the string you entered in the input box. If
3588 an empty string is provided, no replacements are made.<br /><br />
3590 A more complex example. Say you have stored this query:<br /><br />
3592 <br /><br />
3595 the full query will be:<br /><br />
3598 <br /><br />
3602 spaces inserted there
3603 will be later also inserted as spaces in your query and may lead to unexpected
3604 results especially when
3606 Your initial query which is going to be stored as a bookmark has to yield at
3607 least one result row so
3608 you can store the bookmark. You may have that to work around using well
3613 include exported table?</a></h4>
3616 document should look like following one (assuming you have table
3619 <pre>
3620 \documentclass{article} % or any class you want
3621 \usepackage{longtable} % for displaying table
3622 \begin{document} % start of document
3623 \include{table} % including exported table
3624 \end{document} % end of document
3625 </pre>
3629 access them.
3630 </a></h4>
3633 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3634 enable users to see all the database names.
3637 So if your users do not need those privileges, you can remove them and their
3638 databases list will shorten.</p>
3642 possible values for a field, based on some foreign table?</a></h4>
3644 <p> You have to setup appropriate links between the tables, and also
3648 foreign table, a drop-down list of values will be available.
3649 You will see two lists of values, the first list containing the key
3650 and the display field, the second list containing the display field
3651 and the key. The reason for this is to be able to type the first
3652 letter of either the key or the display field.<br /><br />
3654 For 200 values or more, a distinct window will appear, to browse foreign
3655 key values and choose one.</p>
3659 automatically when entering Browse mode for a table?</a></h4>
3661 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3662 </p>
3666 Excel files, how can I enable that?</a></h4>
3668 <p> Current version does support direct export to Microsoft Excel and Word
3669 versions 2000 and newer. If you need export older versions, you can use
3671 which works out of the box or you can
3673 several problems, most important are limitation of cell content to 255
3674 chars and no support for charsets, so think carefully whether you want to
3675 enable this.</b>. For enabling this you need to set
3679 module Spreadsheet_Excel_Writer into php include path. The
3680 installation can be done by following command:</p>
3682 <pre>
3683 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3684 </pre>
3686 <p> First part of switches set we want to install beta version of that module
3687 (no stable version available yet) and then we tell pear we want to satisfy
3688 dependencies.</p>
3690 <p> If you are running in PHP safe mode, you will have to set
3693 modules are located, for example:</p>
3695 <pre>
3696 safe_mode_include_dir = /usr/local/lib/php
3697 </pre>
3701 <pre>
3702 cd phpMyAdmin
3703 mkdir tmp
3704 chmod o+rwx tmp
3705 </pre>
3709 what happens to my column comments stored in pmadb?</a></h4>
3711 <p> Automatic migration of a table's pmadb-style column comments to the native
3712 ones is done whenever you enter Structure page for this table.</p>
3719 <p> Our Bug Tracker is located at
3721 under the Bugs section.<br /><br />
3723 But please first discuss your bug with other users:<br />
3729 existing language, where do I start?</a></h4>
3731 <p> Always use the current CVS version of your language file.
3733 don't know how to get the CVS version, please ask one of the developers.
3734 <br />
3735 Please note that we try not to use HTML entities like &eacute; in
3736 the translations, since we define the right character set in the file.
3737 With HTML entities, the text on JavaScript messages would not
3738 display correctly.
3739 However there are some entities that need to be there, for quotes
3740 ,non-breakable spaces, ampersands, less than, greater than.<br />
3741 You can then put your translations, as a zip file to avoid losing special
3742 characters, on the sourceforge.net translation tracker.<br />
3743 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3744 list, because this is where we ask for translations of new messages.</p>
3748 phpMyAdmin. How should I proceed?</a></h4>
3753 <tt>cvs -d:pserver:anonymous@phpmyadmin.cvs.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
3754 [Password: simply press the Enter key]<br />
3755 <tt>cvs -z3 -d:pserver:anonymous@phpmyadmin.cvs.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
3756 [This will create a new sub-directory named phpMyAdmin]</li>
3758 <li>put the modified files (tar'ed and gzip'ed) inside the patch tracker of
3759 the
3761 </li>
3762 </ol>
3764 <p> Write access to the CVS tree is granted only to experienced developers who
3765 have already contributed something useful to phpMyAdmin.<br />
3776 The phpMyAdmin development team received notice of this security alert:
3777 <a href="http://www.securityfocus.com/archive/1/325641">http://www.securityfocus.com/archive/1/325641.</a>
3778 <br /><br />
3780 The team regrets that the author did not communicate with us before
3781 sending this alert. However, here is our current reply to the points mentioned:
3782 </p>
3786 This problem had been fixed in version 2.5.0, even if the author reports
3787 the 2.5.2 development version as vulnerable, which we could not reproduce.
3788 </li>
3792 This is a misleading title, as the author tells in his text:
3797 It was possible to retrieve the list of phpMyAdmin's directory (which we
3802 Most of the XSS problems have been fixed in version 2.5.0. The rest
3805 We believe that the Path disclosures problems have also been fixed
3810 We believe that an exploit for this weakness would be difficult
3811 to achieve. However version 2.5.2 now encrypts the password
3812 with the well-known blowfish algorithm.</li>
3813 </ul>
3819 <br /><br />
3820 The phpMyAdmin development team received notice of this security alert:
3823 <br /><br />
3824 We would like to put emphasis on the disappointment we feel when a
3825 bugreporter does not contact the authors of a software first, before
3826 posting any exploits. The common way to report this, is to give the
3827 developers a reasonable amount of time to respond to an exploit before
3828 it is made public.<br /><br />
3831 to this problem, if each of the following conditions are met:</p>
3834 <li>In config.inc.php,
3836 is set to FALSE
3838 <li>There is no firewall blocking requests from the Web server to the
3839 attacking host.</li>
3840 </ul>
3846 </a></h4>
3848 <p> Please refer to
3850 for the complete list of security alerts.</p>
3852 <!-- DEVELOPERS -->
3855 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3856 great features have been written by other people and you too can help to
3857 make phpMyAdmin a useful tool.</p>
3859 <p> If you're planning to contribute source, please read the following
3860 information:</p>
3866 it free from other code.<br />
3867 Commonly used functions should be added to
3870 <li>Obviously, you're free to use whatever coding style you want. But
3871 please try to keep your code as simple as possible: beginners are
3872 using phpMyAdmin as an example application.<br />
3873 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3874 compliant on one hand, they fit the
3877 coding standards</a>
3878 on the other hand. Please pay attention to this.</li>
3879 <li>Please try to keep up the file-naming conventions. Table-related stuff
3882 <li>Please don't use verbose strings in your code, instead add the string
3887 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3888 better debug and profile their code.<br />
3889 Please see the
3891 options for more information.<br />
3892 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3893 lost during its re-entry into Earth's atmosphere and in memory of the
3894 brave men and women who gave their lives for the people of Earth.</li>
3895 </ul>
3897 <!-- CREDITS -->
3900 <pre>
3901 phpMyAdmin - Credits
3902 ====================
3904 CREDITS, in chronological order
3905 -------------------------------
3908 * creator of the phpmyadmin project
3912 * multi-language version
3913 * various fixes and improvements
3915 * current project maintainer
3918 * started SourceForge phpMyAdmin project in March 2001
3919 * sync'ed different existing CVS trees with new features and bugfixes
3920 * multi-language improvements, dynamic language selection
3921 * current project maintainer
3922 * many bugfixes and improvements
3925 * rewrote and optimized javascript, DHTML and DOM stuff
3926 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
3927 generate XHTML1.0 and CSS2 compliant codes
3928 * improved the language detection system
3929 * many bugfixes and improvements
3932 * database maintenance controls
3933 * table type code
3935 * DB-based configuration (Not completed)
3938 * many bugfixes and improvements
3941 * bookmarks feature
3942 * multiple dump feature
3943 * gzip dump feature
3944 * zip dump feature
3947 * various fixes
3948 * moderator of the phpMyAdmin former users forum at phpwizard.net
3954 * rewrote and fix dump code
3955 * bugfixes
3958 * rewrote dump code for PHP4
3959 * mySQL table statistics
3960 * bugfixes
3963 * main author of the version 2.1.0.1
3964 * bugfixes
3968 * abstract database interface (PMA_DBI) with MySQLi support
3969 * privileges administration
3971 * various features and fixes
3972 * German language file updates
3975 * automatic joins in QBE
3976 * links column in printview
3977 * Relation view
3980 * enhanced index creation/display feature
3981 * feature to use a different charset for HTML than for MySQL
3982 * improvements of export feature
3983 * various features and fixes
3984 * Czech language file updates
3987 (http://sf.net/projects/phpmysqlformgen/)
3988 * suggested the patch for multiple table printviews
3991 * built the patch for vertical display of table rows
3992 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
3993 * Improvement of column/db comments
3994 * (MIME)-Transformations for columns
3995 * Use custom alias names for Databases in left frame
3996 * hierarchical/nested table display
3997 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
3998 * new icon sets
3999 * vertical display of column properties page
4000 * some bugfixes, features, support, German language additions
4003 * japanese kanji encoding conversion feature
4006 * the Cookie authentication mode
4009 * table relation-links feature
4012 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4013 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4014 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4020 * phpMyAdmin logo (until June 2004)
4023 * blowfish library from the Horde project
4026 * mysqli support
4027 * many bugfixes and improvements
4030 * redesign for 2.6.0
4031 * phpMyAdmin sailboat logo (June 2004)
4034 * Representation at conferences
4037 * interface improvements
4038 * various bugfixes
4040 And also to the following people who have contributed minor changes,
4041 enhancements, bugfixes or support for a new language since version 2.1.0:
4043 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4044 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4045 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4046 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4048 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4049 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4050 Luís V., Martijn W. van der Lee,
4051 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4055 Original Credits of Version 2.1.0
4056 ---------------------------------
4058 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4059 to create a web-based interface to MySQL using PHP3. Although I have not
4060 used any of his source-code, there are some concepts I've borrowed from
4061 him. phpMyAdmin was created because Peter told me he wasn't going to
4062 further develop his (great) tool.
4063 Thanks go to
4065 code for the check when dropping a table or database. He also suggested
4066 that you should be able to specify the primary key on tbl_create.php3. To
4067 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4068 well as a bug-report. Plus many smaller improvements.
4070 were introduced in 1.3.0 (including quite significant ones like the
4071 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4072 bug-fixes and help.
4074 language-independent by outsourcing the strings to a separate file. He
4075 also contributed the French translation.
4077 tbl_select.php3, a feature to display only some fields from a table.
4079 functions in tbl_change.php3. He also added the
4082 servers and is a regular contributor for bug-fixes.
4084 features for 2.0.6.
4085 The following people have contributed minor changes, enhancements, bugfixes
4086 or support for a new language:
4087 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4088 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4089 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4090 G. Wieggers.
4092 And thanks to everyone else who sent me email with suggestions, bug-reports
4093 and or just some feedback.
4094 </pre>
4100 <ul>
4102 - the default name of Apache's directory-level configuration file.</li>
4106 - a software application that enables a user to display and interact with
4107 text, images, and other information typically located on a web page at a
4108 website on the World Wide Web.</li>
4110 - a free software/open source data compression algorithm and program
4111 developed by Julian Seward.</li>
4113 - an important World Wide Web technology that enables a client web browser
4114 to request data from a program executed on the Web server.</li>
4116 - a log or record of changes made to a project.</li>
4118 - a computer system that accesses a (remote) service on another computer
4119 by some kind of network.</li>
4121 - a set of data values of a particular simple type, one for each row of
4122 the table.</li>
4124 - a packet of information sent by a server to a World Wide Web browser
4125 and then sent back by the browser each time it accesses that server.</li>
4127 - Comma-seperated values</li>
4130 - an organized collection of data.</li>
4133 - a PHP module that extends PHP with additional functionality.</li>
4135 - a list of commonly asked question and there answers.</li>
4137 - one part of divided data/columns.</li>
4139 - a field or group of fields in a database record that point to a key
4140 field or group of fields forming a key of another database record in some
4141 (usually different) table.</li>
4143 - the free PDF library</li>
4145 GD Graphics Library</a> - a library by Thomas Boutell and others for
4146 dynamically manipulating images.</li>
4149 - gzip is short for GNU zip, a GNU free software file compression
4150 program.</li>
4152 - any machine connected to a computer network, a node that has a hostname.</li>
4154 - the unique name by which a network attached device is known on a network.</li>
4156 (HyperText Transfer Protocol)</a>
4157 - the primary method used to transfer or convey information on the World
4158 Wide Web.</li>
4161 additional security measures.</li>
4162 <li><a href="http://www.wikipedia.org/wiki/Internet Information Services">IIS (Internet Information Services)</a>
4163 - a set of Internet-based services for servers using Microsoft Windows.</li>
4165 - a feature that allows quick access to the rows in a table.</li>
4167 - a data-oriented protocol used by source and destination hosts for
4168 communicating data across a packet-switched internetwork.</li>
4170 - a unique number that devices use in order to identify and communicate
4171 with each other on a network utilizing the Internet Protocol standard.</li>
4173 (Internet Server Application Programming Interface)</a>
4174 - the API of Internet Information Services (IIS).</li>
4176 - a business or organization that offers users access to the Internet and related services.</li>
4178 - a most commonly used standard method of lossy compression for
4179 photographic images.</li>
4182 <li><a href="http://www.wikipedia.org/wiki/L<sub>A</sub>T<sub>E</sub>X">L<sub>A</sub>T<sub>E</sub>X</a>
4185 - line of personal computers is designed, developed, manufactured, and
4186 marketed by Apple Computer.</li>
4187 <li><a id="glossar_mac_os_x" href="http://www.wikipedia.org/wiki/Mac OS X"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>
4188 - the operating system which is included with all currently shipping Apple
4189 Macintosh computers in the consumer and professional markets.</li>
4191 - a cryptographic library.</li>
4193 - the MCrypt PHP extension.</li>
4194 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4195 - an Internet Standard for the format of e-mail.</li>
4197 - some sort of extension for the Apache Webserver.</li>
4199 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4200 Management System (DBMS).</li>
4202 - the improved MySQL client PHP extension.</li>
4204 - the MySQL client PHP extension.</li>
4206 - open standard for office documents.</li>
4207 <li><a href="http://www.wikipedia.org/wiki/OS X"><abbr title="operating system">OS</abbr> X</a>
4208 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4210 (Portable Document Format)</a>
4211 - a file format developed by Adobe Systems for representing two
4212 dimensional documents in a device independent and resolution independent
4213 format.</li>
4215 - the PHP Extension and Application Repository.</li>
4217 - the perl-compatible regular expression functions for PHP</li>
4219 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4220 programming language used mainly for developing server-side applications
4221 and dynamic web content, and more recently, a broader range of software
4222 applications.</li>
4224 - a connection through which data is sent and received.</li>
4226 - Request for Comments (RFC) documents are a series of memoranda
4227 encompassing new research, innovations, and methodologies applicable to
4228 Internet technologies.</li>
4232 - represents a single, implicitly structured data item in a table.</li>
4234 - a computer system that provides services to other computing
4235 systems over a network.</li>
4236 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4237 - handlers for different table types</li>
4239 - a form of inter-process communication.</li>
4241 Sockets Layer)</a>
4242 - a cryptographic protocol which provides secure communication on the Internet.</li>
4244 - Structured Query Language</li>
4246 - a set of data elements (cells) that is organized, defined and stored as
4247 horizontal rows and vertical columns where each item can be uniquely
4248 identified by a label or key or by it?s position in relation to other items.</li>
4251 - a type of archive file format: the Tape ARchive format.</li>
4253 - one of the core protocols of the Internet protocol suite.</li>
4257 - a sequence of characters, conforming to a standardized format, that is
4258 used for referring to resources, such as documents and images on the
4259 Internet, by their location.</li>
4261 - A computer (program) that is responsible for accepting HTTP requests
4262 from clients and serving them Web pages.</li>
4264 - a W3C-recommended general-purpose markup language for creating
4265 special-purpose markup languages, capable of describing many different
4266 kinds of data.</li>
4268 - a popular data compression and archival format.</li>
4270 - an open-source, cross-platform data compression library by Jean-loup
4271 Gailly and Mark Adler.</li>
4272 </ul>
4282 </body>
4283 </html>