Defect #4497
Wrong info about API key when generated on-the-fly
Status: | Closed | Start date: | 2009-12-28 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 100% | |
Category: | UI | |||
Target version: | 0.9.0 | |||
Resolution: | Fixed | Affected version: |
Description
I just updated one installation to current trunk, and the /my/account
page displays "Missing an API access key" although it gets generated and shown if one clicks on the "show" Link. Reloading the page fixes this. I suppose the user-object passed to the view to make the decision to display "Missing an API access key" or something else is stale and doesn't yet have the info that there in fact is an API key.
Associated revisions
Create and assign the api token so the current instance can access it. (#4497)
History
#1
Updated by Eric Davis over 12 years ago
- Status changed from New to Closed
- Target version set to 0.9.0
- % Done changed from 0 to 100
- Resolution set to Fixed