reset_text_filters_cache(true);
events_get_handlers('reset');
core_text::reset_caches();
- get_message_processors(false, true);
+ get_message_processors(false, true, true);
filter_manager::reset_caches();
core_filetypes::reset_caches();
*
* @param bool $ready only return ready-to-use processors
* @param bool $reset Reset list of message processors (used in unit tests)
+ * @param bool $resetonly Just reset, then exit
* @return mixed $processors array of objects containing information on message processors
*/
-function get_message_processors($ready = false, $reset = false) {
+function get_message_processors($ready = false, $reset = false, $resetonly = false) {
global $DB, $CFG;
static $processors;
if ($reset) {
$processors = array();
+
+ if ($resetonly) {
+ return $processors;
+ }
}
if (empty($processors)) {
This files describes API changes in /message/ messaging system,
information provided here is intended especially for developers.
+=== 3.1 ===
+* get_message_processors accepts an addition parameter for testing, which will just reset processor and exit.
+
=== 2.9 ===
* Renderer method \core_message_renderer::manage_messagingoptions now accepts a user id parameter as well.