Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Sorry I am asking a question that has been asked before but in spite of reading all of them, I am still confused what to do. What exactly I have to do to implement the remember me feature in my website . Is calling the function "setcookie()" alone sufficient
If you are not using identity, then you may need to use cookies for that.
Keep a checkbox in login page for Remember me.
If the checkbox is checked, keep a cookie with some identifier which is in turn stored to the db.
Next time when anyone comes to the login page, check for this cookie identifer in the database and if it exists, login
automatically.
You can read more by doing a quick search on how to remember user using cookies.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm very new to rails and have very little experience with programming in general. I was given the project of creating a simple rails app that is able to check a users Instagram when given their User ID and Password. My question in general is how do I approach this? Where do I start and essentially how do I do this?
Well, you should never ask for the user's password for an external service (no sane user will give it to you). Instead use omniauth (omniauth-instagram, specifically) to get an access_token and then simply use the Instagram ruby gem (https://github.com/Instagram/instagram-ruby-gem) to get their timeline.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I would like to allow users to send me emails directly through my app, and am wondering if this is possible to do?
Your best and most simple way is to bring up the send email view (or even mailto:) with your app specific email to receive comments and requests on.
Another option is to design a web page that has a couple of fields for information and then hooking it up with PHP.
Just about anything works, it all depends on how you balance user experience and easy of implementation.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
What is the refsrc parameter in URLs for? There is a URL that is being circulated with our domain, but not sure if this is a safe thing.
Thank you
It will depend on the application/website receiving request with that parameter. I've seen that parameter name used to embed the current page for the link. (I believe I saw that on facebook links?)
In that way when the link is followed, the next app/web site is able to know where the link is coming from if the information is not in the HTTP headers due to redirections or similar situations.
I don't believe it's a standard though.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
My application is one page contract. I would like users to be able to sign the contract by clicking on a button. The contract is not a resource; it's plain HTML.
Every solution I have found so far relies on having a model that acts as votable. How can I implement a simple button that users may only click once, and display the number of users who have clicked it?
It's not possible to do this with static pages, at least not in a way that is clean and secure.
Think about it this way: every user is looking at a copy of the contract, which is being displayed to them on their browser (the client). If you want users to be able to cast votes that persist and be aware of votes cast by other users, then you need a server that keeps track of it centrally. That's why the solutions you have found so far rely on having a model, presumably backed with a table.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am definitely going to use an authentication scheme (Devise) with 3 roles: user, admin & sponsor. The question is: should I implement authentication right away or wait until I have my other models/views in place first?
I think it is usefull to do it as first, so you can easely integrate them in other models, eg. log that a user does something, you will also be able to set weather a user should have access to a specific controller.
Unless, you have a good reason to not do it...
A rather unexpected question, but you can safely create your authentication routine right away. In any project i create, authentication is definitely one of the first things i code, most times using Sorcery instead of Devise.
IMO it doesn't really matter, but why not do it earlier than later? It's pre-built, allows early testing (and testing it often), and allows access control needs to evolve organically rather than waiting until they all pile up and you have to do it all at once.