Yesterday, after 10+ years of using EE, I fell foul of the maximum content field size, which I think is 64KB, and undocumented. This was in 2.11.3, in which fields larger than 64KB seem to be silently truncated, potentially losing data. In my case, the field had been edited enough times that data was actually lost on the server, and had to be recovered from my test set-up.
Losing data silently like this isn’t good. I’d have expected at least a warning. But since EE2 is on its way out, I’m not going to whine too much about that.
I just deliberately pushed EE3 (3.5.8) in the same way, though, and it doesn’t fail much less clumsily, giving a low-level SQL error and dump of the field:
SQLSTATE: String data, right truncated: 1406 Data too long for column ‘field_id_5’ at row 1:
That sort of works as a warning that something has gone wrong, but it’s not a tidy way to catch or handle the problem.
In addition to gentler error-handling in this situation, it might be nice to have a display in the editing screen which gives a sense of how close a field is to its practical limit. Something like: “2KB used of 64KB”.
Thanks for considering.