Re: [Phpwiki-talk] config in db

[Reini U. <ru...@x-...>]

Joby Walker schrieb:
> I agree completely.
> 
> There are just far too many config settings to continue the way we are 
> going. We can also use the database keep historical config settings to 
> allow for the roll back of configuration settings.  It should help 
> simplify the config/* files (which I need to get back to...).

Ok. But before I do the config stuff (which I really want to do now, 
because I don't dare to commit the new index.php for my new config 
settings, which requires a manual hack in the demo site after the daily 
automatic checkout), I'll implement proper page permissions.

I already changed phpwiki.sf.net/demo/index.php to reallow USE_PATH_INFO 
and all the supported languages, even if the database got raided.

The current new user scheme is quite strict.
e.g. previously ALLOW_ANON_USER = false meant that anon users cannot 
edit, but may browse. With ENABLE_USER_NEW and ALLOW_ANON_USER = false 
he may even not browse which is needed to disable browse PagePermissions 
for a certain user.
So I will implement PagePermissions to get rid of ALLOW_ANON_USER = 
false, which is quite annoying and check permissions per page resp. 
action and user and optionally group.

> Reini Urban wrote:
>> Hi (Joby)
>> Why not storing the index.php configuration in the database, table 
>> config, editable only by the admin?
>>
>> This is much easier to install and maybe easier to maintain then the 
>> current file based solution. then we will be able to have a tiny 
>> index.php. lib/config.php will then load and verify the config 
>> settings, using config/*
>>
>> The only problem I see is that without working database connection one 
>> cannot edit the config...
>> maybe use a single dba/gdbm/sqlite/flat-file file therefore.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/