-
I saw another request about if userpro can be integrated with this theme: http://themeforest.net/item/aruna-retina-content-sharing-gag-meme-theme/6291937 NOTE: THEME’S DEFAULT USERS ARE AUTHOR LIKE: ?author=1 and so on
I’ve been trying to get it to work I do have some success with avatar upload but if I register with userpro the theme doesn’t allow user to be created properly and also I would like to ingrate mostly the post counts and likes from the theme.
There’s also a conflict with the registration with userpro I can no longer register a user with the themes default form it just redirects me to the userpro form which would be fine except I can’t register with the userpro form either. It does however create the user but after that the site is not useable by that user everything is blank except the header. Thereafter I have to delete that user.
My goal is to seamlessly integrate userpro whereas I can still use the theme’s deafault posting, likes, post counts, and login (oh yeah theme’s default login doesn’t work anymore either with userpro redirects as well). I would like to use userpro for profile info, profile photo, basically all user profile data.
Thanks
This requires custom integration to replace theme’s login and specific functions by UserPro.
I knew that it will require custom integration I was asking so Can you point me in the right direction. Here’s the thing I can register with the theme’s default registration but can only login with userpro login. So there has to be a connection somewhere.
Here’s the error Catchable fatal error: Object of class WP_User could not be converted to string in /xxxxx/xxxx/public_html/xxxxxxx/wp-includes/formatting.php on line 1943
I’ve managed to get userpro to create the user in a similar way of the default registration in sends an email with user and pass like the default but when I try to login I get that error above which is:
/**
* Verifies that an email is valid.
*
* Does not grok i18n domains. Not RFC compliant.
*
* @since 0.71
*
* @param string $email Email address to verify.
* @param boolean $deprecated Deprecated.
* @return string|bool Either false or the valid email address.
*/
function is_email( $email, $deprecated = false ) {
if ( ! empty( $deprecated ) )
_deprecated_argument( __FUNCTION__, ‘3.0’ );// Test for the minimum length the email can be
if ( strlen( $email ) < 3 ) {
/**
* Filter whether an email address is valid.
*
* This filter is evaluated under several different contexts, such as ’email_too_short’,
* ’email_no_at’, ‘local_invalid_chars’, ‘domain_period_sequence’, ‘domain_period_limits’,
* ‘domain_no_periods’, ‘sub_hyphen_limits’, ‘sub_invalid_chars’, or no specific context.
*
* @since 2.8.0
*
* @param bool $is_email Whether the email address has passed the is_email() checks. Default false.
* @param string $email The email address being checked.
* @param string $message An explanatory message to the user.
* @param string $context Context under which the email was tested.
*/
return apply_filters( ‘is_email’, false, $email, ’email_too_short’ );
}Thanks
I read in my search it’s looking for the email string to be $email during registration if that helps.
You must be logged in to reply to this topic.