Hey @User, it's definitely possible to extend the user

form

view, as you described. You could copy the view from Twill source to your project at

resources/views/vendor/twill/users/form.blade.php

and modify it.

The more complicated part is to extend other files like,

User

model,

UserController

, and so on. As far as I know, this can only be done with composer configuration. You copy the files into your project and configure composer to use your copies instead of Twill files. Not ideal.

seems good

If I may suggest a different approach to investigate: you could create a separate Twill module, such as

profiles

and then attach that to Twill's

users

with a 1-1 relationship. Maybe this short tutorial can help: https://gist.github.com/pboivin/d20d23ae130ea9a112ee49dd98f00239

okay, that second part is bit more complicated than I thought it would be

I'm a bit confused. This tutorial does not connect Profile with Twill-user (who can log in to the admin), but the default Auth User, right?

Yes that's right. I suggested this mostly to illustrate the general approach, but it would need to be adapted to work with

twill_users

instead of Laravel's

users

I don't know of any complete tutorials for exactly what you are trying to do. But it would be great to have one 😉

I see. Good, now I understand 😅

Hi, has anyone experienced problems with the assets compilation in dev mode? No css has been imported for me building it in dev mode.

Hey @User, are you running

php artisan twill:dev

to work on custom components? Or is this standard

npm run dev

in your project?

Twill: dev

Cool, did you set this in your

.env

?

TWILL_DEV_MODE=true
TWILL_DEV_MODE_URL="http://localhost:8080"

TWILL_DEV_MODE_URL will depend on your setup actually. If you are using homestead, this will probably be like

my-site.test:8080

Hi, how can i copy blocks from vendor to site/blocks ? by command

btw, if i create image.blade.php in site/blocks with

{{ $block->image('image') }}

i have blank image

@`Sebastlan the crop config doesn't go there, it goes in the twill.php config file

yhmm

it is like mediasParams in model?

> If the formField is used inside a block, you need to define the mediasParams at config/twill.php

cover-> default,mobile ,flexible?

you can do whatever configuration you need in each crop config

yhm i will check it

this 'crops' will by dynamic for all modules yes?

yes for any block/repeater, so you need unique keys for those. I'd rename image by block_image or something to avoid conflicts with another block where you need another crop config

yhm i will check it when i create new module