Skip to content

Support checking the category chain for upcoming events #3449

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

Closed
ThiefMaster opened this issue Jul 5, 2018 · 0 comments · Fixed by #3459
Closed

Support checking the category chain for upcoming events #3449

ThiefMaster opened this issue Jul 5, 2018 · 0 comments · Fixed by #3459

Comments

@ThiefMaster
Copy link
Member

ThiefMaster commented Jul 5, 2018

This should be optional since the performance is better for a direct check.

Could be done using a new entry type "Category & Subcategories" in the upcoming events config which then checks using is_visible_in instead of just the category_id

errikos pushed a commit to errikos/indico that referenced this issue Jul 11, 2018
- Add a "Category & Subcategories" entry option.
- This resolves indico#3449.
errikos pushed a commit to errikos/indico that referenced this issue Jul 12, 2018
- Add a "Category & Subcategories" entry option.
- This resolves indico#3449.
errikos pushed a commit to errikos/indico that referenced this issue Jul 12, 2018
- Add a "Category & Subcategories" entry option.
- This resolves indico#3449.
ThiefMaster pushed a commit to errikos/indico that referenced this issue Jul 24, 2018
- Add a "Category & Subcategories" entry option.
- This resolves indico#3449.
ThiefMaster pushed a commit to errikos/indico that referenced this issue May 7, 2019
- Add a "Category & Subcategories" entry option.
- This resolves indico#3449.
ThiefMaster pushed a commit that referenced this issue May 7, 2019
- Add a "Category & Subcategories" entry option.
- This resolves #3449.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants