Our client uses scheduled unpublish for certain nodes, but we discovered these items still exist in ExternalIndex, and when looking at the Published property in this index, nothing seems to have changed too.
This shouldn't be the desired behaviour right?
As far as I know there isn't an event for scheduled (un)publish on which we could subsribe to, right? Otherwise we could make sure the node will be removed when such an event arrises.
Maybe you guys are familiair with this issue and can give me a clue how to fix this?
Scheduled unpublish doesn't get item removed from external index (Or Published set to N in index) What to do?
Hi,
Our client uses scheduled unpublish for certain nodes, but we discovered these items still exist in ExternalIndex, and when looking at the Published property in this index, nothing seems to have changed too.
This shouldn't be the desired behaviour right?
As far as I know there isn't an event for scheduled (un)publish on which we could subsribe to, right? Otherwise we could make sure the node will be removed when such an event arrises.
Maybe you guys are familiair with this issue and can give me a clue how to fix this?
Thanks!
Still no one with a solution for this?
is working on a reply...