http://localhost/ticket/1106 <p> Various bugs I've been encountering: </p> <ul><li>Autocomplete of tag names no longer works (no longer works on <a class="ext-link" href="http://ckan.net/"><span class="icon">​</span>http://ckan.net/</a>). Appears to be due to no longer have a routes for apiv2 (i'm seeing failing calls to: <a class="ext-link" href="http://ckan.net/apiv2/package/autocomplete?callback=callback&amp;incomplete=a"><span class="icon">​</span>http://ckan.net/apiv2/package/autocomplete?callback=callback&amp;incomplete=a</a>) </li><li>Incorrect url generated for API in page footer (e.g. <a class="ext-link" href="http://ckan.net/rest/get_api"><span class="icon">​</span>http://ckan.net/rest/get_api</a>) due to use of old 'rest' rather than new 'api' </li></ul><p> Latter issue was masked by existence of 'default' routes: </p> <pre class="wiki"> map.connect('/{controller}', action='index') map.connect('/:controller/{action}') map.connect('/{controller}/{action}/{id}') </pre><p> Having these is, I think, bad practice as it is better to be explicit and we should therefore remove asap. </p> <p> In addition I think we should be cautious about 'default' routes in core such as: </p> <pre class="wiki"> map.connect('/api/rest/:register', controller='api', action='list', conditions=dict(method=['GET']) ) </pre><p> 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). </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1106 Trac 0.12.3 rgrp Tue, 26 Apr 2011 16:07:49 GMT http://localhost/ticket/1106#comment:1 http://localhost/ticket/1106#comment:1 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> <p> fixed in branch:defect-1106-bugs-with-routing. </p> Ticket