What I see in this query is that the FROM master_comprofiler_plug_profilebook seems correspond to your master.

When run from the slave, the expected result is a FROM with the slave table prefix.

thats correct. on the dummy slv000 is being used and on chrissy slv001. those queries do not return any result in phpmyadmin

while I do understand that the module cannot return a result on the slaves (the tables are empty) it should return the result on the master , shouldn't it? even adjusting the module's php file for master_comprofiler_plug_profilebook doesn't change anything.

So if you have the two MySQL queries, you have to try identify the element in the queries that make in fail on the slv001 and that is working on slv000.

Normally, as both tables have the same content (because this is a view), you have to try understand the field that make cause the "no result".

You can use your PHPMyAdmin to execute both queries and try change them to identify the origin of the issue

well its not quite like that

the query on the master table returns a result, those on the slv000 and slv001 do not

and mouse over the slv000 and the slv001 tables shows 'view (0 rows)'

I just figured what is causing the query not returning anything for the slave tables: its the

mode ='b'

haven't figured out yet how to adjust it though

well I figured how to adjust the query now:

mode appears to require being wrapped in backward quotes here so that the query reads:

SELECT posterid, userid, `mode` , postertitle, postercomment, date
FROM slv001_comprofiler_plug_profilebook
WHERE published =1
AND userid =63
AND `mode` = 'g'
ORDER BY date DESC
LIMIT 4

this way the query works for all master, slv000 and slv001 tables (in phpmyadmin)

however the module is still not displaying anything no matter where I enable it