Custom Query (2152 matches)
Results (658 - 660 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1784 | wontfix | Links to renamed objects break | seanh | seanh |
Description |
The HTML templates for some activity stream activities link to objects (packages, resources, etc.) by their names, e.g. /dataset/foo, but if the object has since been renamed then the link will be broken. Possible solutions are to use the object ID to find its current name at rendering time and link to that, or link to the object by ID rather than by name. Linking by ID is both simpler to implement and better. Links by ID are ugly, but they are permanent and don't break when an object is renamed. We should be using links by ID everywhere on CKAN, so that when third-party sites copy-paste our URLs and link to us, their links don't break later. Fixing this means fixing the dataset_link(), resource_link(), group_link() etc. functions in ckan/lib/helpers.py which will change the links everywhere in CKAN where those functions are used to link to objects (which should be everywhere where we link to an object). If we want to have nice looking by-name URLs and what them to be permanent, then we need to change CKAN so that objects cannot be renamed. |
|||
#1807 | fixed | Recently added/updated datasets for EC portal | seanh | seanh |
Description |
For EC Portal need a page (or HTML snippet embedded in the front page?) listing recently added or updated datasets.
|
|||
#1808 | fixed | Translation of content on dataset view pages | seanh | seanh |
Description |
All data is that is translatable should be translated when viewed. This includes tag names will be ID codes. When viewing a dataset page, look up the current language of the interface (ckan_lang or something in the environs) and display the string for the tag in that language. Related to the dataset view extension points for translation, recently added by kindly/=. |