Seeing as this bug was uncovered on our training server running 3.2.10, I feel comfortable confirming this bug and targeting it to series 3.4 also.
Are we still updating 3.3? If so, this bug should be targeted at series 3.3.
Seeing as this bug was uncovered on our training server running 3.2.10, I feel comfortable confirming this bug and targeting it to series 3.4 also.
Are we still updating 3.3? If so, this bug should be targeted at series 3.3.