Custom Query (2152 matches)
Results (1636 - 1638 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2940 | fixed | Edit different resources from edit dataset pag | johnmartin | johnmartin |
Description |
We need a nice way to be able to get to editing the different resources that are associated to a dataset. |
|||
#2941 | fixed | Add follower support back into CKAN 2.0 | johnmartin | johnmartin |
Description |
Add the views and functionality of following users and groups into 2.0 |
|||
#2950 | fixed | paster command to minify javascript and css | icmurray | |
Description |
With the latest template, css and js changes in 2.0, there are a number of things that need preparation prior to a production deployment. One of these is:
This ticket is to:
## Background Currently, minification works seamlessly without the need for any preparation when CKAN is started in a development setup. But on a production site, the webserver will (almost certainly) not have write-access to the directories that will contain the minified files. And so the minification will fail, and the site will end up serving the un-minified media, or even *old* minified media. One way around this would be to allow webserver write access to the directory its serving out of. But this is not generally considered good practice. Another method would be to distribute the minified files with CKAN. This ticket describes how to do this without causing a lot of noise in the commit history of the repo. The auto-minifcation occurs when importing ckan/lib/fanstatic_resources.py. ## Changing the process slightly The reason for moving away from auto-minifying files at start-up, to minifying files when running a paster command is:
|