How can I manage users without user the Backpage Permission package?
Basically all users will be the same level. I tried creating a User crud and tying to the original User model but that doesnt seem to work.
Any thoughts?
Related
I have been struggling to figure out what is happening about my new BE user. I have created a back-end User and give the proper permission (News administration module only) and also the ns_news_comments.
I can create News content, edit, and so on... however when the news receives a new comment to approval the backend user cannot change the News anymore. If I change the BE to Admin, it will work fine. I have already granted permission to the entire root tree.
Any thoughts?
I am using the accounts-entry, accounts-ui, accounts-facebook packages and need to have the signup code feature for Facebook. Anyone successfully done this?
In it's simplest form, I just need a link (that I can dynamically generate) that will grant users access to my app. Then, on my homepage, I need a login button that will only allow those who have already gained access to my app in, and not allow those who don't have access. So basically a button that grants access to my FB "app" and a button that logs in only those who have access.
Create a new collection called "allowedUsers" or something. Add users to this collection who "click the button at a private link".
Then, on the Accounts.onCreateUser(func) callback, verify* that the user attempting to login using facebook exists inside the "allowedUsers" collection. If they don't, then just throw new Meteor.error(500, 'User isn't allowed to sign up through facebook') (an account is not created for the user in this instance).
See the documentation on Accounts.onCreateUser(func) for more details.
http://docs.meteor.com/#accounts_oncreateuser
*When I say verify, there are multiple ways to do this, but none are infallible to my knowledge. It would be up to you to determine if the person you added to your "allowedUsers" collection is truly the person signing up through facebook.
Is it possible to add a role on users after they register to my dotnetnuke site through facebook?
I'm using the out of the box version of the facebook login control located at DesktopModules\AuthenticationServices\Facebook\Login.ascx and after the login procedure is done I want to add a role to the created user.
Is this possible through settings? If not, is there a way to determine in code if the user is registered through facebook?
I don't believe this is possible in the standard FB provider for DNN. You likely would need to do this via the database, I would recommend looking at a user that you know was added through FB and see if you can see any differences in their profile from a regular user (likely in their username) and see if you can create a SQL trigger that handles that role addition.
How do you populate a Facebook Test User account with check-in data? I tried posting on the wall of the user with a Location entered in, but that did not seem to trigger a "check-in". Anyone run into this issue?
The only workaround I've found is to use a real user account.
Have you tried logging in as the user, using the email and password provided when you created the user?
I've only worked with photos, but I've had luck with using the normal user interface for these kinds of tasks.
Also, you have to be careful to keep using the same user. The access token expires, so you have to renew it with the same user ID. I was accidentally creating new users.
We have already launched an application, but we clearly see now, that we need publish to wall permission (our approach with not requiring this from user and basing on invites doesn't work well). Can we do it? How to make sure, that users will be instantly notified about the need of accepting new permissions, rather than having our application malfunction, if they don't have them yet?
Basically, it will allow current user to perform only the permission they granted. But there is a trick to solve the malfunctioning of app as permission is changed.
Always put the permission button as first step for the application. So that if user has already given all the permission to app, it will automatically redirected to next_step mentioned. If there is all/any permission added, it will ask only for updated permission to users.
It will make your app work with new as well as old users.