This is a very obscure problem that can manifest in messages advising that a product is out of stock when there is in fact stock available. It only applies if you use components | attributes | choices and permutations, and then assign associated products to each permutation. With these conditions in place, the following chain of events will cause the problem...
1) Mark for deletion either any product, or any subsection, which contains a product that already has one of its choices marked for deletion.
2) Un-delete the same product/section element that was deleted in step 1.
The choice which was originally deleted will have been re-instated implicitly by step 2 but will have inconsistent values in an internal ID field (nValue2). This is turn will effect the stock check procedures on line for the permutation associated with that product.
Simply deleting and un-deleting the choice itself does not cause the problem - you have to delete / un-delete a parent element of the choice.
(v11.03 and 12.00)
1) Mark for deletion either any product, or any subsection, which contains a product that already has one of its choices marked for deletion.
2) Un-delete the same product/section element that was deleted in step 1.
The choice which was originally deleted will have been re-instated implicitly by step 2 but will have inconsistent values in an internal ID field (nValue2). This is turn will effect the stock check procedures on line for the permutation associated with that product.
Simply deleting and un-deleting the choice itself does not cause the problem - you have to delete / un-delete a parent element of the choice.
(v11.03 and 12.00)