Recent changes to feature-requests

Japanese translation updated

2006-05-02T14:45:14Z

I Japanese translation updated.
Current translation file is supporting only Encoding of
EUC-JP.
I added encoding of UTF-8 this time, and added one
element to $langueTranslated.
-4=>"German", 5=>"Japanese", 6=>"Italian",
+4=>"German", 5=>"Japanese(EUC-JP)", 6=>"Italian",
7=>"Croatian", 8=>"Brazilian portuguese",
9=>"Netherlands",
10=>"Spanish", 11=>"Danish", 12=>"Chinese traditional",
-13=>"Chinese simplified");
+13=>"Chinese simplified", 14=>"Japanese(UTF-8)");

An official Japanese translator's Rui checked this
translation and idea.

Please check also by dev-team.

autodetection for SQLITE3

2005-11-08T13:34:37Z

Hi,
why does SQLiteManager not try some kind of
autodetection? f.e. I tested with:
--- user_defined.inc.php.orig Sun Oct 23 22:03:40
2005
+++ user_defined.inc.php Tue Nov 08 14:22:00 2005
@@ -20,8 +20,9 @@
* if you want to manage SQLite database version 3, you
must install 'php_pdo' and 'php_pdo_sqlite' extension
from PECL
* after you can set 'SQLITE3' contant to true
*/
-// define("SQLITE3", false);
-
+if (extension_loaded('pdo') &&
extension_loaded('pdo_sqlite')) {
+ define("SQLITE3", true);
+}
/**
* By default the DEBUG mode depend of
SQLiteManagerVersion, if it's finish by 'CVS' debug mode
turn on
* You can force debug mode to on by setting 'DEBUG'
constante

Guenter.

CVS exports

2005-05-06T17:09:10Z

Exporting in comma separated values could be very handy.

Define HTTP root folder

2005-01-21T15:09:47Z

I didn't want to run SQLiteManager 1.0.4 from my HTTP
server root
http://127.0.0.1/
but from
http://127.0.0.1/sqlite/

So I added a line to defined.inc.php
include\defined.inc.php(14): define ("HTTP_ROOT",
"/sqlite/");
and modified the URL references (src=, href=) in
index.php(19)
index.php(22)
index.php(23)
left.php(17)
left.php(23)
main.php(45)
main.php(49)
main.php(58)
include\common.lib.php(217)
include\common.lib.php(218)
include\common.lib.php(498)
include\SQLiteDbOption.class.php(116)
include\SQLiteDbOption.class.php(118)
include\SQLiteDbOption.class.php(208)
include\TableIndex.class.php(142)

It seems to work well, now I can access
http://127.0.0.1/sqlite/
:-)

Keep up the good work,
René

cookie authentication

2005-01-17T05:16:07Z

On Apache servers the http-www authentication doesn't
work when PHP is running in CGI mode - it requires PHP
to be run as an Apache module (like php5apache2.dll).

However, on the combination PHP 5 (5.0.3) and Apache2
on the Windows 2000 pro platform certain database
operations causes the Apache2 to produce a fatal error
messagebox when PHP is run as an Apache module (via
php5apache2.dll), and since this errorcondition doesn't
exist in CGI mode (via php-cgi.exe), it would be most
useful to run PHP in CGI mode.

Since the http-www authentication isn't available when
PHP is running in CGI mode, it would be most useful if an
option to use cookie based authentication was added to
SQLiteManager.

Best regards,
Arne

Support different encodings

2005-01-15T12:22:38Z

It would be very useful e.g. to have the page encoded
in UTF-8, so that if the DB has content in UTF-8 it
shows correctly and also text input in TEXT fields get
upload in UTF-8 by the browser.

Using iconv() you can easily have translation files in
one encoding but produce a different encoding for the
browser.

I can provide a patch if you like the feature.

Importing SQLite database files.

2003-12-04T15:27:45Z

Sometimes the user might have the SQLite database file
created in another program, or in another script. There
is a problem - how to make SQLitemanager see this
database? I was making it like that:

- Create a new database.
- Copy into it another database file, which overwrites it.
- SQLitemanager sees it.

I think it would be a good way to allow the user to
import unregistered in the SM databases (and also
removing them from the configuration db!).