www programming

Just an update to say I eventually gave up with Profile Builder and switched back to Simple Wordpress Membership for the frontend membership solution. It's free and works fine with W3all.

It has a few weaknesses which I was able to get around. On WP multisites, it assigns new members to the Subscriber role (regardless of your settings).

To overcome the biggest issue - preventing Spam members from creating (inactive) accounts - I force users to validate their emails (via a form) which sends them a link to a hidden registration form.

[quote=axew3 post_id=5168 time=1614449174 user_id=48]
i see that the integration plugin has been disabled so i cannot test anymore.
[/quote]

That is strange. It is still network activated - I just ran another test.
This time...

I registered a new account.
Then I activated via email link.
Then I tried to login to Forum. Fail.
Then I login to WP. Success.
Then I logout and re-login. 'Wrong Username or Password'. :(

I tested into different sites and configurations, one was gulliver.it yesterday night, having same problem.
Now it has been resolved and any test i did worked ok.
I regret that it was not working for you and yes for my test into your site.
So i returned back to test again, but i see that the integration plugin has been disabled so i cannot test anymore.
Very strange anyway, should really work now.

I'm afraid it's the same old story from me.

I registered a new account.
Then I activated via email link. Success.
Then I login. Success.
Then I logout and re-login. 'Wrong Username or Password'. :evil:

Let's go!

I not resisted to:
download class.wp.w3all-phpbb.php from your site and apply the patch directly, after that i've test it successfully into another online multisite wordpress, and into ant my localhost tests.
[b]
The coming 2.4.4 will contain this fix [/b] as option

So i registered a new account.
Then i activated. Success.
Then i login. Success.
Then i logout and re-login. Success.
Then i logout and request new pass: success
Then i login with provided that arrive by email: success
then i logout and relogin: success.

Resolved in 3 lines of code finally. Very fast (performance cost 0: execute only when user onlogin, and only when user's pass do not match).
Will be added as option.
The hint will say +- this (in the hope that the resumed and expressed concept will be clear)

[quote]If a frontend plugin bypass the default password reset process, so that this do not let update the new WordPress password at same time into phpBB, force the user's password update into phpBB when user login in WordPress

Note: may activating this option, you'll have to allow user's logins as mandatory only into WordPress, or the user that try to login in phpBB, will fail until the phpBB password will not be updated, due to an explicit and successful login into WordPress

Activate this option if using front-end plugins to manage user's password reset processes, you note that after a password reset and then a first successful login, if the user logout then try to re-login, will get password mismatch

This option is may not required into default WordPress installations[/quote]

[quote]///////////
// Scenario: password mismatch after a successful reset, then succesful login, then logout and re-login. Password do not match.
// Problem: if a frontend plugin bypass default password reset process, so to do not let update the new wp password at same time into phpBB,
// force the password update into phpBB onlogin in wordpress. [/quote]

2.4.4 will be released on next hours and will contain this fix and all the rest

p.s this can only be an option. Due to the logic behind the problem, any fix i did in the past failed. This way will be ok for any frontend plugin that can now work his own way (It is not necessary to activate this option into a default wordpress multisite).

p.sss there is [b]test1[/b] user to be removed into your penny! Sorry i do not have login with the other admin user to remove him!

Nope, You forgot to remember me, but someone else into another post did, that the problem come out after first login, or i've not well read what you said, and for sure, i forgot that this is the problem: after a first login ..