then what is a generic redirect URL on Twitter plugin?
When I used the URL, I got a error message below. Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings.
So you can log in with Twitter, but you can’t tweet etc. All you can do is retrieve Twitter login details and list of Tweets.
The redirect you need to add is the page that your “logon with social network” button is on. Without the “debug” as it will get lost when it comes back.
I spoke too soon, email address does not get retrieved, and it’s impossible to assign it afterwards as it’s not in the Twitter’s plugin’s response @Bubble
Yeah I ran into the same problem with the email (while also still just not getting the login auth to work) and just nixed it from login possibilities altogether for now @cwmoss
So I did some digging thru their API docs and StackOverflow. The callback URL you should be using is the URL of where the “thing” is located. That “thing” being the URL of the page where your “Signup/Login” button is located.
I added three callback URLs because I have a “login”; “signup”; and “settings” pages where I have such button or “thing” located.
I tried both “Login” and “Settings” URL callbacks and they worked without a hitch.
I’m testing now the “Signup” call back will post results later today.
Ah yeah! That makes sense and is why I had issues.
If I remember correctly I have a ton of pages so I had to throw the login/signup in the reusable header and that made it impossible to add that specific pages callback to the list because they only allow 10 total url’s but my pages are dynamic
I like just having a dynamic login in the nav bar instead of a single page for it. Oh well