Yeah. The error message is fine (I guess it should mention âsso masterâ, but I knew right away). Itâs just that it wasnât what I expected, and itâs taken me forever to figure it out. (Not your fault.)
What Iâm trying to do now is have a function called at login. Iâm trying to get the Discourse username so that I can then do an old-school curl to an API call to add to the group.
That is the correct way to get the userâs Discourse id if it has been set. $user_id needs to be the WordPress userâs ID. If youâre getting an empty response, the user has not logged in via Discourse yet. Try making the call with a user you know has logged into WordPress from Discourse.
Yeah, writing to a log file is what I wanted to do, but it seems that the only way I have access to the log on this webhost is by getting it emailed to me.
My solution is pushing stuff to https://pipedream.com/ . Itâs quite painful, but better than anything else Iâve found today. My problem before is that I need to do something different to push an array to the pipedream webhook than I do for the integer that get_user_meta returned.
Well, it seems that if I do a curl within a wp_login action, it interferes with the SSO connection. (OOps, Iâm not passing the API key, but I donât think thatâs the problem.)
Is there maybe something that gets called immediately after SSO is complete?
Maybe
wpdc_sso_client_after_login_link
edit: I think that might do it. Now to see if I can add to group via user_id rather than username. . .
nope. Need to figure out how php will let me access user_nicename out of $user = wp_get_current_user(); Itâs right there.
Well, of course, itâs $discourse_username = $user->data->user_nicename;
I donât think that php had that -> syntax when I learned it in 1997.
But now, the user_nicename changes. Sometimes itâs correct, and sometimes itâs got a -2 appended. Iâm logging out and then clicking Login via your forum account in the same browser window. This doesnât seem right.
Youâre kind of in uncharted territory with this. Itâs going to be hard to develop it on a live site. Iâm not sure whatâs going on with the nice_name, but Iâm going to take a closer look at that tomorrow.
Yeah. Thatâs on me. Setting up a staging sites with SSO seemed like itâd be a bigger problem than fighting with what was already working. It was going to be simple. This is one more reason to finish my Ansible tooling to support WordPress.
Iâm a Discourse Sysadmin, dammit, not a WordPress developer!
Thanks. Unlike pretty much every other question Iâve had in this exchange, that does seem like a . Thanks for all of your help!
Yes, this is a bug. I can only reproduce it if a username is changed on Discourse after an account is created on WordPress. Iâll get this fixed by early next week.
By adding log statments to my development site. This should be an easy fix, but Iâd rather not push the change to WordPress before I test it out some more.
Sure you have a reasonable development environment. Like a real developer. That I understand (in spite of my not having such!) But even thinking to try usernames that had changed⌠I guess the 2 was the clue.
Hereâs a slightly different method to handle Paid Memberships Pro group sync. Pop this into your functions.php file. Expected behavior is add upon subscribe and remove upon cancellation. Thanks to @dfriestedt for sponsoring.
I am implementing the PMPro code above and am hung up on something. My understanding is that this code only fires when users buy subscription or cancel a subscription.
Is there a way that I can auto-sync users as they are created on Discourse? In my case, I have some users who are subscribers but donât have a Discourse accounts (will be created via SSO).
The add_user_to_discourse_groups function will create a Discourse user if it doesnât already exist. If that function is being called for your users, then you should be fine. Where you might run into problems will be for existing WordPress users who got their membership before the code was added to your site. If that is the case, you will probably need to add the users to Discourse groups through the SSO parameters that are passed to Discourse on login.
To pass additional SSO parameters with the WP Discourse plugin, you can hook into the 'wpdc_sso_params' filter. The parameter you need to use to add users to a Discourse group is called add_groups. You can use it with something like this:
add_filter( 'wpdc_sso_params', 'wpdc_custom_sso_params', 10, 2 );
function wpdc_custom_sso_params( $params, $user ) {
if ( /* some condition that returns true if groups should be added for the user */ ) {
$params['add_groups'] = 'comma,separated,group,names'; // Don't use spaces between names.
}
return $params;
}
This is one more reason to finish my Ansible tooling to support WordPress. 
. Thanks for all of your help!
! Howâd you manage to find it!? Nice work.
