can you share your user model here?

yes.

just moment.

user_model

I am not sure that model is extended to twill model.

it is not. Right now you're extending authenticatable

which you will still need but you can get differently, one sec

haha, yes .right.

well that model must extend authenticateable.

so you need to extend Twill's model and use the traits and interfaces from this Laravel class

I will try on this.

Good evening. Does a module require to have

deleted_at

column? Currently my index page throws

column not found

error even though I set

$forceDeleting

to true in both model and translation model

Hey @User , yes I think the column is necessary because of the

SoftDeletes

trait on the base

Model

class

thanks. What confuses me is that there is an option in

createDefaultTableFields

helper to not create deleted_at column

it's the

softDeletes()

I think nervermind, clearly not focused today 💤

looks like an inconsistency. Currently if you extend the twill classes it will expect that column to exist. It shouldn't be mandatory and will be addressed in Twill 3

Thanks you both on saturday evening. Too great for open source support

🙏🏻

thing is you can perfectly use a model that doesn't extend twill's and doesn't use soft deleting so I guess we left that door open in the helper, but that's definitely not standard behavior of a twill module since it has features to delete and restore before destroying by default

thanks for this tip. I'll rather add one column than not extending Twill's model 😅

Repository acting differently when used inside seeder I've come across a very specific edge case when I've tried to seed my database (including tranlsations and slugs) via Twill generated repository.

php
...
    public function run() {
        $repository = app()->make(App\Repositories\WorkshopRepository::class); // doesn't matter how it's obtained, behaviour is the same
        $repository->create(["title" => ["cs" => "Testing"], "slug" => ["cs" => "testing"]]);
    }
...

The problem happens only when the seeder is being called from

db:seed --class=...

command. When I try to run the command by following the exact same logic in

php artisan tinker

, it works correctly. What happens Internal error (Grammar::parametrize()), happens 'cause the slug entry is still present in the array that is retrieved by getAttributesForInsert() in the Laravel's model class in performInsert() which is not the case when run from tinker instance/or web. Laravel: 8.63 Twill CMS: 2.5.2 Should this be posted as an issue or am I missing something here? Thank you.

Hey again, I have

"publish" => false

in my indexOptions in Controller but I still get an SQL error that

published

column was not found.

in other module it works correctly, I don't know what could be wrong with this one

is it still in your fillables, maybe ?

If I delete that, I get

Add [cmsSaveType] to fillable property to allow mass assignment on [App\Models\ProductOptionCategory

if you delete publish false?

you mean in the controller? Still the same

seeding-issue

Oh, I got it. For some reason There cannot be empty "fillable" array. There was actually not problem with the published field but with empty fillable