In almost every Backdrop project at AltaGrade, we find it necessary to trim all textfields using a custom hook. This is because users often leave empty spaces at the beginning or end of their entries. While it may not be a significant issue for textfields like names, as it might only disrupt alphabetical ordering, it becomes more critical for fields that can accept mixed values such as text, integers, and floats. This can affect calculations and lead to more serious consequences. Therefore, I briefly considered the idea of having every textfield entry trimmed by the core. This could be a beneficial solution without causing any known issues. However, I acknowledge that this is just my opinion, and I welcome everyone to share their insights on this matter.
GitHub Issue #:
6386
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?