Custom Query (2152 matches)
Results (1663 - 1665 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1053 | fixed | Deletion in Model API | dread | dread |
| Description |
Currently in the API if you DELETE a package/group/user (and you have the required permissions) then it purges the object, when it should probably just set the state to deleted. There is no way to delete objects at the moment - changes to 'state' are ignored in the API. Do we need an alternative way to purge objects in the API? |
|||
| #560 | fixed | Deleted packages showing up in tag lists | kindly | rgrp |
| Description |
E.g. http://ckan.net/tag/lod contains musicbrainz_ (Musicbrainz) item (if you click you will get 403/login as deleted packages can only be seen by admins). Also suggested that these are showing up in the API (courtesy of Anja) Cost: 2h |
|||
| #1283 | fixed | Deleted packages shouldn't be searchable or browsable | dread | dread |
| Description |
A package in deleted state doesn't show to general users, but admins DO see them. The idea is that they can resurrect them if they want. But now we have the trash can that lists deleted packages. So we don't want admins to see the deleted packages anywhere else. (But an admin should still be able to READ and EDIT a deleted package, so if he clicks on it in the trash list he can see it to decide whether to resurrect and actually be able to change its state.) Same in the Web interface and API. This ticket ties in with #948 highlighting a package being deleted (when viewing or editing) and follows on from the introduction of the trash can #1076. |
|||
