> Although I understand your point (I have to update some plugins too to reflect > that change too, and I already see the forum been hit by a wave of "where does > this '%' come from" threads ;)), I think that the introduction of a new $conf > setting, just to prevent "cosmetical" bugs in plugins, would lead to a much > more unwanted situation, namely that the plugin authors don't even notice that > something has changed and that they need to update their plugins accordingly. This means that a subset of users will be stuck in a situation like "I can't update my wiki because the new release is incompatible with plugin X, but the author of X has gone away and I'm not a programmer". What about a middle ground like: make this an option but set it to off by default (ie. there is a checkbox in the administration interface where it says "auto-generate old date format string" which is unchecked by default)? PS. A small critique: it is bad practice (imho) to change the interface of a software (and by interface I mean the programmatic way of interacting with it, not the GUI) in a way which is purposefully incompatible with the old one (like changing the format of a configuration variable). Even more so when the given interface is semi-public and it is known that third-party code relies on it. Given how flexible dynamic programming languages like PHP are, it is much nicer to introduce a new property with the desired meaning and let the old property alone. Best regards. ___________________________________________________________ Rise to the challenge for Sport Relief with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/ -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist