Custom Query (2152 matches)
Results (994 - 996 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1001 | fixed | API should use normal user credentials if available | rgrp | rgrp |
| Description |
When using the API 'locally' i.e. from the CKAN instance (as would be the case with an ajax interface) the API, especially that allowing READ requests should use the normal user credentials if they are available prior to looking for an API key. The key change appears to be to change _get_user_for_apikey method in lib/base.py BaseController? to check the c.user attribute (may wish to rename as the name may now be a bit misleading ...). This is critical to incorporating any ajax editing into the frontend. As part of this ticket we should do a general consolidation of the identification system in lib/base.py so that both api_key and normal user auth lead to the same set of auth-related objects being available (suggest c.user and c.userobj and c.author). |
|||
| #1003 | fixed | CKAN Javascript library and demonstration web interface | rgrp | rgrp |
| Description |
A plain javascript library for interfacing with CKAN would be very useful (why? see below!). It would also be nice to have a pure html + javascript web interface to CKAN both for its own sake and to act as a demonstrator for the library. Why?
|
|||
| #1008 | fixed | eval() of user display name in template head | rgrp | pudo |
| Description |
We're currently setting the user preferences links via a javascript snippet that also evals the name. This should be removed as we're not displaying the user name any longer. We should also have page fragment caching in Genshi, which is not currently implmented. cf. http://api.rubyonrails.org/classes/ActionController/Caching/Fragments.html |
|||
