Just a note to remember that this issue still exists in v3.0.10. While I understand there is a mass removal procedure, I want to report this particular behavior.
Paolo
Just a note to remember that this issue still exists in v3.0.10. While I understand there is a mass removal procedure, I want to report this particular behavior.
Paolo