Description of the need
I wonder if we should consider adding breakpoint functionality to core as D8 has done. This would allow core to manage breakpoints that could be used by modules, themes, layouts, ...
I started work on porting that module from D7: - https://github.com/backdrop-ops/contrib/issues/409 - https://github.com/backdrop-contrib/breakpoints
Here's the D8 info: - https://www.drupal.org/docs/theming-drupal/working-with-breakpoints-in-d...
This was @klonos in a separate thread:
Well, we are aiming for as much feature parity with D8 as possible (where it makes sense, and for features that would make people hesitate choosing Backdrop over D8), so I'd be all in for a breakpoints API in core, that both core and contrib could then use.
Breakpoints in core would help with make developing complex frontend themes easier, but could also be used in responsive things in the admin UI, like the admin bar, the primary tabs, the "low priority" columns in tables etc. Breakpoints could even be used as a visibility condition for blocks.
Recent comments
This is helpful. When I Googled for suggestions about the error message, I found an old entry in Stack Overflow that suggested increasing max_connections. I passed that along to the hosting...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?
Thanks for the suggestions. All caches have been enabled from the start. I'm not sure what qualifies as a "complex" view. There are 400-500 pages that include EVA fields. But the vast...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?
Also, when we had some problems with the Backdrop sites, this is what the server admin did: I have increased the max_connections for mariadb and increased the child_processes for...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?