I wonder if the "Tracking" db and table menu tab should be replaced by a
link, either under Structure or Operations.
I would be tempted to move Designer as a link under Structure but it's
been as a menu tab for a while so I don't know.
Maybe a "Files" menu could lead to Export - Import - Backup - Restore
(these last two being future items probably in 3.4)? If so, should we
start to implement another level of menus?
am I the only one who get a white page with this revision? Source page
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="icon" href="./favicon.ico" type="image/x-icon" />
<link rel="shortcut icon" href="./favicon.ico" type="image/x-icon" />
<link rel="stylesheet" type="text/css"
Welcome to the first beta of phpMyAdmin 3.3.0. The main new features are:
- new import and export modules
- changes tracking
- synchronizing structure and data between servers
- replication support
The development team will appreciate your testing and feedback about
Details will appear on http://phpmyadmin.net. In a hurry? you can visit
http://sourceforge.net/projects/phpmyadmin to download.
Marc Delisle, for the team
I still get warning from phpMyAdmin about timezones:
Warning in ./libraries/common.inc.php#291
date_default_timezone_get(): It is not safe to rely on the system's
timezone settings. You are *required* to use the date.timezone setting
or the date_default_timezone_set() function. In case you used any of
those methods and you are still getting this warning, you most likely
misspelled the timezone identifier. We selected 'Europe/Berlin' for
'CET/1.0/no DST' instead
And I started to think if it would not be better to make timezone our
configuration (in config and in store it in cookie) with default to UTC
to get rid of this warning.
I know this can be fixed by changing php.ini, but there is lot of
people who can not do it.
Michal Čihař | http://cihar.com | http://blog.cihar.com