cubicweb: comparison server/hook.py

equal deleted inserted replaced

-:fef0b8214fcf
+:77ea3eed9946
 Hooks control
 ~~~~~~~~~~~~~
 It is sometimes convenient to explicitly enable or disable some hooks. For
-instance if you want to disable some integrity checking hook.  This can be
+instance if you want to disable some integrity checking hook. This can be
 controlled more finely through the `category` class attribute, which is a string
 giving a category name.  One can then uses the
-:class:`~cubicweb.server.session.hooks_control` context manager to explicitly
+:meth:`~cubicweb.server.session.Session.deny_all_hooks_but` and
-enable or disable some categories.
+:meth:`~cubicweb.server.session.Session.allow_all_hooks_but` context managers to
+explicitly enable or disable some categories.
-.. autoclass:: cubicweb.server.session.hooks_control
 The existing categories are:
 * ``security``, security checking hooks
 * ``email``, email address handling hooks
 * ``bookmark``, bookmark entities handling hooks
-Nothing precludes one to invent new categories and use the
+Nothing precludes one to invent new categories and use existing mechanisms to
-:class:`~cubicweb.server.session.hooks_control` context manager to
+filter them in or out.
-filter them in or out. Note that ending the transaction with commit()
-or rollback() will restore the hooks.
 Hooks specific predicates
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 .. autoclass:: cubicweb.server.hook.match_rtype