Administering configuration

[anonymous]

Some of the configuration is administered via the Plogger Options page and other configuration is set in various files and still other configuration is in a SQL table.

Plogger would be easier to administer if all configuration information was stored in SQL and configurable via the Admin UI in Plogger.

You could have a feature to load and save configuration from and to a file to apply it to a different server, etc.

[mike]

Anonymous,

All the configuration information is stored in SQL. The only variables that aren't stored in SQL are the SQL connection parameters, and how would you get into your database without those?

If you want to move your configuration information from one server to another, you can use the PHPMyAdmin export function on the plogger_config table. However, some information, such as pathnames and such, will differ on your new server.

[sidtheduck]

As mike mentioned, this is already how it is set (with the additional exceptions of the new FTP workaround for safe_mode servers and the PLOGGER_EMBEDDED override).

I'm closing this since all options are either already in the SQL table (which is accessible via the Admin -> Options tab or phpMyAdmin) or, to a lesser amount, the plog-config.php file (which, again, is needed to connect to the SQL database to fetch the other options).