Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

EZP-31310: Fixed editing for content with multiple locations #333

Merged
merged 1 commit into from
Feb 18, 2020

Conversation

mikadamczyk
Copy link
Contributor

@mikadamczyk mikadamczyk commented Feb 13, 2020

Question Answer
Tickets https://jira.ez.no/browse/EZP-31310
Bug fix? yes
New feature? no
BC breaks? no
Tests pass? yes/no
Doc needed? yes/no
Related to
License GPL-2.0

When the user wants to edit the content that has multiple locations and occurs checking if unpublished draft exists then we need to know in which location the user tries to do this. This is needed to prepare proper links to edit versions. We should do this when it is possible (when a user is on the location view). When the user wants to edit content from a dashboard then the location is unknown. Therefore ContentEditViewBuilder must not only check the main Location but also other possible locations to which a user may have access.

Checklist:

  • Coding standards ($ composer fix-cs)
  • Ready for Code Review

Copy link
Contributor

@webhdx webhdx left a comment

Choose a reason for hiding this comment

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

Please be aware you have to port this change to ezsystems/ezplatform-content-forms. You can git merge it since whole repoforms tree was commited there.

Copy link

@tomaszszopinski tomaszszopinski left a comment

Choose a reason for hiding this comment

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

QA Approved on eZ Platform EE v2.5.8 (patch) and on eZ Platform EE 2.5 with diff.

@lserwatka lserwatka merged commit 36a6e44 into 2.5 Feb 18, 2020
@lserwatka lserwatka deleted the EZP-31310 branch February 18, 2020 12:20
@lserwatka
Copy link
Member

Could you merge it up?

# for free to join this conversation on GitHub. Already have an account? # to comment
Development

Successfully merging this pull request may close these issues.

7 participants