Now that 3.5.4 has been released, I would assume this bug can be marked fixed/released unless someone can reproduce it. Is this still a bug?
Now that 3.5.4 has been released, I would assume this bug can be marked fixed/released unless someone can reproduce it. Is this still a bug?