Posted by Mike Sances on February 14, 2008 at 2:55pm
Jump to:
| Project: | Token authentication |
| Version: | 5.x-1.2 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I've installed and activated the module but can't figure out how to start using feeds with tokens. I'm assuming that once I activate the module my feed pages (like mysite.com/rss.xml or any additional feeds I specify in the token authentication settings) should have a token appended to the URL. However they display as normal. The readme file does not include any instructions on how to install or use once installed.
Comments
#1
I have the same problem: I have absolutly no idea on how to use this module. I couldn't find any documentation, and Google doesn't provide obvious results when searched.
#2
Go to your user profile, and click there on the "tokenauth" tab.
You'll find there the token that needs to be appended to any feed url from the site;
and also some basic links (e.g. for the default blog view) that can be used directly.
To use other feed urls than those provided directly on this page - keep a record of your token somewhere, and just paste this in at the end of any feed url from the site.
#3
OK, many thanks. That did the trick.
It should be added in a README or something, because it is not obvious.
#4
added
#5
Automatically closed -- issue fixed for two weeks with no activity.
#6
I keep getting permission denied messages on these URL's (removed http://domain.com for readibility):
?q=aggregator/sources/296&token=HKDJahfdks
?q=taxonomy/term/77?token=HKDJahfdks
?q=aggregator/sources/296/feed&token=HKDJahfdks
?q=taxonomy/term/77/feed?token=HKDJahfdks
The token-URLs that are suggested by default on the My Accont page in Drupal work fine for anonymous users.
The user that has this token, is full admin on the website with full privileges everywhere.
Are the URL's constructed properly? What is the difference between using & and ? (I see the token module suggests both variants)?
#7
#8
Perhaps you did not explicitly allow tokens on those pages? See admin/settings/tokenauth
#9
It's been over 2 years. I assume this is resolved either way.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.