number 2 is already a option in the settings in the acp look for this setting
PM sender
Insert the UID of the user who will be the sender of the PM. By default is set to 0 which is MyBB Engine, but you can change it to whatever you like.
(2013-05-03, 10:07 AM)WebDevandPhoto Wrote: [ -> ]1) Need a way for an Agree to terms process either before or after facebook sign in (assuming not previously signed in) during facebook registration process. I didn't notice any "you must agree to site terms anywhere". This EULA is crucial for every website service provider.
2) A way to pick a user to be the "MyBB Engine" replacement for giving the password PM.
3) A secure password generation option should be available to give users a strong password at the get go.
1) True indeed, didn't think about it. Added to my todo list.
2) Already possible:
https://github.com/Shade-/MyFacebook-Con...-pm-sender
3) This is the default behavior of MFC:
https://github.com/Shade-/MyFacebook-Connect#general
AH! That's why... I entered in username not UID for #2, ofc works
#3, I went to the link but am not understanding, the only bullet about password info is:
- You can notify a newly registered user with a PM containing his randomly generated password. You have full control on the subject, the sender and the message of the PM that you can edit from your Admin Control Panel
which doesn't tell me anything about how to enable strong password generation, I'm assuming I'm missing something?
#1 That would be perfect if you implement this! EULA is extremely important.
The generated password is already that strong. It's a 8 characters long string with random numbers, capital letters, lowercase letters and symbols.
Thank you for this excellent plugin!
I am however having a problem.
These are the steps to the problem
1) User logs in via facebook connect
2) User prompted to enter facebook login info
3) User logs into forum using facebook connect
4) User logs off of forum and facebook
5) User clicks facebook connect
6) Problem - Despite beings logged off of Facebook, user is automatically logged into forum as facebook user. User cannot get to facebook login screen again if they want to change accounts.
I am using the one click login. The only way I could find to fix this is by clearing the cache of the web browser.
(2013-05-04, 06:29 AM)jaa09 Wrote: [ -> ]I have an error, here's my forum url: http://www.camotesislandforum.com/ hope you help me..Thanks..
Sure. What's the problem? It seems like the plugin haven't been installed on your board yet.
(2013-05-04, 06:59 AM)orbitpdx Wrote: [ -> ]Thank you for this excellent plugin!
I am however having a problem.
These are the steps to the problem
1) User logs in via facebook connect
2) User prompted to enter facebook login info
3) User logs into forum using facebook connect
4) User logs off of forum and facebook
5) User clicks facebook connect
6) Problem - Despite beings logged off of Facebook, user is automatically logged into forum as facebook user. User cannot get to facebook login screen again if they want to change accounts.
I am using the one click login. The only way I could find to fix this is by clearing the cache of the web browser.
You're right. Thank you for reporting this! This problem is caused by the enhancements I've included in the last commit: to speed up the login process, if the user infos can be retrieved before prompting the login page then the user is directly logged in instead of send an unuseful request to the Facebook server. However, it seems like the Facebook API can obtain the user's data even if he has logged out: that's because the secure access token is stored in a PHP session in your browser's cookies and it's not deleted by Facebook when you log out.
I have to check whether if there's a reliable way to see if an user is logged out from Facebook.
----
Fixed in
https://github.com/Shade-/MyFacebook-Con...4220f360b1
Awesome, thanks for fixing the problem! I've now implemented this on my site and I will let you know if I ever see any bugs.
Thanks to
Senethic who reported this, I've just fixed a low risk SQL Injection vulnerability that would throw a SQL error in certain circumstances. Strange that nobody reported it yet as it was a quite important flaw.
It isn't worth to update the plugin to 1.0.3, but a new package has been submitted to the Mods Site just to prevent new downloads to be affected by this problem.
Download the new package from
GitHub in the meantime and simply overwrite old files to update.
Thanks for the update i've not faced a problem but then, no one has reported any problems to me either.