October CMS - Data too long for column 'content' at row 1

Question

I have an error saving a field to the database, which is giving me the error: String data, right truncated: 1406 Data too long for column 'content' at row 1.

However the field in the database is set to Type: String, length 191. Which i believe translates to varchar.

Anybody else had this?

use text field for the datatype – Shobi Aug 19 '18 at 14:02 — Shobi, Aug 19 '18 at 14:02
what is wrong with it, i mean having HTML in the input – Shobi Aug 19 '18 at 14:03 — Shobi, Aug 19 '18 at 14:03
What exactly are you asking? – Ozan Kurt Aug 19 '18 at 14:04 — Ozan Kurt, Aug 19 '18 at 14:04
It seems it was a simple change of string to text.. Thanks. – m33bo Aug 19 '18 at 14:06 — m33bo, Aug 19 '18 at 14:06

score 1 · Answer 1 · answered Aug 19 '18 at 14:07

https://stackoverflow.com/a/13182846/2693543

copied from above answer

VARCHAR(X) Case: user name, email, country, subject, password

TEXT Case: messages, emails, comments, formatted text, html, code, images, links

MEDIUMTEXT Case: large json bodies, short to medium length books, csv strings

LONGTEXT Case: textbooks, programs, years of logs files, harry potter and the goblet of fire, scientific research logging

score 1 · Answer 2 · answered Aug 19 '18 at 14:11

Use this in your migration file and it will change your column data type and then you can save html content into it without any problem.

public function up()
{
    Schema::table('the_table_name', function () {
        $table->longText('columnName')->change();
    });
}

public function down()
{
    Schema::dropIfExists('the_table_name');
}

score 0 · Accepted Answer · answered Aug 19 '18 at 14:07

0

You should NOT store a posts or pages content (something that contains a lot of text/html) as String.

Instead use TEXT for the MySQL column type, which allows to enter enough characters in there.

answered Aug 19 '18 at 14:07

Ozan Kurt

3,731
4
18
32

October CMS - Data too long for column 'content' at row 1

3 Answers3