Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Update search index in hide cronjob #1348

Merged
merged 4 commits into from
Jun 25, 2018
Merged

Update search index in hide cronjob #1348

merged 4 commits into from
Jun 25, 2018

Conversation

SerheyDolgushev
Copy link
Contributor

@SerheyDolgushev SerheyDolgushev commented Feb 1, 2018

@andrerom andrerom requested a review from emodric February 6, 2018 10:36
@@ -49,6 +49,9 @@
{
$cli->output( 'Hiding node: "' . $node->attribute( 'name' ) . '" (' . $node->attribute( 'node_id' ) . ')' );
eZContentObjectTreeNode::hideSubTree( $node );

//call appropriate method from search engine
Copy link
Contributor

@andrerom andrerom Feb 6, 2018

Choose a reason for hiding this comment

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

nitpick: // Call appropriate ..

@gggeek
Copy link
Contributor

gggeek commented Feb 6, 2018

Seems legit.

I wonder if there are other cases in the legacy kernel where we miss similar calls...

eg: content/copy.php first creates a copy and only after it updates the visibility => if copy an hidden node, does the copy gets indexed as visible or invisible ?

@andrerom andrerom requested a review from kmadejski April 5, 2018 06:11
@andrerom
Copy link
Contributor

andrerom commented Apr 9, 2018

@l0rdJ Seems some new commits have been introduced here now, possible to cleanup tp focus on the cronjobs/hide.php change so we can merge it? See also review comment while on it if possible.

@SerheyDolgushev
Copy link
Contributor Author

@andrerom I pointed source branch for this PR.
I will check other possible cases where this call might be missed a bit later.

@andrerom
Copy link
Contributor

andrerom commented Apr 10, 2018

@l0rdJ Ok, but this PR is good to go now right?

@SerheyDolgushev
Copy link
Contributor Author

Yep, it safe to merge it to master as it is

@@ -90,6 +90,7 @@ eZOEPopupUtils.settings.onInitDoneArray.push( function( editorElement )
ezoeLinkAttribute.timeOut = setTimeout( eZOEPopupUtils.BIND( ezoeLinkAttribute.ajaxCheck, this, url[0] + '_' + id, lid ), 320 );
return true;
});
inp.keyup();
Copy link
Contributor

Choose a reason for hiding this comment

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

@l0rdJ I think you accidentally merge in unrelated changed here, or?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@andrerom Sorry, you are correct. It was unrelated change. This change was related to #1291.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, merged that first so it got resolved when merging this, thanks @l0rdJ !

@andrerom andrerom merged commit 6f4e99f into ezsystems:master Jun 25, 2018
andrerom pushed a commit that referenced this pull request Jun 29, 2018
* Update search index in hide cronjob

(cherry picked from commit 6f4e99f)
mateuszbieniek pushed a commit to mateuszbieniek/ezpublish-legacy that referenced this pull request Jan 3, 2019
* Fix link source change (object => node) when editing a version

* Update search index in hide cronjob
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
5 participants