Same here, on line 58 and 67. I have deactivated it for now.
wpms3.01 + bp1.2.5.2
@intimez @dubya1337 You can go back to Version 1.7.6.2 and you won’t have that issue. Or you can just edit this line:
$this->pag_per_page = get_option(‘bp_points_logs_per_page_cp_bp’);
to this instead
$this->pag_per_page = ’20′;
Change 20 to whatever number you set per page in the admin
@hnla @thekmen I have it just pulling the number from a field in the admin screen. Any ideas to fix this issue?
I’ll set up a WPMU test site and see if I can fix this for good.
@xberserker Tried that. Edited line 31 of bp-cubepoint-templatetags.php to: `$this->pag_per_page = ‘20?;` Now I get the following as soon as I activate: “Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in /home/***edited***/***edited***/wp-content/plugins/cubepoints-buddypress-integration/includes/bp-cubepoint-templatetags.php on line 56″
you forgot the extra ‘ should be this:
`$this->pag_per_page = ’20′;`
I installed a WPMU 2.9.2 and installed buddypress/cubepoints/buddypress-cubepoint and I’m not able to recreate that error yet.. strange.
Funny thought this issue was resolved, at any rate installed new versions recently on WP3.0.1 BP 1.2.5.2 and all was fine
For those with the issue, try replacing your bp-cubepoint-templatetags.php file with this and see if it fixes it and report back.
http://pastebin.com/EAmp3s2m
@xberserker That was a typo, I’m prety sure it was correct in the file edit… Anyways, your updated file resolved the issue for me.
Thanks for the help. Keep up the good work.
Cheers!
@dubya1337 Just to be clear you copied this entire code chunk
http://pastebin.com/EAmp3s2m
into your bp-cubepoint-templatetags.php file and your error free? 
Just wanted to double check before I commit a new update tonight when I get home from work.
@xberserker Um… no.
The problem is solved for the main site, but sub blogs still get the same 2 errors as before 
@dubya1337 I haven’t worked with WPMU much so is there a copy of the plugin on each blog? Or does it all point to the same plugin?
On your sub installs & main install do you have a value in the logs per page field in the admin?
@xberserker
I stand corrected. The problem is soved. I had another problematic plugin that was causing a similar error. At first glance, I thought it was your plugin, but I stand corrected. Sorry about that.
Your updated file did fix the problem.
WPMS (as it is being called since 3.0) does things a little differently than regular single site WP. I’m not really qualified to advise you an it as I am just leaning myself.
I used your code update and it fixed the issue for me as well.
@dubya1337 @bmtrnavsky
Great! Thanks for getting back to me about it. I’ll update the plugin in the next day or so. But hopefully tonight..
[edit] Version 1.7.6.4 should be up in about 15 mins.
@xberserker
Upgraded to Version 1.7.6.4 this morning… no problems and everything is working great.
Cheers!
