How can I add new field to the Page entity?

[schel4ok]

I decided to add new fields meta_title, meta_keywords and meta_description, because it is more comfortable for me to have them directly in DB instead all in one extra field.

    public function up()
    {
        // TODO: use JSON data type for 'extras' instead of string
        Schema::create('pages', function (Blueprint $table) {
            $table->increments('id');
            $table->string('template');
            $table->string('meta_title', 50)->nullable();
            $table->string('meta_keywords')->nullable();
            $table->string('meta_description')->nullable();
            $table->string('author', 25)->nullable();
            $table->string('name', 50); // (only seen by admins)
            $table->string('title', 50); // Page Title
            $table->string('slug', 25);
            $table->text('content')->nullable();
            $table->text('extras')->nullable();
            $table->timestamps();
            $table->softDeletes();
        });
    }

Then in PageTemplates I commented 'store_in' => 'extras',

namespace App;

trait PageTemplates
{

    private function services()
    {
        $this->crud->addField([   // CustomHTML
                        'name' => 'metas_separator',
                        'type' => 'custom_html',
                        'value' => '<br><h2>'.trans('backpack::pagemanager.metas').'</h2><hr>',
                    ]);
        $this->crud->addField([
                        'name' => 'meta_title',
                        'label' => trans('backpack::pagemanager.meta_title'),
                        'fake' => true,
                        //'store_in' => 'extras',
                    ]);
        $this->crud->addField([
                        'name' => 'meta_description',
                        'label' => trans('backpack::pagemanager.meta_description'),
                        'fake' => true,
                        //'store_in' => 'extras',
                    ]);
        $this->crud->addField([
                        'name' => 'meta_keywords',
                        'type' => 'textarea',
                        'label' => trans('backpack::pagemanager.meta_keywords'),
                        'fake' => true,
                        //'store_in' => 'extras',
                    ]);
        $this->crud->addField([   // CustomHTML
                        'name' => 'content_separator',
                        'type' => 'custom_html',
                        'value' => '<br><h2>'.trans('backpack::pagemanager.content').'</h2><hr>',
                    ]);
        $this->crud->addField([
                        'name' => 'content',
                        'label' => trans('backpack::pagemanager.content'),
                        'type' => 'summernote',
                        'placeholder' => trans('backpack::pagemanager.content_placeholder'),
                    ]);
    }

}

But when I create new page I don't see values saved in my new fields meta_title, meta_keywords and meta_description.
What I should do more?

[backpack-ai-bot]

To have your new fields (meta_title, meta_keywords, and meta_description) saved directly in the database columns (instead of inside the extras JSON column), you need to make sure of the following:

1. Remove 'fake' => true from the field definitions.
   The 'fake' => true attribute tells Backpack to treat these fields as "fake fields" and store them in a JSON column (like extras). If you want them as real columns, do not mark them as fake.

2. Add the new columns to your model's $fillable property.
   This allows mass assignment for these fields, so Backpack can save them.

3. Do not use 'store_in' => 'extras' (which you already commented out).

Example changes:

In your field definitions, update like this:

$this->crud->addField([
    'name' => 'meta_title',
    'label' => trans('backpack::pagemanager.meta_title'),
    // 'fake' => true, // REMOVE THIS LINE
    // 'store_in' => 'extras', // already commented out
]);
$this->crud->addField([
    'name' => 'meta_description',
    'label' => trans('backpack::pagemanager.meta_description'),
    // 'fake' => true, // REMOVE THIS LINE
]);
$this->crud->addField([
    'name' => 'meta_keywords',
    'type' => 'textarea',
    'label' => trans('backpack::pagemanager.meta_keywords'),
    // 'fake' => true, // REMOVE THIS LINE
]);

In your Page model, add the new fields to $fillable:

protected $fillable = [
    // ... other fields ...
    'meta_title',
    'meta_description',
    'meta_keywords',
    // ... other fields ...
];

Summary:

• Do not use 'fake' => true for real DB columns.
• Add the new columns to $fillable in your model.

This will ensure Backpack saves the values directly to the meta_title, meta_description, and meta_keywords columns in your pages table, as you want.

This approach is confirmed by the Backpack team in similar situations, where not adding the field to $fillable or marking it as fake prevents it from being saved as a real column Error in translatable models. and create new field does not save the value in the database.

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

CRUD API|Create & Update Operations Part 1
Github Issue (closed): Fake fields are not always saved into DB
Github Issue (closed): What Are Fake Cols/Fields For? (Add Documentation)
Github Issue (open): [v12][Feature Request] store fake fields in "meta" table
Github Issue (closed): Fake field not loading when stored in a field not called extras
Github Issue (closed): Translatable fake fields.
Github Issue (closed): Translatable fake fields getTranslation() must be type string
Github Issue (closed): Error in translatable models.
Github Issue (closed): create new field does not save the value in the database
Github Issue (closed): Translatable models and multi-language CRUDs form values not saved
Github Issue (closed): restoreRevision error 500 with fake fields
Github Issue (closed): [Bug] One crud of many not properly working create/edit/preview pages.
Fields|Optional - Fake Field Attributes (stores fake attributes as JSON in the database) Part 2

[schel4ok]

I doesn't work for me.
For now I have only behaviour that meta_title, meta_description, and meta_keywords are not anymore saved in extra JSON.
But meta_title, meta_description, and meta_keywords columns still not filled in DB.

I suspect that problem with model Page.
How I should add the new fields to $fillable in Page model?
For now I just copied Page file from \vendor\backpack\pagemanager\src\app\Models\Page.php to \app\Models\Page.php and changed namespace in the file to namespace App\Models, but still it doesn't work.

[tabacitu]

@schel4ok I notice you've been using our AI to help you code. I have great news - the AI is now available for free on our website (see bottom-right corner). Please use it there, where you can have a conversation.