but atleast now it's working, sorry for the trouble

hi everyone! is there anyway to add more field in user setting, i want to add field avatar for user

Hey @User I have not yet done this myself, but I believe you can customise the model that is behind the user. Alternatively you could also disable regular user management and implement that module yourself. Maybe others have better ideas doh :).

Hi guys, there's actually an option for that!

config('twill.enabled.users-image')

Ok, I wanted to write what ifox said haha, but Im interested in User Model since its in vendor location? What would be best solution to extend it in app? For additional fields

or composer overrides

Im gonna check it out thanks

❤️ thank u

i got problem with pagination, when i'm in first page, i click next page and it jump to page 11 at address bar url

Seems like an weird issue. Have you checked DB if you have some malformed inputs? It happened to me on manual inserting over Eloquent model before. Have you maybe tweaked

protected $perPage

in Controller ? Any console errors?

Does multi select inline accept default values since this is not working?

php
    @formField('multi_select', [
        'name' => 'translate_langs',
        'label' => 'Translate langs',
        'unpack' => false,
        'note' => 'Langs which user can translate',
        'default' => 'sr',
        'options' => array_map(function($locale) {
            return [
                'value' => $locale,
                'label' => getLanguageLabelFromLocaleCode($locale, true)
            ];
        }, config('translatable.locales', ['sr']))

it doesn't

Ok ty 🙂

it could though, please submit an issue if you'd like it to be possible

In my case its also good if it doesnt have an default value so Im good. I could raise an issue if this could affect some other users.

there was an issue about adding the default feature to a couple of fields that were missing it which was addressed recently, you can reference it

Ok, also docs are missing this fields in description so Ill reference it, probably gonna make a PR for it. @User do you have some edits for this in your docs PR's?

No, I do not have pending docs afaik 🙂

It happened on all modules, no error in console

It seems like you have perPage set to 1, correct?

that's right

Hello, I'm using the prepareFieldsBeforeCreate($fields) method in a subscription repository to create a new user if the field new_name is not empty:

public function prepareFieldsBeforeCreate($fields) {
        
        if($fields['new_name'])
        {

            $user = new User();
            $user->name = $fields['new_name'];
            $user->email = $fields['email'];
            $user->password = Hash::make($fields['password']);
            $user->save();
            $fields['user_id'] = $user->id;
        }

    
    return parent::prepareFieldsBeforeCreate($fields);
    }

I'm having two problems with this code. First, it creates two subscriptions with the new user correctly assigned, and second, if I don't send a new_name, twill will not validate the fields and throw a "Your submission could not be validated, please.....".

Hi @User, I'm not sure if

prepareFieldsBeforeCreate()

is the right hook for your use case. First, I think this runs after your form request is validated, so it's technically too late to trigger the message you're talking about.

pagination-issue

Or maybe I don't fully understand this part > if I don't send a new_name, twill will not validate the fields and throw a "Your submission could not be validated, please....." Can you expand on that?

Hi @User , I need to be able to create a user for a subscription. When I click on the "add new" button the modal will show the following fields: title, user name, user email, and user password. When I fill out all fields, it will create two subscriptions instead of one. When I want to add a new subscription for an existing user, only the "title" field is required on the create modal. It is in this last modal that the validation fails and the modal doesn't create a new subscription. I know that it would be better to have a user first and then add a subscription to him, but I failed trying to add a user controller.... it would bring twill users instead of front-end users..... ??

If I understood you, you want to make separate actions on create and update actions from Twill?

@User I was trying to create a new user and a new subscription from the same "create modal"