You said in the previous post that you are sharing the Community Builder.
Now, you say that the table slv000_comprofiler_plug_profilebook is empty.

Normally this table should be a link to the other one when you share the Community Builder and can not be empty.

So you have to check how you have create the slave site to have a specific table only for the slv000_comprofiler_plug_profilebook

You can check the table type when you go in JMS tools and select the slave site. After that click on the "table" tab to see how are defined the table.
If you have shared CB, all the table should have a link.

ahhh yes! got that part fixed now.... must have used installed from master instead of share upon creating the first slave
thanks for the hint!


however I still have a bit of a problem :
mod_cbpblatest meant to display the latest guestbook entries keeps displaying the no entry message. I cleared cache and checked the query which is using #__comprofiler_plug_profilebook

any chance you would know what else to check?

I don't know.
If you have a look in the module mod_cbpblatest, you will see that it query the #__comprofiler_plug_profilebook

Perhaps you could try debug this module and add a trace on the query executed to try understand why if does not reply the expected answer.

yes I checked the query before posting as well.

and I have tested the module on a session without JMS also and its working there just fine.

system debug on master looks like this:

Profile Information
Application afterLoad: 0.011 seconds, 0.59 MB
Application afterInitialise: 0.620 seconds, 3.37 MB
Application afterRoute: 0.722 seconds, 3.74 MB
Application afterDispatch: 1.250 seconds, 6.34 MB
Application afterRender: 3.186 seconds, 12.22 MB
Memory Usage
12853232
24 queries logged
Language Files Loaded
Untranslated Strings Diagnostic
None
Untranslated Strings Designer
None

OK but the most interesting trace would be to have the SQL query to allow you execute manuall and identify why you would have no records.

You should be able to compare the MySQL query results between the two cases.

As the table called is the same (linked), the result should be identical.

That will help you identify what in the MySQL query reult in 0 results.

The trace you provide here does not help in any maner.

You have to analyze the MySQL query itself and reproduce it in a PHPMyAdmin to understand the reason.

the query with system debug enabled:

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

running that query in phpmyadmin is returning a single result corresponding to the profile screenie above