Users occasionally have some questions about Tweet Display Back. This FAQ is intended to answer questions about the type of data that can be accessed, versions of Joomla! supported, and various commonly asked questions.
Q Why do I receive a "This user has reached the maximum allowable queries against Twitter's API for the hour." message?
Twitter's API limits requests on the REST API (which is the API being used to retreive your tweets) to 150 per hour. With caching disabled, a request will be made with every site visit. You are encouraged to enable caching for the module (located under the advanced parameters), even with a one minute lifetime, to limit the number of requests.
Q What does Tweet Display Back do?
Tweet Display Back displays tweets on your Joomla! website from a user or list of your choosing, but only if the tweets are NOT protected.
Q Why are protected tweets not displayed?
Displaying protected tweets would require the use of Twitter's OAuth to log in the user and retrieve the protected tweet(s). Currently, OAuth is not implemented in the module.
Q What versions of Joomla! do you support?
Current, actively maintained versions of Joomla! will be supported, to include future versions once they are in the beta phase. At present, 1.5, and 2.5 are supported. Joomla! 1.6 and 1.7 were short term releases with a total of seven months of support, and as such, are no longer explicitly supported in this module. Although version specific support will have ended, this does not mean that the module will no longer work. This will mean that any bugs found specific to Joomla! 1.6 and 1.7 that are not present in Joomla! 1.5 or 2.5 will not be fixed. Additionally, the module will still be packaged and compatible with Joomla! 1.6 and 1.7, and future versions as they reach EOL, until new code is released that breaks backwards compatibility with non-supported versions.
Q Can other information be retrieved?
Yes, information such as user mentions and the home timeline (what you see when logged into twitter.com) can be pulled from Twitter's API feeds. Also, additional bits of data concerning the user and tweet are by default returned from Twitter but not processed with this module. Many of Twitter's API feeds require OAuth authentication to retreive additional information. OAuth is not implemented in this module at this point in time.
Q Can I request features, report bugs, or provide a translation?
Certainly! The links for these activities are on the About Tweet Display Back page. Feel free to contribute patches or pull requests to go with your report as well! Appropriate credit will be given if an idea you code is included.