Hi,
I suggest to remove chinese from sync_lang.sh, as I was never
able to do the conversion here (with recode) and we always get
all the files from the chinese translators.
Marc
The Internet, 2003-07-30
Greetings,
the phpMyAdmin development team announces the availability of the first
patch level version for phpMyAdmin 2.5.2.
It contains only critical bugfixes over version 2.5.2, and is believed to be
the most stable version.
The final version of 2.5.3 is planned on August 31st.
Download/support information on http://www.phpmyadmin.net.
Marc Delisle, for the team.
The Internet, 2003-07-29
Greetings,
the phpMyAdmin development team is pleased to announce availability of the first
release candidate for phpMyAdmin 2.5.3.
This one comes early, because some last-minute bugs found their way into 2.5.2.
MySQL 4.1 Note:
phpMyAdmin's MySQL 4.1 support is still experimental
Improvements:
* MySQL 4.1: new page about Character sets and collations
* better support for MySQL charsets
* LIKE in Select sub-page for non-text fields
* optional icons for actions
* better PHP code generation
* possibility to let phpMyAdmin continue execution of a multi-query statement even though single queries may fail
* possibility to display the result of each query of a multi-query statement
* display MySQL error code and link to relevant documentation
Fixes:
* Removed lowercase transformation of SQL
* "Missing..." messages were wrongly displayed
* armascii8 appears twice in the charset list
* InnoDB and multi-columns foreign key
* Confirmation for TRUNCATE statements
* InnoDB and cross-db foreign keys
* A user could not edit his own global privileges
* Obey fmtType when set to 'none'
* SELECT DISTINCT was broken (MySQL 3)
Download/support information on http://www.phpmyadmin.net.
Marc Delisle, for the team.
(Darn, I always get screwed by the new 'members-only' E-Mail adress catcher. So, again:
I posted this earlier today:)
Hi All!
I modified the handling of multi-query submits today. (RFE #771282)
The intention was, to optionally let a multi-query be executed, even though there could
be errors in it. As this is normally not useful, I put a configuration directive
($cfg['IgnoreMultiSubmitErrors']) to it. It will be deactivated by default. The
mysql_die() function will then print each failed query.
The other feature is a more verbose output for each query ($cfg['VerboseMultiSubmit']).
If this is set, the results (affected_rows / num_rows / failure) of EACH query will be
appended as a MySQL comment into the SQL-Query output. I also changed how many
lines/pieces per file/query are allowed until bandwidth saving gets activated and no
results are shown. I put the configuration directly into read_dump.php3 because I think
putting it into configuration is a bit too much.
I checked it for all my basic queries and I hope the changes are non-intrusive. Can you
please all test it?
--
Bye,
Garvin.
--
Bye,
Garvin.
Hi Garvin & list,
I was just wondering what this change is good for, except breaking our
beautiful XHML code... *g*
http://cvs.sourceforge.net/cgi-
bin/viewcvs.cgi/phpmyadmin/phpMyAdmin/header.inc.php3.diff?r1=1.94&r2=1.95
I'd be glad if someone could enlighten me... :-)
Regards,
Alexander
Hi,
I like the new icons! I hope that those are not copyrighted...
Could we use the same new Browse icon in the left frame?
Also, if someone can design a good one for Edit, we could
use it in the displayed results, along with the trashcan.
Marc
Hi,
in libraries/grab_globals:
-------------
if (!empty($_SERVER)) {
if (isset($_SERVER['PHP_SELF'])) {
$PHP_SELF = $_SERVER['PHP_SELF'];
}
if (isset($_SERVER['HTTP_ACCEPT_LANGUAGE'])) {
$HTTP_ACCEPT_LANGUAGE = $_SERVER['HTTP_ACCEPT_LANGUAGE'];
}
} else if (!empty($HTTP_SERVER_VARS)) {
if (isset($HTTP_SERVER_VARS['PHP_SELF'])) {
$PHP_SELF = $HTTP_SERVER_VARS['HTTP_ACCEPT_LANGUAGE'];
}
if (isset($HTTP_SERVER_VARS['PHP_SELF'])) {
$HTTP_ACCEPT_LANGUAGE =
$HTTP_SERVER_VARS['HTTP_ACCEPT_LANGUAGE'];
}
} // end if
--------------
I think should be replaced by:
--------------
if (!empty($_SERVER)) {
if (isset($_SERVER['PHP_SELF'])) {
$PHP_SELF = $_SERVER['PHP_SELF'];
}
if (isset($_SERVER['HTTP_ACCEPT_LANGUAGE'])) {
$HTTP_ACCEPT_LANGUAGE = $_SERVER['HTTP_ACCEPT_LANGUAGE'];
}
} else if (!empty($HTTP_SERVER_VARS)) {
if (isset($HTTP_SERVER_VARS['PHP_SELF'])) {
$PHP_SELF = $HTTP_SERVER_VARS['PHP_SELF'];
}
if (isset($HTTP_SERVER_VARS['HTTP_ACCEPT_LANGUAGE'])) {
$HTTP_ACCEPT_LANGUAGE =
$HTTP_SERVER_VARS['HTTP_ACCEPT_LANGUAGE'];
}
} // end if
-------------------
Objections?
Marc
The Internet, 2003-07-22
Greetings,
the phpMyAdmin development team is pleased to announce the availability
of phpMyAdmin 2.5.2.
Improvements:
* Preserve edited contents of the query window
* Uploading of SQL when no database selected
* Optional server list drop-down in left frame
* "Options" tab merged in "Operations"
* PDF report: paper size selection
* $cfg['LimitChars'] now limits all non-numeric fields
* MySQL 4.1 support: table and field charsets
* Better Export functionnality, including export for big tables
* Partial support for InnoDB foreign keys: PDF report, Select tab,
results display
* Visual editor (scratchboard) for PDF schema
* Export any query in CSV, LaTeX, XML
* Warning for missing length on VARCHAR
* Export: checkbox for AUTO_INCREMENT value
* Gzip output buffer: auto-detection and set to FALSE for IE 6.x
* Display CREATE DATABASE query
Fixes:
* MySQL 4.1 related fixes:
o User was unable to edit column privileges
o The table structure page sometimes displayed "Array" in the
charset column
o When altering the field type, the input box for the field
length sometimes had a strange default value
o Erroneous export of timstamp fields
o Incorrect row count for subqueries
o Errors when inserting ENUM / SET values (in CVS)
* Now use TRUNCATE with MySQL 4 when emptying multiple tables
* Various HTML pretty printer problems
* Bad display of parser bug report
* docSQL and filename disclosure
* Row count and DISTINCT
* GD2 autodetection
* Cookie: encrypt password (blowfish)
* Wrong field names when exporting query results
* Support for PROCEDURE ANALYSE
* Security fix against bad JS code
* Proper escaping in inline images
* Safari detection and proper fonts
* PDF schema and hardcoded A4 scaling
* Incorrect row count for UNION
* Better behavior when phpMyAdmin is within a frameset
* Backslashes in username or password
* Query statistics: percentages were wrong
* Checks to avoid path disclosures
* Do not display "Check referential integrity" for InnoDB tables.
Download/support information on http://www.phpmyadmin.net.
Regards,
Marc Delisle, for the team.
