[Question]:Array to string conversion error when using EditorjsTextField – how should model and migration be defined?

[HosseinEsteki]

What happened?

I’m using the EditorjsTextField component in my Filament form.
When I try to save an article, I get the following error:

Array to string conversion (Connection: mysql, Host: 127.0.0.1, Port: 3306, Database: laravel, SQL: insert into `blog_articles` ...)

It seems that the field returns a JSON string, but my model/migration setup might be incorrect.
I’m not sure what the recommended database column type and model cast should be for EditorjsTextField.

How to reproduce the bug

How to reproduce the bug

1. Create a migration with a json column for content:

Schema::create('blog_articles', function (Blueprint $table) {
    $table->id();
    $table->string('title');
    $table->json('content'); // or longText?
    $table->json('content_images')->nullable();
    $table->timestamps();
});

2. Define the model:

class Article extends Model implements HasMedia
{
use ModelHasEditorJsComponent,InteractsWithMedia;
    protected $table = 'blog_articles';

    protected $fillable = ['title', 'description', 'keywords', 'content', 'status', 'user_id'];

    protected $casts = [
        'content' => 'array', // or string?
    ];
}

3. Use EditorjsTextField in the Filament form:

EditorjsTextField::make('content')
    ->label('Content')
    ->required()
    ->columnSpanFull();

4. Try to create a new article with some content.

---

Expected behavior

I would like to know the correct way to define the database column type and the model cast for EditorjsTextField.
Should the column be json, text, or longText?
Should the cast be string or array?

Could you please provide an example of a recommended model + migration setup for this field?

---

Thanks a lot for your help and for maintaining this package!

### Package Version

2.3

### PHP Version

8.4

### Laravel Version

12

### Which operating systems does with happen with?

Windows

### Notes

_No response_

[athphane]

From what you've said, it should be working just fine.

I use the JSON column type on my migration.

$table->json('content')->nullable(); // nullable because I have the field disabled on Create pages.

And I have the cast configured as array

protected function casts(): array
{
    return [
        'published_at'    => 'datetime',
        'content'         => 'array',
    ];
}

You do not need a content_images column. That is the name of a media collection (spatie/laravel-medialibrary) defined in the Trait. See the Readme -> Quickstart -> Prepare Your Model to learn more. This package integrates with spatie/laravel-medialibrary for image uploads.

If you can provide a reproduction repo with your exact setup, I can take a look at it as well.

[HosseinEsteki]

How is the media library setup? I tried a lot to upload an image into editor js but I couldn't and got an error

[athphane]

@HosseinEsteki can you please let me know what the error is. I can help you better if I know what the error is.

The media library setup is standard just like how it is on the spatie/media-library docs. Nothing special is done to the media library in this filament-editorjs package.

---

I've made a little repo you can close and see exactly how the app is set up.

https://github.com/athphane/filament-editor-js-demo

Clone this repo, check it out and you might see what you're looking for.

I really want to solve this for you. IMO, it's very straightforward.

Let me know how this goes.

[HosseinEsteki]

When I upload an image, this error appears at the bottom of the page.
Of course, I'm using localhost. I don't know if this has anything to do with it.

Couldn’t upload image. Please try another.

[athphane]

@HosseinEsteki are you on the CREATE or EDIT page of your resource? I think you're having issues because you are on the CREATE page. This is my fault. I should have documented that the image upload doesn't work on the CREATE page.

Can you please try to upload a photo after you create the initial record.