Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuring the App #28

Closed
gizmecano opened this issue Jul 5, 2013 · 3 comments
Closed

Configuring the App #28

gizmecano opened this issue Jul 5, 2013 · 3 comments

Comments

@gizmecano
Copy link

Greetings,

After creating the App, could you confirm there's nothing to change in the Request Settings block in the OAuth tab?

Indeed, I followed step by step your how-to, but nothing appears on my pages, so I wonder if I missed a step during the configuration (the debug option does not write anything at all...).

Thanks.

@paultibbetts
Copy link

The script works for me without changing any settings in the OAuth tab so this can be left on GET with https://api.twitter.com/1/ as the Request URI.

You should only need the Consumer Key, Consumer Secret, Access Token and Access Secret Token from the Twitter App.

If you open the console on the site, what error messages are you getting?

I once had no Tweets coming up because I left the trailing slash / from the end of the modpath I'd told the script to use, worth a quick check if everything else is set up correctly.

@gizmecano
Copy link
Author

Greetings,

Well, so the first point is established: the authentication configuration for the application seems reliable. I have the four data mentioned: my problem seems not be at this point.

Now, about the console, as I said before, even setting the debug option, I have absolutely no error nor warning about JavaScript.

Assuming that application is configured, I think I'll take everything from the beginning, step by step... If it works elsewhere, error seems to be from my doing... 😔

@gizmecano
Copy link
Author

Assuming the App configuration is correct according @ptibbetts, I close this issue and I have opened a new following issue (#29).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants