Am 28.05.2011 23:00, schrieb Ryan Lane:
hooks should
-go/come via the core, and in consequence
-via Auth.
We were talking about something completely
unrelated. Unless MediaWiki supports user deletion and merging, this
should not be in core. The hooks should go in the extension that
then I understood you, let's say, partially. Your last sentence
clarifies the situation in that you indirectly confirm, that the
introduction of the two hooks
DeleteAccount and MergeAccountFromTo (in UserMerge and in OpenID
extensions) is -currently- the correct and only way.
If the
On Sun, May 29, 2011 at 6:41 PM, Ryan Lane rlan...@gmail.com wrote:
I'm not sure we have standards on hook names (someone please correct
me, if this isn't the case).
In core, there certainly is no naming convention for hooks. Some are verb
phrases, some are noun phrases. I think if you're
On 11-05-29 03:48 PM, Chad wrote:
On Sun, May 29, 2011 at 6:41 PM, Ryan Lane rlan...@gmail.com wrote:
I'm not sure we have standards on hook names (someone please correct
me, if this isn't the case).
In core, there certainly is no naming convention for hooks. Some are verb
phrases, some are
Chad wrote:
On Sun, May 29, 2011 at 6:41 PM, Ryan Lane rlan...@gmail.com wrote:
I'm not sure we have standards on hook names (someone please correct
me, if this isn't the case).
In core, there certainly is no naming convention for hooks. Some are verb
phrases, some are noun phrases. I
Am 30.05.2011 01:05, schrieb Platonides:
Chad wrote:
On Sun, May 29, 2011 at 6:41 PM, Ryan Lane rlan...@gmail.com wrote:
I'm not sure we have standards on hook names (someone please correct
me, if this isn't the case).
In core, there certainly is no naming convention for hooks. Some are verb
Status:
http://www.mediawiki.org/wiki/Manual:Hooks/AddNewAccount is currently
the only Account-adminstration related hook which changes table user -
as far as I can see.
Problem (solved yesterday)
OpenID needs to be informed when an account is deleted or merged, which
currently UserMerge
As suggested some days ago by Ryan Lane - and I support his view - such
hooks should
- go/come via the core, and in consequence
- via Auth.
The two hooks should be implemented in core as
abstract public function ()
or whatever is conformity to our standards (pls. let me know).
