Not signed in (Sign In)

Categories

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

Help keep Vanilla free:
Welcome Guest!
Want to take part in these discussions? If you have an account, sign in now.
If you don't have an account, apply for one now.

Add-ons: WordPressFullName

Bottom of Page

1 to 4 of 4

  1.  
    • CommentAuthorjcwatson11
    • CommentTimeJun 21st 2008 edited
     # 1
    This extension populates Vanilla's $User->FullName field with WordPress' display_name field. Since Vanilla's FullName field is a virtual field constructed from Vanilla's FirstName and LastName fields separately (found in the user table).

    This extension will only benefit users who have successfully integrated Vanilla into WordPress using the WordPress2.5 Bridge. You can also look at the forum thread discussing common difficulties integrating the WordPress2.5 Bridge.

    This extension effectively allows theme developers to use Vanilla's native FullName field with confidence, knowing that even though the user's account was created in WordPress, the user's full name will appear where appropriate throughout Vanilla.

    It is recommended to use this extension in conjunction with the NamedVanilla2_WordPress theme, though creating your own theme with references to FullName is an obvious alternative. For notes on how this extension was developed, see the Vanilla form thread that preceded this extension.

    This extension and the NamedVanilla2_WordPress theme are sponsored by Avnet

    Change Log:

    0.1 - Original extension.
    0.2 - Included readme.txt file as recommended by the Add-on Guidelines.
  2.  # 2
    Uploaded version 0.2 of WordPressFullName.
    • CommentAuthorcircuit
    • CommentTimeJun 22nd 2008
     # 3
    what happens if the user updates their full name via the vanilla admin interface? (i'm still on wp 2.2.3 so i haven't tried this extension yet - i'm just curious)
    • CommentAuthorjcwatson11
    • CommentTimeJun 23rd 2008
     # 4
    Hi Circuit,

    I believe you would need the latest version of WordPress for this to work. But to answer your question:

    Nothing at this point. The extension is intended to make WordPress' display_name appear in place of any FullName info that Vanilla would store. It is probably a better idea, though, to redirect the user to the WordPress profile editor page instead of using Vanilla's profile editor page. An automatic redirect is probably out of the scope of this extension, since redirecting pages would be difficult to do as part of an extension to my knowledge.

    In reference to a similar solution, we are currently redirecting Vanilla's people.php to the WordPress login screen using the following code.

    if((isset($_REQUEST['PostBackAction']) && $_REQUEST['PostBackAction']=='SignOutNow')) {
    header('Location: ../wp-login.php?action=logout');
    exit;
    }
    if((isset($_REQUEST['ReturnUrl']) && $_REQUEST['ReturnUrl'])) {
    header('Location: ../wp-admin');
    exit;
    }


    Explanation of Code:

    The first 'if' checks to see if we are signing out. If so, it redirects the user to wordpress' logout action.

    The second 'if' checks to see if we are logging in. If so, it redirects th euser to wordpress' login page. It is interesting to note that an 'else' is not appropriate after the first if because there appear to be cases where people.php is called other than just login and logout.

    This code is placed at the top of people.php in our Vanilla 1.1.4 and works wonderfully for avoiding use of the Vanilla login page. This is especially important in our case, since we are using the WordPress LDAP authentication extension. To my knowledge, Vanilla doesn't have LDAP authentication yet, so this redirect is necessary.

1 to 4 of 4

  1.  
Add your comments
    Username Password
  • Format comments as
 
Back to Discussions Top of Page