Custom Query (2152 matches)
Results (1903 - 1905 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#172 | fixed | Build ckan documentation using sphinx and upload | rgrp | rgrp |
Description |
Use python sphinx to build documenation in ./doc and then upload it somewhere publicly accessible. NB: improving the documentation is another matter (as is integrating e.g. existing api docs). Upload location (these are docs for CKAN codebase/concept not the ckan service at ckan.net so good not to associate it too closely with ckan.net): |
|||
#1161 | duplicate | Build a simplified theme for PDEU | pudo | amercader |
Description |
We need to offer a strongly simplified version, read-only of CKAN under publicdata.eu, with a focus on its role as search engine instead of a data catalogue. This ticket relates to work on the PDEU theme only! |
|||
#1106 | fixed | Bugs related to routes arising from API refactor + removal of default routes | rgrp | rgrp |
Description |
Various bugs I've been encountering:
Latter issue was masked by existence of 'default' routes: map.connect('/{controller}', action='index') map.connect('/:controller/{action}') map.connect('/{controller}/{action}/{id}') Having these is, I think, bad practice as it is better to be explicit and we should therefore remove asap. In addition I think we should be cautious about 'default' routes in core such as: map.connect('/api/rest/:register', controller='api', action='list', conditions=dict(method=['GET']) ) As it makes it harder for extensions to introduce their own APIs (here one could perhaps add something at /api/rest/{my-object} but only by using before_map rather than after_map). |