Custom Query (2152 matches)
Results (961 - 963 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #999 | fixed | Factor out ckan.net theme changes to a separate theme repo and apply | rgrp | dread |
| Description |
Rather than polluting the ckan core code base on ckan.net install with ckan.net specific changes these adaptations should be moved out into a dedicated ckan.net theme. |
|||
| #1000 | fixed | Remove call timings code | kindly | rgrp |
| Description |
Not used and extra overhead. Very useful to strip this out and low cost. Places where it seems to be:
|
|||
| #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). |
|||
