MoMan
03-28-2010, 08:10 PM
It looks like I've currently got a plugin on my forum that's breaking the the social groups 'mark read' functionality.
I.e the script http://www.pentaxforums.com/forums/group.php?do=markread&groupid=67&discussionid=241 is returning a blank page and doing nothing.
When I disabled all my plugins via vBulletin options, it started working again. However, after just disabling those add-ons that had hooks at group_*, it was still broken. Is there any smarter way to troubleshoot this than to manually disable all my plugins and then manually re-enable them until the functionality breaks? (I.e. have the script print out any errors - how is that done?)
Also, is there any easy way (i.e. via SQL query) to disable all my products so that all I have to do is start re-enabling them, rather than spending 15 minutes disabling them?
Thanks!
--------------- Added 1269825750 at 1269825750 ---------------
Found the problem; if you are using the Social Groups Mass-PM mod, see my post in that thread for a fix. That mod is buggy as hell it turns out, but if you implement all the fixes listed in that thread it should be good to go.
I.e the script http://www.pentaxforums.com/forums/group.php?do=markread&groupid=67&discussionid=241 is returning a blank page and doing nothing.
When I disabled all my plugins via vBulletin options, it started working again. However, after just disabling those add-ons that had hooks at group_*, it was still broken. Is there any smarter way to troubleshoot this than to manually disable all my plugins and then manually re-enable them until the functionality breaks? (I.e. have the script print out any errors - how is that done?)
Also, is there any easy way (i.e. via SQL query) to disable all my products so that all I have to do is start re-enabling them, rather than spending 15 minutes disabling them?
Thanks!
--------------- Added 1269825750 at 1269825750 ---------------
Found the problem; if you are using the Social Groups Mass-PM mod, see my post in that thread for a fix. That mod is buggy as hell it turns out, but if you implement all the fixes listed in that thread it should be good to go.