On Dashboard listings, use 'key' instead of 'slug' #7141
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bobdenotter
force-pushed
the
hotfix/key-vs-slug
branch
from
592563e
to
a74672c
Compare
GwendolenLynch
force-pushed
the
hotfix/key-vs-slug
branch
from
a74672c
to
6c1cbad
Compare
GwendolenLynch
approved these changes
Nov 3, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Additional fix for #7124, using 'key' instead of 'slug'. Using the CT from #7124, you'd get this on the dashboard:
In the listings, we pass in the permissions, using
context.permissions[contenttype.slug], but this should use the 'key' instead.