$messageStack->add(...) in observer won't work

[Dave224]

mc12345678,
Some further clarification please...

The notes in includes/init_includes/init_observers.php refer to the naming convention of the class in includes/classes/observers/auto.xxxx.php as "zcObserver" + the camelcased xxxx string, and in includes/classes/class_base.php notes, the naming convention of the class method is "update" + camelcased xxxx string or just update. But I could also use the zc version below 1.5.3 method of freely naming the class zzzz in class file class.yyyy in includes/classes/observers with the method name of update, as long as the config.yyyy is present in includes/auto_loaders and it defines the class name as zzzz. Do I have this all correct?

Also, if two or more observers are triggered by the same notifier, in what order are the observers executed? DrByte said in a post referring to zc 1.5.1 that the order of instantiation was the order of execution. Is that still true for zc 1.5.5 and what is the order of instantiation? Unfortunately, I could not determine the order of instantiation from a quick look at class_base.php.

Thanks again for your help!

[Dave224]

Just wanted to correct the above post (correction in red)...

The notes in includes/init_includes/init_observers.php refer to the naming convention of the class in includes/classes/observers/auto.xxxx.php as "zcObserver" + the camelcased xxxx string, and in includes/classes/class_base.php notes, the naming convention of the class method is "update" + camelcased notifier string or just update. But I could also use the zc version below 1.5.3 method of freely naming the class zzzz in class file class.yyyy in includes/classes/observers with the method name of update, as long as the config.yyyy is present in includes/auto_loaders and it defines the class name as zzzz. Do I have this all correct?

[mc12345678]

Just wanted to correct the above post (correction in red)...

The notes in includes/init_includes/init_observers.php refer to the naming convention of the class in includes/classes/observers/auto.xxxx.php as "zcObserver" + the camelcased xxxx string, and in includes/classes/class_base.php notes, the naming convention of the class method is "update" + camelcased notifier string or just update. But I could also use the zc version below 1.5.3 method of freely naming the class zzzz in class file class.yyyy in includes/classes/observers with the method name of update, as long as the config.yyyy is present in includes/auto_loaders and it defines the class name as zzzz. Do I have this all correct?

To go slightly a step further and to be sure that x, y, z and the new w match up see the blue text edits below:

The notes in includes/init_includes/init_observers.php refer to the naming convention of the class in includes/classes/observers/auto.xxxx.php as "zcObserver" + the camelcased xxxx string, and in includes/classes/class_base.php notes, the naming convention of the class method is "update" + camelcased notifier string or just update (when more than one notifier is present then it may be necessary to detect which notifier is present to take only the specific action for the specific notifier). But I could also use the zc version below 1.5.3 method of freely naming the class zzzz in class file class.yyyy in includes/classes/observers with the method name of update (note that any other functions in this file pre-1.5.3 can be called from the standard update method), as long as the config.wwww.php file is present in includes/auto_loaders, identifies the stored location of the class as being in the observers directory and it defines the class name as zzzz. Do I have this all correct?