[Koha-devel] Moving system preference serialization into the database

[Chris Nighswonger]

Ok. Here is a quick fix which seems to be what everyone is headed
toward. Please abuse it a bit and see if it meets the present
criteria.

http://git.koha-community.org/gitweb/?p=wip/koha-fbc.git;a=commit;h=5b23a615018e049b1e11dbc10b131ecb30dfc6ab

On Mon, Jul 12, 2010 at 2:46 PM, Frederic Demians <frederic at tamil.fr> wrote:
>>
>> The former case would also change the security profile of Koha
>> significantly.  Allowing your application to write to template directories
>> is bad practice.  Among other things, if you happen to be running your Koha
>> installations off of git repos (as I know several vendors do), then having
>> new uncommitted changes in the repo will *block* git pull/rebase for
>> updates.  I regard it as inadvisable.
>
>
> +1
>
>> The latter is also undesirable, but only because we are talking about
>> trying to translate SQL, and for the reasons Frederic points out having to
>> do with translation.  Therefore the fix is to do something like allowing to
>> Koha to ingest values from a template file at install and runtime.  Read the
>> template (doesn't have to be H:T:P, as long as we can get PO files from it),
>> parse it to whatever, match against keys in the syspref table and update
>> description.
>
> That's how it works now with .pref being specifically tokenized to extract
> text to be translated which are written into a .po file.
> --
> Frédéric
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel