EZP-30493: Fix cache not cleared on node visibility change #1359
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
andrerom
reviewed
Jun 28, 2018
|
Updated PR here @diaborn19, would you be able to move the changes either with the two commits or just one by you to 2017.12 branch? |
andrerom
approved these changes
Aug 2, 2018
emodric
approved these changes
Aug 2, 2018
|
Hi @andrerom |
|
I meant 2017.12 here, it's the release used with eZ Platform 1.13.x, so the oldest branch here that receives fixes for the time being. But if you prefer I can adapt this on merge. But can you report JIRA issue? Or is there one already? |
|
Hi, EZP-30493 created and base branch switched to 2017.12. Thanks. |
andrerom
changed the title
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.
Fix issue with cache not cleared on node visibility change.
Search index takes wrong visibility status from cache.
Todo: