Custom Query (2152 matches)
Results (928 - 930 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#958 | duplicate | ui for new kind field | kindly | |
Description |
Ui for related new field in resource (#957) |
|||
#960 | fixed | Support non-ascii character in internal error messages | pudo | rgrp |
Description |
Just saw an error like the following which looks like it is to do with having a user object with non-ascii characters in it. Either get rid of 'cast' to str type here or do it in a unicode aware way. Should do this not just here but everywhere we can find in the code base. Module ckan.controllers.package:302 in edit << am_authz = self.authorizer.am_authorized(c, model.Action.EDIT, pkg) if not am_authz: abort(401, str(gettext('User %r not authorized to edit %s') % (c.user, id))) auth_for_change_state = self.authorizer.am_authorized(c, model.Action.CHANGE_STATE, pkg) >> abort(401, str(gettext('User %r not authorized to edit %s') % (c.user, id))) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 1: ordinal not in range(128) EstimateCost: 1h |
|||
#961 | fixed | [super] Refactoring of forms, validation and model synchronization | kindly | rgrp |
Description |
This is a meta-ticket to hold all of the work on refactoring forms, validation and model-synchronization in CKAN. ckan-dev thread: http://lists.okfn.org/pipermail/ckan-dev/2011-January/000180.html The IssueFrom #926: The current formalchemy setup conflates view, controller and model code in a way that makes it hard to debug and customise. From http://lists.okfn.org/pipermail/ckan-dev/2011-January/000181.html: ... FormAlchemy, in retrospect, was probably a mistake as it merges too much model/validation/form generation into one thing. At least 3 functions involved [in this area]:
Related Tickets
|