Hello Brian,
You are right, that behavior is caused by an issue introduced in 3.1.6
Do you still have the incorrect behavior using 3.1.7? It should be fixed in that version.
My regards
Hello Brian,
You are right, that behavior is caused by an issue introduced in 3.1.6
Do you still have the incorrect behavior using 3.1.7? It should be fixed in that version.
My regards