Skip to content
This repository has been archived by the owner on Jul 13, 2018. It is now read-only.

Tweets not showing on the module #95

Open
thulibaby opened this issue Apr 28, 2015 · 6 comments
Open

Tweets not showing on the module #95

thulibaby opened this issue Apr 28, 2015 · 6 comments

Comments

@thulibaby
Copy link

Good day,

Can anyone please assist me, the module is just blank and not showing any tweets

@mbabker
Copy link
Member

mbabker commented Apr 28, 2015

  1. What version are you running? Anything before the current release (3.1.0) will not work due to external dependencies having gone away.

  2. Do you have caching enabled? If so, check your site's cache folder for files from the module. The one ending in a number should hold the user and timeline data for the user you specified (the one ending in 'bearer' is a cached copy of the authentication token).

  3. Enable your site's error reporting, if there are any PHP errors this will cause them to show up.

@greenlanegreb
Copy link

Hi, does this application still work please? I have followed the instructions and installed the 3.x version from the Joomla Extensions Directory. I am running Joomla 3.4.

Kind Regards,

greenlanegreb

@mbabker
Copy link
Member

mbabker commented Mar 1, 2016

Yes it still works.

@greenlanegreb
Copy link

Ahh I must have a made a mistake somewhere. I put the consumer key and consumer secret in the authentication section, selected token source = consumer key and as the remote URL I pasted https://api.twitter.com/1.1/statuses/home_timeline.json although i'm not sure if that last bit is wrong :-) Currently, I get "Due to an error, potentially a timed-out connection to Twitter, this user's tweets are unable to be displayed."

Thanks for the quick reply,

Kind Regards,

greenlanegreb.

@mbabker
Copy link
Member

mbabker commented Mar 1, 2016

The remote URL should be a URL that returns your authentication token if you're storing it somewhere remote. If you've got the Consumer Key set as the source it shouldn't be using that anyway.

Since it's a message that shows up for end users the message is really generic and right now there aren't any other logging capabilities in place to help debug. But basically you'd get that message for any type of connection related error (authentication, over the API limit, failing to connect in general).

@greenlanegreb
Copy link

Thanks for this :-)

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

No branches or pull requests

3 participants