I'm glad that workaround worked. We will include that fix in the next revision of the stack that we will release in the following days. I'm sorry for all the inconveniences this may have caused to you.