EZEE-2692: Buttons are in different order while user doesn't have Content/Publish policy #952
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
adamwojs
approved these changes
Apr 9, 2019
mikadamczyk
approved these changes
Apr 10, 2019
…tent/Publish policy
konradoboza
force-pushed
the
EZEE-2692-buttons_ordering
branch
from
70892ff
to
5b501e9
Compare
konradoboza
force-pushed
the
EZEE-2692-buttons_ordering
branch
from
5b501e9
to
a1c0da0
Compare
barbaragr
approved these changes
Apr 18, 2019
|
You can merge it up? |
|
Done. |
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.
Ordering of menu items in Admin UI relies now on orderNumber which is necessary for repositories which add new items to the dropdown.
Checklist:
$ composer fix-cs)