Hello @User , I did check your git sample.

did you read this message too before pinging me again in DM? please state your actual problem so we can help you and stop pinging me in DM I don't need you to notify me in 2 places.

okay. I will ask only here. okay?

so if I want to manage users info, I should make new table for twill and make relationship between user table and profile table in twill?

Yes, like I said, that's one way of doing it and the gist is showing you all the steps needed

Is there other way?

your user is currently extending the eloquent model. If you make it extend the Twill model, which is discussed in the second link I sent you, you will be able to manage it in twill without a separate table. But what is your concerns with a separate table?

well, in user table, there are so many fields.

and also, there are some other table linked with user table.

and in admin side, I hope to make admin can mange them.

so I will explain more detail.

user have several step for registration.

so first step, user can input their normal data.

then admin can see registered user on the first step.

then admin can accept or refuse user to next step.

I would like to this functionality using twill on back office.

Hey @User , yes the

profiles

example in the tutorial adds a separate table and a relationship to the

users

because this is the most simple way. You can make your

User

model extent the Twill

User

, but this is very custom. You will have to figure most of this out on you own... because this is not what Twill

User

was designed for. It is separate from Laravel's

User

exactly to allow frontend vs. backend users. This may be improved in the future, and made easier, but for now, it's custom land.

so you suggest separate table?

Sorry I think I wrote too fast there ⬆️ . You are not working with Twill's

User

but I think my comment still applies. It's quite a bit of work right now to plug an external model into Twill's Model. This is why the tutorial approaches it with a relationship. And yes I would recommend you explore that. Try to find the most simple solution to your problem.

thanks.

I should solve this asap.

@pboivin regarding extending the Twill model on existing models, I think the only non standard aspect is that it includes the soft delete trait. which technically means only the

deleted_at

column would need to be added to an existing model to be able to be loaded in a twill module.

so could I make list the existing model data on twill UI?

this is main point.

and updating the existing model data on twill UI.

yes you can, but that will require custom code from the repository of the module you use. you will have to pull data from the user relationship to fill the form data so that the form fields can show the existing data, and when saving, you will need to update the user associated

Is there any sample for this?

??

@User I think the answer is no, there is no tutorial or ready made code for this. Please explore this problem and write this tutorial. This would be a very cool contribution!

so twill is only used for content management not for data management?