redsoulwarrior

It’ll go live tomorrow, but here’s an early preview for you – https://youtu.be/419vDvBxWPE

(Never sure whether links will work on these forums, sorry…)

Thank you for the offer, I truly appreciate it. The main point of the video is to showcase how easy it is to use; we just installed and activated the plugin and we didn’t see any more external calls afterwards, which is of course the main selling point and the core feature. So there’s really nothing that it currently lacks as far as I’m concerned.

I recorded yesterday and it will go live tomorrow. ??

We’ll publish a quick how to use tutorial on our YouTube channel this weekend and hope we can get a few more folks to download the plugin and see for themselves why it’s so great. ??

Thank you, I appreciate it!

Alright, thank you and I understand.
We’ll abandon using the plugin for the time being, but if we reconsider, I’ll let you know.

Hi,
pretty much, yes.
It appears to happen even if the same user has been the one doing all the edits.

We haven’t created any posts with the standard WP content editor, that’s not really an option if you’re “committed” to this theme I’m afraid (it is its biggest downside by far).

Thanks for the reply.

If the textdomain is “business-elite”, shouldn’t the child theme textdomain be identical? So your child theme code should be:

add_action( ‘after_setup_theme’, ‘my_theme_child_setup’ );
function my_theme_child_setup() {
load_child_theme_textdomain( ‘business-elite’, get_stylesheet_directory() . ‘/languages’ );
}

—

Hope that helps.

Ah, I’m super sorry for this. The problem could be backtracked to the theme that was working with a new feature (a visual editor). After saving in the visual editor, the custom fields were being deleted.

So it’s not your plugin (or it’s a combination of the theme (it’s “Divi” by elegant themes) and your plugin).

Thanks regardless! ??

I have now figured out that the problem is not the registration mail, but rather the registration itself. If users are using Hebrew characters to sign up for the page, they aren’t entered into the database (but somehow, the mail is still being sent).

We used a functions.php hack to allow for Hebrew characters for the username. Here is the code:

function sanitize_user_with_hebrew( $username, $raw_username, $strict ) {

	$username = $raw_username;
	$username = wp_strip_all_tags( $username );
	$username = remove_accents( $username );
	// Kill octets
	$username = preg_replace( '|%([a-fA-F0-9][a-fA-F0-9])|', '', $username );
	$username = preg_replace( '/&.+?;/', '', $username ); // Kill entities

	// If strict, reduce to ASCII for max portability.
	if ( $strict ) {
		$username = preg_replace( '|[^a-z0-9?-? _.\-@]|i', '', $username );
	}

	$username = trim( $username );
	// Consolidate contiguous whitespace
	$username = preg_replace( '|\s+|', ' ', $username );

	/**
	 * Filter a sanitized username string.
	 *
	 * @since 2.0.1
	 *
	 * @param string $username     Sanitized username.
	 * @param string $raw_username The username prior to sanitization.
	 * @param bool   $strict       Whether to limit the sanitization to specific characters. Default false.
	 */

	return $username;
}
add_filter( 'sanitize_user', 'sanitize_user_with_hebrew', 10, 3 );

Is there a way for you to tell us how to change this bit of coding to allow for Hebrew characters during sign-up?

Thanks.

I’m no longer sure it was a problem in the plug-in rather than Divi’s lack of support for buddypress. There are no buddypress templates that are coming together with the theme, so many things aren’t exactly working depending on the browser (Firefox tends to automatically fix a lot of the erros that are getting thrown; with Chrome or Safari, you might not be able to “like” a post, reply to a message, etc.).

I can try the plug-in again once I’m done setting up all the necessary templating files for Divi.

The plug-in was pretty much displaying the log-in in the way I wanted it to (I would have changed it a bit with css), but it wasn’t possible to log in. Either it was a conflict with the theme or it was because of Divi’s lack of buddypress support.

If you need help with the German translations, don’t hesitate to reach out.

Thanks again. I’ll rate the plug-in (5 stars obviously), it does its job and the support is one of the best I’ve ever seen.

Oh, my, I had no idea it would be this stressful to change that. I’m sorry for causing you so much hassle, but I do appreciate your effort!

Thanks Evan!

Hi, did you get it to work?

I’m using Divi as well and while it was opening a modal, it didn’t provide the functionality I needed / it simply didn’t work. I’ve written to their support and hope that they can make it work, the plug-in seems to do a pretty good job on most other pages I’ve seen it in use.

The easiest way to deal with this problem is creating a child theme and overriding the header.php.

In it, replace:

<title><?php elegant_titles(); ?></title>

with

<title><?php wp_title(); ?></title>

Hope that helps.
There are other ways; I’m currently sitting on an override for the “elegant_titles” function and try to implement the buddypress functionality. It’s not working too smoothly yet, but I’m somewhat confident I’ll get there. ??

Thanks for forwarding me there. Weird that if you click on “Support” on the info page for Guided Transfer, they forward you right here…