PatrickRQ Posted February 15, 2023 Share Posted February 15, 2023 Hello, I tried to post a long comment for a record created within Pages database and fall into the issue: IPS\Db\Exception: Data too long for column 'comment_post' at row 1 (1406) The database_comment table has comment_post column of TEXT data type which is 65535 in length. Consider changing it to to MEDIUMTEXT or LONGTEXT to avoid such scenarios. Thanks. Link to comment Share on other sites More sharing options...
Marc Stridgen Posted February 15, 2023 Share Posted February 15, 2023 Please could you advise on which database is this on your system, so I can take a look? Link to comment Share on other sites More sharing options...
PatrickRQ Posted February 15, 2023 Author Share Posted February 15, 2023 What do you mean on which database? This is MySQL, InnoDB. Link to comment Share on other sites More sharing options...
Adriano Faria Posted February 15, 2023 Share Posted February 15, 2023 Just now, PatrickRQ said: What do you mean on which database? This is MySQL, InnoDB. Pages database. Link to comment Share on other sites More sharing options...
PatrickRQ Posted February 15, 2023 Author Share Posted February 15, 2023 (edited) 7 minutes ago, Adriano Faria said: Pages database. Pages creates own table aka cms_database_x and the issue I mention is in database_comment table comment_post column. On the top of that, seems there is no protection that would check data length before attempting to INSERT data to DB, what results now in throwing an error. Edited February 15, 2023 by PatrickRQ Link to comment Share on other sites More sharing options...
Marc Stridgen Posted February 15, 2023 Share Posted February 15, 2023 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. tnn 1 Link to comment Share on other sites More sharing options...
Solution Marc Stridgen Posted April 4, 2023 Solution Share Posted April 4, 2023 This issue has been resolved in our recently released 4.7.9 version. Please upgrade if you are seeing this issue, and let us know if you see any further issues. Link to comment Share on other sites More sharing options...
Recommended Posts