#1584 (ok 4.3.5) Update documentation for automatic Configuration Storage feature

[Isaac Bennetch]

We should update the documentation, specifically the part about creating and configuring the phpMyAdmin Configuration Storage, to reflect the new automatic features.

I suggest leaving the existing documentation but adding a line mentioning the automatic stuff.

[Christian Wittmer]

Will the USER have a chance to DECIDE if he wants this automatic features ?

[Isaac Bennetch]

Yes, of course the user has the power to decide here. The $cfg['ZeroConf'] directive is for this purpose :)

[Isaac Bennetch]

Proposed fix: https://github.com/phpmyadmin/phpmyadmin/pull/1449

[Christian Wittmer]

sorry, but AFAIK does the ZeroConf VAR not enable or disable the pma_storage config. It enables pma_storage for each DB.

$cfg['ZeroConf']
Type: boolean
Default value: true

Enables Zero Configuration mode in which the user will be offered a choice to create phpMyAdmin configuration storage in the current database or use the existing one, if already present.

Note: If there is no central configuration storage defined then you may end up with different set of phpMyAdmin configuration storage tables for different databases.

[Marc Delisle]

Christian, starting from version 4.3.5, the phpMyAdmin configuration storage is no longer automatically created. If the ZeroConf directive is true, user has a chance to create these tables via Operations of one database, without configuring anything.

[Christian Wittmer]

Marc, thanks for info.
So if I understand you right, then with 4.3.5 no pma storage is used when ZeroConf is false even if the pma VARS are configured.

Does this also change the previous behavior ?
Enables Zero Configuration mode in which the user will be offered a choice to create phpMyAdmin configuration storage in the current database or use the existing one, if already present.

[Marc Delisle]

Well, if the variables are configured and the tables exist in the configured pmadb, the features are active.

[Christian Wittmer]

IMHO the variables are always configured (by default). The important question is which value they should have, when 'admin' wants to have
a) no pma storage configuration at all
b) automatic pma config with default pmadb 'pmadb' and default controluser 'pma'.

[Marc Delisle]

No, by default these variables are empty (see libraries/config.default.php).

[Christian Wittmer]

uhhm ... we have a misunderstanding ...

would this config http://paste.opensuse.org/50144141
result in a 'disabled' pma storage ?
Or what do I need to do for disabling this 'automatism' ?

And would ZerConf = true, as well as pmadb = "pmadb" result in enabling ?

Thanks for clarification

[Marc Delisle]

Are you talking about version 4.3.5?

[Christian Wittmer]

Yes, 4.3.5 and newer.

P.S.: Are you on IRC (#phpmyadmin / ChrisWi)? We could talk about this, because it is important not for me alone. I maintain the SUSE phpMyAdmin package.

[Marc Delisle]

Christian,
First, your sample file is just that, a sample file. config.sample.inc.php is not executed.

Assuming that this file is copied over to config.inc.php, there are still two problems with it: The <?php prefix is missing, and $i is not initialized. If these problems are fixed, the user won't be offered a chance to use the ZeroConf feature to create his own configuration storage tables.

To enable, well it depends what you want to enable exactly, and it depends if this is for a multi-user installation or not.

[Christian Wittmer]