Bricks 1.5.5 release brought a few new bugs. 2 being serious (loop & class lock issues). I think it’s high time Bricks add one more member to the team who can handle Quality Assurance. Such bugs should have been detected easily. A QA can test 10 sites covering multiple scenarios while testing pre-release product. I find it hard that easy bugs are missing the testing.
I am happy with what Bricks is doing but this is a serious issue. A major bug in future release can break confidence of users. I know it’s not possible for any product to be bug free. Code changes will bring bugs. That is fine. But it’s beyond my understanding how can silly stuff is not being tested before release.
If @jornes have time or can make time then I recommend his name for such a testing position.
Hi, Yes I have updated 6 sites. All have loops and grids and I have had no problems at all. I also tried to recreate your example but again a new loop just works - although without a lot more info I can’t really say that my test duplicated yours exactly.
I wasn’t doubting that you have an issue. I was trying to make the point that just 1 person reporting an issue does not necessarily make it a serious bug. On the back of that to then claim the sky is falling and things must be changed is several steps too far.
Don’t update on a production site without first testing on a staging site. New releases bring bugs. It’s a point point release.
That’s why the update cycle has been updated to smaller, quicker releases so bugs can be squashed quickly. If you find a bug, report it and move on. The team know what they are doing and they are managing things well.
Ultimately don’t update your production site day of release and not without tearing first. Wait until confirmation that any bugs that affect you have been closed before updating.
