bp-help

@caboni
Not being rude but please do not add replies on this plugins support forum that has nothing to do with the scope of this plugin. Post on https://buddypress.org/support/ or https://bbpress.org/forums/ and bump your topic about once every 24 hours. Eventually you will get an answer but keep in mind both of those forums are made up of volunteers. If you need prompt attention then you may want to hire a developer. A little cash is a good incentive to get prompt help. You can post your job here: https://buddypress.org/support/forum/plugin-forums/bp-jobs-board/
and here: https://jobs.wordpress.net/
Make sure you leave your contact info as well as the budget to get the job done. Good luck!

@mramott
Not unless you plan on rewriting the code. This is above the scope of what I created this plugin to do and my time is limited so unless you would like to tinker around with the code and provide it here then I have no plans on adding this in the future. However if you can get it working you could fork the plugin or provide me the working code here and I will gladly credit you on development after it is tested. Since this is outside the scope of the functionality this plugin was created for then I am marking this as resolved but feel free to post back if you decide to add this functionality and would like to get involved in development. Thanks!

I will close this for now. Thank you for bringing the issue to my attention.

@anotheropus
I got this issue squared away. Matter of fact you raising the issue made me aware of a function I re-used in several plugins and I fixed them all because of you, so I owe you a big ole Thanks!

Obviously your using one of my other plugins so I am sorry your having this issue I will take care of this swiftly!

pdillon809
I am glad it worked for you and thank you for the great review!

@gilles66
Sorry I totally missed that you had already commented out what I told you to comment out in my above reply. I fixed the depreciated function call in version 1.2 so thank you for bringing it to my attention. I still need to fix the issue with the calls you listed above because I suppose I should not assume everyone that uses this plugin is going to have bbPress installed along side of BuddyPress. Thanks again!

@gilles66
In line 8 just comment out this:

|| bbp_is_single_topic()

Like this:

/*|| bbp_is_single_topic()*/

I will have this and the depreciated tag taken care of in the next update. Thanks for your patience and the heads up!

@gilles66
Also this will be fixed in the next update. But for now just follow the instructions I gave you above.

@gilles66
If you are not using sitewide forums just comment the below example part out on line 8 of private-bp-pages.php

/*|| bbp_is_single_forum()*/

Closing as the other plugin is now available!

Hi again @imath
I changed the function in the plugin with the function you listed above and I also removed the code I added to remove the error and I can confirm that it fixed the issue! Thank you again for the awesome plugin! Very handy indeed!

@pdillon809
The version I mentioned above is now available on the official WP Repo:
https://www.ads-software.com/plugins/private-bp-pages/

@magichew
The version I discussed is now available on the official WP Repository:
https://www.ads-software.com/plugins/private-bp-pages/

This plugin on github is the initial release and in my opinion it is the best option if you only want to lock down BuddyPress without locking down your WordPress posts and pages. It specifically targets BP and bbPress pages while leaving the others untouched! As it stands the version on github will probably remain the same even once transferred to the WP repo for a long time unless the template tags/conditionals start changing within the core and I have to make an adjustment to accommodate those changes. So basically you could upgrade when it is approved by the WP repo but it will still be the same code, it will just be the official WordPress version that lets you know there is nothing wrong with the plugin. With this plugin there will be fewer release cycles as I don’t anticipate many changes for some time. I chose to keep this a simple alternative for those that don’t need a FT.Knox security but allows non-BP pages to be public!