Opened 18 years ago
Closed 18 years ago
#1543 closed defect (fixed)
Plugin doesn't create SlimTimer tasks
Reported by: | Michael Kruger | Owned by: | tst |
---|---|---|---|
Priority: | normal | Component: | TracSlimTimerPlugin |
Severity: | blocker | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
I've installed the plugin, and setup a trac / slimtimer user.
The plugin doesn't seem to be talking to slimtimer. I'm expecting a SlimTimer task to be created when I create a new ticket. Perhaps I'm not using it correctly?
I've tried creating new tickets & setting the SlimTimer ID to:
- the username setup thru the Trac Admin section,
- a SlimTimer email address, and
- 0,
but none of these create a SlimTimer ticket.
Also unexpected: when I enter the API key, the key disappears from the text box when I click the "Apply changes" button - is this expected behaviour?
Many thanks, mike
Attachments (0)
Change History (2)
comment:1 Changed 18 years ago by
Summary: | Plugin doesn't seem to be doing anything → Plugin doesn't create SlimTimer tasks |
---|
comment:2 Changed 18 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Existing code wasn't correctly saving the API key. Made the following changes to fix it. In admin_ui.py:
if req.method == 'POST':
#for option in ('api_key'): # self.config.set('slimtimer', option, req.args.get(option)) new_api_key = req.args.get('api_key') self.config.set('slimtimer', 'api_key', new_api_key) self.config.save() req.redirect(req.href.admin(cat, page))
Viewing the log shows the following lines: Trac[ticket_change] WARNING: Missing username or API key for SlimTimer login. Task ... will not be updated.
I'm guessing the API key isn't being stored properly. How can I test this?