Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cached versions of datasets don't appear in the resources list #35

Open
LukeTully opened this issue Mar 6, 2017 · 3 comments
Open

Cached versions of datasets don't appear in the resources list #35

LukeTully opened this issue Mar 6, 2017 · 3 comments

Comments

@LukeTully
Copy link

LukeTully commented Mar 6, 2017

CKAN: 2.6.1

I've set up archiver for production with supervisor and I'm running into 2 issues.

The first is that the 'cached' indicator is not present on the dataset page after running paster archiver update-test and then verifying that the cached datasets are in fact copied to their respective directories.

Secondly, supervisor doesn't seem to automatically process the datasets that are on the queue. update-test forces that backup successfully and I can test that it's working.

Are there any obvious supervisor setup steps I might be missing or that anyone has run into?
Are there any more robust examples of the config options that need to be in .ini?
The documentation is clear on the steps but I don't understand how strict the configuration options are, whether the specific ports/names are important or defaults that can be copied straight in after installing redis-server.

@LukeTully
Copy link
Author

Just now noticed the question in the README that tries to address this. Though it did help me correct some issues, it did not help in addressing the problem of the cached information showing up on the dataset page.

@LukeTully
Copy link
Author

LukeTully commented Mar 14, 2017

The problem here seems to have come from a conflict with ckanext-scheming. Both extensions write to the same block in the package template resource_read.html and scheming appears to take precedent in all cases. My solution, at least temporarily—because I'm not familiar with how the theme system logic works—is to amend the ckanext-scheming resource_read.html template to check for the same variables as in this module and render them. Could someone with more domain knowledge help provide some input on a better way I can approach this?

@TkTech
Copy link
Member

TkTech commented Mar 14, 2017

@wardi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants