Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.

Vanilla & Wordpress integration issue

edited December 2006 in Vanilla 1.0 Help
Hello I've followed Mark's excellent documentation on the swell blog for integrating Vanialla & WP. On my test site it is working wonderfully. However, one small issue. If you decide to allow logins only from WP, and delete the people.php as suggested, when in vanilla, signing out attempts to redirect to the people.php, throwing up a page not found error. Just wondered if this sign out should now be redirected to the WP logout? And how to do this. thanks ps. Hope this is the write place to post

Comments

  • If you add the lines: $Configuration['SIGNIN_URL'] = 'people.php'; $Configuration['SIGNOUT_URL'] = 'people.php?PostBackAction=SignOutNow'; to your conf/settings.php file with the correct values in there it should do the trick.
  • Wow, that was a quick reply! Many thanks Minesweeper - worked great.
  • edited September 2006
    Hello again Been testing further and found a potential bug in the integration. The last visit count does not update. As a consequence I believe the Notify 0.2 extension doesn't send out emails. (I've checked that vanilla does send out other emails) I haven't tested things fully yet, but it's a real deal-breaker at the moment, as other wise the WP & Vanilla integration is a beauty If Mark or anyone else has time, it would be really appreciated if this could be fixed thanks
  • MarkMark Vanilla Staff
    If you use the Vanilla login instead of the wordpress one, the last visit will update properly.

    I don't know how to create addons for wordpress, but I'd hope they have the capability of allowing you to alter a query and update a field on-sign-in. We'd need a WP developer to help out if you want to keep using the WP login.
  • Thanks for the info Mark. I may post on the WP forum about this, as there's been some interest since you wrote the guide. Also, in case you didn't see this, there was positive write up of Vanilla and WP integration http://bloghelper.is-there.net/integrating-a-forum-with-wordpress/
  • MarkMark Vanilla Staff
    Interesting - thanks for the link :)
  • edited September 2006
    Hello

    Sorry, but I'm back again with a small issue with the integration.

    I've set things up where a new user is created, and sign in is done via vanilla now

    When I delete a user in wordpress, it correctly gets deleted in vanilla. (Not sure if this has anything to do with the issue below though).
    When a new user applies for registration, everything seems ok.
    But when admin tries to login after, I get this 'error' (displayed twice) above the you have successfully signed in message.

    Notice: Undefined variable: CookiePath in /home/asylum10/public_html/site/discuss/library/People/People.Class.WordpressAuthenticator.php on line 34

    Notice: Undefined variable: SiteCookiePath in /home/asylum10/public_html/site/discuss/library/People/People.Class.WordpressAuthenticator.php on line 34

    This message disappears after a couple of logins. But I've found that with the Notify0.2 extension, the new user isn't being sent any notification messages after testing, (visit count gets updated properly). I understand that I would need to contact the Notify0.2 author to debug this, but wondered if it's related to the integration/cookiepath message?

    I've installed the integration twice now and get the same issue

    thanks
  • edited October 2006
    I have used the full method (no people.php deleted and creatingthe wordpressAuthenticator plugin), and found a small issue:

    1. user created from vanilla are given the "contributor" privilage in wordpress, but they can't create anything in wordpress. Each time i try to login through wp-admin, it will tell me "You do not have sufficient permissions to access this page.

    2. user created from wordpress are well, creatd the way you want them to (subscriber, author, editor or admin) and they can login and post in vanilla.

    Number 1 is the issue here.... I wonder y...

    It would be great if Mark could get issue 1 working the same way as 2.
  • Poking around in my WP database, I'm guessing that the missing elements go in the mainusermeta table (wp_casual_mainusermeta in my case where casual is the dbname). The structure of the table is pretty simple name-value type stuff umeta_id user_id meta_key meta_value an example admin line looks like umeta_id 26 user_id 2 meta_key wp_casual_mainuser_level meta_value 10 the user level in meta_value is the role as in the WP Codex here http://codex.wordpress.org/Roles_and_Capabilities
  • I should add, that while I think it's pretty easy, I don't know how. And since I'm choosing to use WP to do all the login/logout/password/membership management crap, it's not high on my list to hack around with...
  • I'm having a problem with the Wordpress - Vanilla integration.

    I have added the 2 lines suggested above to my conf/settings.php file:
    If you add the lines:
    $Configuration['SIGNIN_URL'] = 'people.php';
    $Configuration['SIGNOUT_URL'] = 'people.php?PostBackAction=SignOutNow';
    to your conf/settings.php file with the correct values in there it should do the trick.
    My file:
    $Configuration['SIGNIN_URL'] = '/home/.hog/hometurf/hometurfmedia/blog/wp-login.php';
    $Configuration['SIGNOUT_URL'] = '/home/.hog/hometurf/hometurfmedia/blog/wp-login.php';

    I have also deleted the people.php, but I get a 404 when I try and access the forum...it is still looking for the people.php file

    I am still unable to login to Vanilla at all, after going through the instructions [twice] step by step. I can create a new user in Vanilla and then log into WordPress with the account, but there is no way to get access to Vanilla.

    I'm using WP 2.0.5 and Vanilla 1.0.3 and I noticed the directions are for Vanilla 1.0.1...has anything changed that would affect WordPress integration?

    Thanks
This discussion has been closed.