Le 01/04/2014 14:23, Tomasz Sterna a écrit :
Just remove 'active' module from 'user-load' chain in your sm.xml.
Oh, haven't thought of that. *dumb me*
(I wrongly assumed all the modules would fail to user_load without
calling user_create first. Didn't think it was the purpose of the active
module and that all the others should do fine xD).
I found only one other module relying on the "active" status :
"roster-publish". I need to deactivate roster-publish (it relies on
roster-items and roster-group that are not used when using my custom
roster plugin, and i don't use ldap).
Is it safe/better/not a good idea to deactivate the active plugin from
every chain (user_load; user_create; user_delete) ?
The sm.xml seems to indicate that the deliver plugin also use the active
status, but I couldn't find any of this in the code.
You may want to implement the fail-if-not-exist function in your own
roster module in this chain.
For now, I think it's ok : users can not connect to any c2s without
"existing" and can not register through XMPP. But I take good note of
this advice if ever I need it.
Thank you very much for your time.
--
Sylvain "Gugli" Guglielmi
