My apologies @timmse, nothing personal.
It’s just that such issues make me crazy.
The Bricks team develops Bricks but doesn’t actually build websites, this is obvious, hence some poor ergonomic or technical decisions, sometimes totally against common sense or every standard or good practice.
Besides, such critical issues for customers (or other backward compatibility problems like the search form, for which I receive multiple daily crash reports) need instant investigations and quick patches, or at least some fast communication if it’s not possible.
Or else, mention on Bricks website that the theme is not suitable for real world production.
Maybe I’m too old school and today standards are not the same, but when I was a developper for a company, I had to publish patches the same day or the day after the bug report, period. And I do the same today for my clients if they report a problem.
Also, I’m very concerned by the fact Bricks won’t fix some issues like the blog prefix added to template URLs or simple ergonomics or accessibility things like a real contrast for selected element in structure panel or other things like that. It is very frustrating for and me it says nothing good about Bricks politics and future.
Finally, it is always the same problem… Companies want to include new shiny stuff at fast pace to compete and attract new customers (like grids, filters, WPML, etc.), but neglect other aspects like good software foundations, improving the existing, no-bug policy, or most basic service principles.
The worst is, today, the trend is to buy an unfinished product, imagine buying a half-working car!
But it’s another subject.
Hear me, Bricks is clearly among the best, but we users are expecting always more
Proof is this great forum’s activity!
That said, thanks for your patience and your awesome work here!
I’ll take a Bricks holiday to cool down.