atmojones

I found the reason but I’m not sure why it makes sense. In the core file for the plugin there is:

function bp_registration_deny_access() {

	$user = new WP_User( get_current_user_id() );
	$private_network = (bool) get_option( 'bprwg_privacy_network' );

	if ( $private_network ) {

		if ( bp_registration_buddypress_allowed_areas() ) {
			return;
		}

		if ( bp_registration_bbpress_allowed_areas() ) {
			return;
		}

I used the filter in bp_registration_buddypress_allowed_areas() [which the code in my callback seems to be running now] to return false. Because it’s false it continues to execute an calls bp_registration_bbpress_allowed_areas() which returns true, and displays the message composition page. Once I used the filter in both functions it works. I feel like this is a bug, why wouldn’t you check bbpress and buddypress allowed areas in one function so they don’t both need to be addressed when overriding? Is it possible that plugins or custom code I am running is the cause of bbpress returning true? I’ll try to test on clean install later this week.

@blenderitalia

Do you use a bp-custom.php file in your site?

Sorry this took so long for me to get back too. I’ve had a lot of other deadlines to complete before revisiting bug fixes. I tried other transitions and still had an issue. Link to gif of issue using fade transition.

I’m using Google Chrome v53.0.2785.116 (64-bit) on iMac (27in, Mid 2011) running OS X El Capitan v10.11.6. Please let me know what other information I can provide to help resolve this.

I should also clarify that with my current setting the archive page works but the links it generates are to mysite.com/fossil/%title%/ for single posts. This does not work for me because title is not supported by my custom post type. so I need the links to use the post_id

I’m having this problem as well but I can’t seem to figure out how to get the edit box off the bottom of the screen.

I don’t follow what you mean when you say “The activity-meta was not in my activity-content div”. Could you explain what you mean by this and perhaps that will solve my problem.

Yep, it definitely reloads the whole page. This cause makes sense since it seemed pretty obvious “DOING_AJAX” wasn’t defined, which is a very overtly named variable. I’ll examine how to get this turned on so that I can fix pagination the proper way rather than altering bps-search.php. Thanks.

I am not a wordpress or buddypress developer, but I recently inherited a mess of a wordpress site to getting working again. One of the issues was pagination was not working on member page for bps search results.

I ended up editing the functions bps_set_cookie and bps_get_request in bps-search.php to solve my problem. I am 99% sure this is a terrible solution but it worked.

bps_set_cookie was setting the cookie bps_request to ” ” after the initial search result page because $_REQUEST[‘bp_profile_search’] was no longer being sent when clicking pagination links. Additionally bps_get_request was not retrieving the cookie because DOING_AJAX was not defined.

Andrea, I have a feeling that the actual problem is elsewhere, and the code I altered would be functioning properly if I fixed the actual issue. I’m guessing that DOING_AJAX should be getting defined while also passing the $_REQUEST [‘bp_profile_search’], any ideas on where I should be looking? Unfortunately I cannot give you access to code as it’s on our company servers.