Matrix's robustness

Hi,
I moved to the trash a single std page which had close to 300 std pages as children. The popup came up as expected and started slowly moving the assets. I then absent-mindedly (and after doing a couple of other things) clicked on the log out button.



As expected the popup window (being only 30% complete) didn't like it. Logged back in and saw that the parent asset was in the trash along with what appeared to be all its children. Cleared the HIPO and I am know purging the trash.



The question is, what effects would the cancelling of the HIPO have had? Is my DB a mess?

As I write this, i remember a script checking for orphan assets. Is that what it is designed for?



Cheers.

[quote]The question is, what effects would the cancelling of the HIPO have had? Is my DB a mess?
[right][post=“8737”]<{POST_SNAPBACK}>[/post][/right][/quote]



Nope. Actually, moving a single asset with lots of children to the trash is really easy: As the single asset is moved, all its children come with it automatically. The rest of the move HIPO is just removing the URL from all the children – this is the time consuming bit, but its not site-breaking if it doesn’t complete.



Also, if you have a Squiz Server running, the HIPO will continue even if the pop-up is logged out. You can login again and check its progress on the HIPO Herder screen. As long as the “Time since last update” stays below 10 seconds or so, you can be sure the HIPO is still being processed.

Ace. Thanks.