Eric Nemchik

Seems to be working again. Thanks.

seems to be an outage https://www.cloudflarestatus.com/

Quick update:

I have a second site that was never upgraded to 1.17.2 (it is running 1.17.1). It is having the same issue (and showing line 161 in the debug log).

Based on this, I suspect the issue to be a cloudflare problem and maybe not related to the plugin, but I cannot say for certain.

Version 1.13.1 seems to have resolved the issue for me! Thanks again for your quick response!

Hi Elliot

Thanks for your quick response! I’ve updated to Version 1.13.0 but the issue does not seem to be resolved.

Additional context: The submit button is disabled on the comment form because I have that option enabled in the plugin settings, but comments cannot be submit because turnstile does not seem to appear and perform it’s check.

That’s great news! I’d still love to poke around if you do decide to post a git repository.

Here is what I have working btw:

	public function bp2wp_add_sync_options( $field ) {
        global $wpdb;
		$bp2wp_sync = false;
		if ($field) {
			$childs = $field->get_children();
			if (isset($childs) && $childs && count($childs) > 0 
				&& is_object($childs[0]) && $childs[0]->type == 'bp2wp_sync') {
				$bp2wp_sync = $childs[0]->name;
			}
        }
        $wpfields = $wpdb->get_results( "SELECT DISTINCT meta_key FROM {$wpdb->usermeta} ORDER BY meta_key" );
		?>

		<div class="postbox">
			<h2><?php _e( 'Sync to WordPress user field', 'bp2wp-full-sync' ); ?></h2>
			<div class="inside">
				<p class="description">
					<?php _e( 'Please select the WordPress user meta you want to sync with this BuddyPress field.', 'bp2wp-full-sync' ); ?>
				</p>
				<p>
					<label class="screen-reader-text" for="bp2wp_sync"><?php _e( 'Sync to WordPress user field', 'bp2wp-full-sync' ); ?></label>
					<select name="bp2wp_sync" id="bp2wp_sync" style="width: 90%">
						<option value="" <?php selected( $bp2wp_sync, '' ); ?>><?php _e( 'None', 'bp2wp-full-sync' ); ?></option>
						<?php foreach( $wpfields as $wpfield ) { ?>

							<option value="<?php echo $wpfield->meta_key; ?>"<?php selected( $bp2wp_sync, $wpfield->meta_key ); ?>><?php echo $wpfield->meta_key; ?></option>
						
						<?php } ?>
					</select>
				</p>
			</div>
		</div>
			
		<?php
	}

• This reply was modified 5 years, 4 months ago by Eric Nemchik.
• This reply was modified 5 years, 4 months ago by Eric Nemchik.

Do you happen to have a git repository for source control? I am considering contributing. I am looking into adding the ability to use any meta field rather than just the 5 predefined ones.

Also I followed your instructions to perform a conflict test and was unsuccessful. I was able to deactivate all plugins except Ultimate Members and switch to the Twenty Nineteen theme (I did not have 2015 installed at the time). And this did not resolve the issue. I did the conflict test as described and also tried using WordPress’s https://www.ads-software.com/plugins/health-check/ troubleshooting mode and neither method worked.

I tested the members directory on another site of mine and it worked without issue. The only real difference I can think of between the two setups is the one that is not working has https://www.ads-software.com/plugins/next-active-directory-integration/ installed. Like I mentioned above I did disable the NADI plugin for the conflict test and the users still exist in WP (and in the database) and further to that point there is a user account in the system that is not synced via the NADI plugin, and UM still does not display any members at all.

Here is a screenshot of my settings. https://i.imgur.com/e1Bfls1.png

I have tried adjusting various settings with no luck.

Sorry to be clear I’m not asking for ultimate members to add active directory support. The other plug-in I mentioned already does this using the standard WordPress login page.

The issue is having both active means using the ultimate members login page which for some reason doesn’t allow the active directory logins to work. Standard logins still work with both active. Using wp-login.php still works (allows active directory logins) with both active. It’s just the custom ultimate members login page that doesn’t allow active directory logins, only standard WordPress logins work (with both plug-ins active).

Awesome, thanks!

See you in 2 more years lol.

Awesome, I just updated and confirmed it works, thank you!

I noticed a PR on git https://github.com/Automattic/jetpack/pull/2776 didn’t make the cut (kind of too bad, I thought this looked really good).

So this got me to thinking, I’m having trouble with a site of mine ( https://kdash.keeforce.com/ ) ALWAYS showing the math challenge. We run this site on a Windows server (IIS) on our internal network and have it publicly available for external access, but it’s locked down with a membership plugin to only allow logged in users to access the content. Internally we have a domain controller handling DNS and it has a dns record for kdash.keeforce.com to provide our webserver’s internal network address. Externally we have our registrar handling the nameservers for our domain and it’s zone file is setup to point kdash.keeforce.com to our public static IP and our router is setup to handle providing a connection to our internal web server. I have also configured the protect module via /wp-admin/admin.php?page=jetpack&configure=protect to whitelist the following addresses;

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

Note that I actually entered them without the spaces around the dash, but when I click submit jetpack adds the spaces.
So the issue I’m having is that all of our visitors internally (from our 172.16.x.x addresses) are being shown the math challenge EVERY TIME we login, even though our range is whitelisted.

What gives?

/edit: I should note I have disabled the protection module recently because of this issue, and I have a google nocaptcha/recaptcha plugin in place.