이 플러그인은 최근 3개의 주요 워드프레스 출시와 시험 되지 않았습니다. 워드프레스의 좀 더 최근 버전으로 이용할 때 더 이상 관리되지 않고 지원되지 않고 호환성 문제가 있을 수 있습니다.

LH Private BuddyPress

설명

Protect your BuddyPress Installation from strangers. Only registered users will be allowed to view view directory pages, activity and profile pages. Users attempting to view blog content via RSS are also authenticated via HTTP Auth.

This plugin is inspired by the Private Buddypress plugin by Dennis Morhardt. I rewrote it to provide a solution that followed the WordPress coding stndards and the decisions rather than options philosophy. I deploy this on my own multisite environment where I don’t want public profiles, activity or members directories (and where I don’t want site admins changing this).

Like this plugin? Please consider leaving a 5-star review.

Love this plugin or want to help the LocalHero Project? Please consider making a donation.

설치

Use the automatic plugin installation in the backand or install the plugin manuell:

  1. Upload ‘lh-private-buddypress’ to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress

FAQ

Can I change the URL where non-loggedin users are being redirected?

Yes, currently you need to write a filter function in your functions.php or site specific plugin.

function redirect_nonloggedin_users($current_uri, $redirect_to) {
    // Redirect users to the homepage
    return get_option('siteurl') . '/?from=' . $redirect_to;
}

add_filter('lh_private_buddypress_redirect_login_page', 'redirect_nonloggedin_users', 10, 2);

Are there other actions or filters?

In LH Private BuddyPress are 4 existing filters:

  • lh_private_buddypress_is_buddypress_feed: Boolean value if the current page is a BuddyPress feed
  • lh_private_buddypress_redirect_to_after_login: Called URI from where the users came from
  • lh_private_buddypress_display_login_message: Customise the message when vistors try to access a private component
  • lh_private_buddypress_redirect_login_page: URI where nonloggedin users are being redirected
  • lh_private_buddypress_login_required_check: Boolean value if for the current page a login is needed

What components are made private?

Only the members directory, user profile, and activity pages. These can only be visited by logged in users. All other components are still public.

Why this set up?

This is primarily for organisations, they usually want a public presence but may not want to disclose membership details to non members.

What if something does not work?

LH Private Buddypress, and all https://lhero.org plugins are made to WordPress standards. Therefore they should work with all well coded plugins and themes. However not all plugins and themes are well coded (and this includes many popular ones).

If something does not work properly, firstly deactivate ALL other plugins (except Buddypress and this on) and switch to one of the themes that come with core, e.g. twentyfifeen, twentysixteen etc.

If the problem persists please leave a post in the support forum: https://wordpress.org/support/plugin/lh-private-buddypress/. I look there regularly and resolve most queries.

What if I need a feature that is not in the plugin?

Please contact me for custom work and enhancements here: https://shawfactor.com/contact/

후기

2021년 7월 30일 답글 1개
Just what I needed, very simple to use.
2018년 1월 18일
Was very happy to find this! We have a site which we simply can’t have nosy visitors trolling. I had some issues getting plugin to work (because of bad code in existing plugins), but the author was very prompt and help at creating a solution. Way to go!
2018년 1월 17일
Works exactly as expected. I hope this plugin continues to receive compatibility checks/updates for future versions of Wordpress.
2016년 11월 30일
Hello, It is really working. Thank you this excellent plugin 🙂 Best Regards
모든 5 평가 읽기

기여자 & 개발자

“LH Private BuddyPress”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

기여자

자국어로 “LH Private BuddyPress”(을)를 번역하세요.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록RSS로 구독하세요.

변경이력

1.00 November 02, 2016
* First release

1.01 November 04, 2016
* More documentation

1.02 March 24, 2017
* Fixed very minor error in php strict error reporting

1.03 March 24, 2017
* Nest bp_init

1.04 March 30, 2017
* More explicit variable check

1.05 May 10, 2017
* Another explicit variable check

1.06 July 26, 2017
* Added class check

1.07 December 23, 2017
* Made translation ready

1.08 January 17, 2018
* Singleton and did_action

1.09 March 05, 2019
* Minor changes and improvements

1.10 April 04, 2019
* Better Authorisation handling

1.11 May 16, 2019
* Prevent direct access

1.12 July 29, 2022
* code fromatting