Skip to content
This repository has been archived by the owner on Nov 7, 2019. It is now read-only.

apps/organisation: Do not assume an organisation to be present in templatetag #986

Merged
merged 2 commits into from
Sep 18, 2019

Conversation

rmader
Copy link
Contributor

@rmader rmader commented Sep 18, 2019

    The templatetag was created during a cleanup of the previous 'partner' logic,
    which did not assume a partner to be present. Adapt the new logic to also not
    assume that.
    
    This one was tricky as the templatetag is loaded as part of the base-template,
    which again is loaded by the 404-template, which is loaded e.g. if there is
    no matching organisation for the query. The fact that the templatetag did not
    handle this let to a 500-error within the 404-error.

Copy link
Contributor

@MagdaN MagdaN left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

…platetag

The templatetag was created during a cleanup of the previous 'partner' logic,
which did not assume a partner to be present. Adapt the new logic to also not
assume that.

This one was tricky as the templatetag is loaded as part of the base-template,
which again is loaded by the 404-template, which is loaded e.g. if there is
no matching organisation for the query. The fact that the templatetag did not
handle this let to a 500-error within the 404-error.
@rmader rmader merged commit 1954d03 into master Sep 18, 2019
@rmader rmader deleted the rm-2019-09-fixes branch September 18, 2019 11:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants