Editing a public node resets search index to 0%

The method _private_nodes_update_privacy_table() calls search_wipe(null,null,true), which removes the entries node_cron_last and node_cron_last_nid from the variables database table. This effectively resets the indexing back to 0%.

This occurs every time an existing public node is edited and saved.

I assume the intended behavior is to index the edited node only, especially if the visibility was changed from private to public.

I replaced the call to search_wipe(null,null,true) with search_wipe($nid, 'node', true) to prevent the index reset.