To the Wix team. We are now well into the beta program and some people developed live sites with Wix Code. Still in beta, the code changes, that is not the problem. What now does start to become a problem is the lack of info WHAT changed. This is important, for we cannot constantly test all parts of our code all day.
One example of a change that broke a part of my code is that wixLocation.baseUrl did not return the path with a slash at the end, but I noticed since yesterday that it does, breaking a part of my code.
Could you contemplate a more elaborate way of informing us what has changed, so we can make an educated guess if it merits re-testing?
Hi Giri,
Thanks for bringing the point to our attention.
I’ll have a talk with my colleagues about it.
Liran.
Hi Giri,
I checked and it seems like it always had a slash in the end.
Any chance you can reproduce this?
Liran.
Hi Liran. Another hat tip for your level of support. But no, I cannot reproduce it, but I am certain of it because I constructed a URL with baseURL + “/somepath”. It did not give me a double slash, otherwise it would not have worked. But day before yesterday, I just tested it again and a click brought me to my Home page, not the page I wanted. Cause was a double slash.
On a more broader note: I have been pondering my suggestion a bit more, and came to the conclusion that this can become a major problem for Wix Code. The advantage of a managed environment is that a web master doesnot have to install new versions of components, databases, OS-patches, etc. But: when something in code changes, he has no option whatsoever to test it on a copy site, hold back a certain patch, etc. So code could brake and clients will become angry at him, not you. Therefore, I cannot stress enough the need for some kind of documentation, or, better, managed updates (Thursday Patch Day) with some kind of testing bed to prevent chaos. And it will happen, because it can.
I couldn’t agree more.
We are aware of this, and we’re really doing everything we can to avoid breaking changes.
Please let me know any time you see something like that, that’s why we’re here for.
Liran.