When segment selector redirects to new segment, must make sure value is triple encoded to match 3 urldecodes done server side.
@diosmosis must have missed that. Can you point me to the change or where this is done? 3 urldecodes are quite a few :) were we also not breaking anything when we did that?
i see guess that makes sense. not sure re possible side effects.
These changes should only affect the segment editor (ie, the segment definition that gets saved & what we redirect to). I suppose it might not recognize definitions for old segments that were created improperly... not too sure. Will test a bit more.
Did some more testing, seems to work, couldn't find any issues.