From 2e585f0be74ef893181ee65b244f1e3dd60d6be0 Mon Sep 17 00:00:00 2001 From: reivilibre Date: Mon, 1 Nov 2021 15:46:26 +0000 Subject: deploy: 69ab3dddbc1595ee64c428df7a7f3c861a84b5b0 --- develop/modules/third_party_rules_callbacks.html | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'develop/modules/third_party_rules_callbacks.html') diff --git a/develop/modules/third_party_rules_callbacks.html b/develop/modules/third_party_rules_callbacks.html index 789e2e40ca..e0709fc882 100644 --- a/develop/modules/third_party_rules_callbacks.html +++ b/develop/modules/third_party_rules_callbacks.html @@ -215,6 +215,12 @@ servers are using the same module, with the same configuration.

event with new data by returning the new event's data as a dictionary. In order to do that, it is recommended the module calls event.get_dict() to get the current event as a dictionary, and modify the returned dictionary accordingly.

+

If check_event_allowed raises an exception, the module is assumed to have failed. +The event will not be accepted but is not treated as explicitly rejected, either. +An HTTP request causing the module check will likely result in a 500 Internal +Server Error.

+

When the boolean returned by the module is False, the event is rejected. +(Module developers should not use exceptions for rejection.)

Note that replacing the event only works for events sent by local users, not for events received over federation.

If multiple modules implement this callback, they will be considered in order. If a -- cgit 1.5.1