Custom Query (2152 matches)
Results (1180 - 1182 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1798 | fixed | API search in non-q fields has exception for unicode characters | dread | |
Description |
You get an exception if you use the API to search packages and specify a non-ascii character in a field other than q. For example: http://catalogue.data.gov.uk/api/search/package?title=%E2%80%93 This "N-dash" (Unicode character 2013) causes this exception: Module ckan.controllers.api:460 in search << if ver in u'12': # Otherwise, put all unrecognised ones into the q parameter params = convert_legacy_parameters_to_solr(params) query = query_for(model.Package) results = query.run(params) >> params = convert_legacy_parameters_to_solr(params) Module ckan.lib.search.query:38 in convert_legacy_parameters_to_solr << for search_key in non_solr_params: value_obj = legacy_params[search_key] value = str(value_obj).replace('+', ' ') if search_key == 'all_fields': if value: >> value = str(value_obj).replace('+', ' ') UnicodeEncodeError: 'ascii' codec can't encode character u'\u2013' in position 30: ordinal not in range(128) This problem affects CKAN 1.5 and 1.5.1 only. |
|||
#1799 | fixed | To login as a different user or register, you need to logout first | dread | dread |
Description |
When you are logged in, you cannot login as a different user before first logging out. (This is a restricting in repoze.who, which gives priority to an existing recognised identity over another one you supply.) Yet, the CKAN login form appears when you try to do something you're not allowed to, even if you are logged in already. You login with a different identity and nothing happens - you remain as the first identity - this is incorrect. (It is also a little confusing to be sent to the log-in page, although we do have a flash message explaining, and you might want to relogin as a superuser if you can.) Whilst in this area, it would be worth fixing the problem for developers where you are logged in, do "paster db clean" and then try to log in - AuthTkt? recognises your old cookie but the User object doesn't exist, so you get an error logging in. In this instance we should tell people to log-out. |
|||
#1801 | fixed | No links to password reset | dread | |
Description |
You can reset your password (#1186) but you have to know the URI (/user/reset) - there is no link to this page! |