[pLog-svn] r5080 - plugins/branches/lifetype-1.2/authimage/templates

[Oscar Renalias]

There's no need to do that, see the message I just sent. Clients can
set whatever values they want in the blog settings, but code is smart
enough to return the global value if it cannot be overriden,
regardless of the value in the blog settings.

Otherwise plugin code gets too messy, as for each one of the settings
we'd need to check if overrideable and if so save it, or discard the
value otherwise. The whole point of the global settings framework was
that it could be implemented with little or no effort (although it
turned out to be "little effort" rather than "no effort" :))

On 3/13/07, Reto Hugi <plog at hugi.to> wrote:
> Jon Daley wrote:
> >     I think the global can't-override setting needs to be checked in the
> > updateconfigaction.
>
> I think that would be the best solution. if the user cannot override it,
> he doesn't need to send it. The updateconfigaction should check if the
> value can be overriden by the user or not. if the user cannot override
> the settings, the request variable should be ignored (this would prevent
> saving settings to the blog-based plugin settings if "readonly" is
> removed on the client side)
>
>
> _______________________________________________
> pLog-svn mailing list
> pLog-svn at devel.lifetype.net
> http://limedaley.com/mailman/listinfo/plog-svn
>