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

Activity stream actions not overridable #4684

Open
amercader opened this issue Mar 14, 2019 · 1 comment
Open

Activity stream actions not overridable #4684

amercader opened this issue Mar 14, 2019 · 1 comment
Assignees

Comments

@amercader
Copy link
Member

Some calls to action functions in action/get.py call the functions directly instead of using get_action, meaning they can't be overridden from extensions.

@amercader amercader self-assigned this Mar 14, 2019
@amercader
Copy link
Member Author

Just noticed that after #4627 this is no longer relevant in master. I'll target 2.8 for this.

amercader added a commit that referenced this issue Mar 14, 2019
Otherwise they can not be overridden
wardi added a commit that referenced this issue Mar 14, 2019
…tions

[#4684] Use get_action to call activity actions
smotornyuk pushed a commit that referenced this issue Jun 16, 2019
Otherwise they can not be overridden
amercader pushed a commit that referenced this issue Sep 4, 2019
This occurred because the docker/python:2 image switched from Debian stretch to buster this week.
Buster uses openjdk 11 instead of 8, but even with this CKAN was unable
to talk to Solr - maybe to do with AppArmor enabled in Buster. It was
just easiest to pin back to stretch.
wardi added a commit that referenced this issue Sep 5, 2019
smotornyuk pushed a commit that referenced this issue Mar 24, 2020
This occurred because the docker/python:2 image switched from Debian stretch to buster this week.
Buster uses openjdk 11 instead of 8, but even with this CKAN was unable
to talk to Solr - maybe to do with AppArmor enabled in Buster. It was
just easiest to pin back to stretch.
smotornyuk pushed a commit that referenced this issue Mar 24, 2020
This occurred because the docker/python:2 image switched from Debian stretch to buster this week.
Buster uses openjdk 11 instead of 8, but even with this CKAN was unable
to talk to Solr - maybe to do with AppArmor enabled in Buster. It was
just easiest to pin back to stretch.
fostermh pushed a commit to cioos-siooc/ckan that referenced this issue Sep 10, 2021
…-jdk

This occurred because the docker/python:2 image switched from Debian stretch to buster this week.
Buster uses openjdk 11 instead of 8, but even with this CKAN was unable
to talk to Solr - maybe to do with AppArmor enabled in Buster. It was
just easiest to pin back to stretch.
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

1 participant