If Kim or another xpert is around ...
I have an observer that was using a simple notifier generated in v137's page, advanced_search, header_php.php

But Kim's been in that file for V138, in between coffee's, and changed the notifiers in that header_php.php, and put the call that creates the advanced search results, in that file now.. so v137 / v138 has changed there..

NOTIFY_HEADER_END_ADVANCED_SEARCH_RESULTS has been invaded by NOTIFY_SEARCH_ORDERBY_STRING

138 header_php.php has
Code:
  $zco_notifier->notify('NOTIFY_SEARCH_ORDERBY_STRING', $listing_sql);
//then the product search listing is created/called
////then later, at end of file..
Code:
$zco_notifier->notify('NOTIFY_HEADER_END_ADVANCED_SEARCH_RESULTS', $keywords);
I was using the first notifier to add to the search sql, it worked.. but it doesn't in v138.., now I'm flummoxed..

If I use NOTIFY_SEARCH_ORDERBY_STRING instead in my observer, my observer update function still doesn't kick in, and also theres a parameter after that new notifier in the header_php/php, wot I don't know to do with

Sorry this is a bit technical

Basically my 137 observer class v1for 137 used NOTIFY_HEADER_END_ADVANCED_SEARCH_RESULTS
but now the same observer refuses to kick in, although the observer class is still instantiated correctly, the function update section in my observer class no longer works (i.e is not called), whichever notifier above, that I use

Yes I know I'm a dumbo, but I can't locate a simple 138 version of an observer class, the purpose of the extra 'new' parameter after the actual notifier 'constant name' in the header_php.php is unexplained.. and why does my observer class hibernate in 138.. where it worked in v137..