well I guess it could, it depends on the use case. it might be helpful to your CMS users to have a "title" to indicate why/what the generated voucher is about?

Okay, this sounds good

you're right, thanks ifox

Just coming back to this @ifox, when attempting to perform an action on publish I have a trait with and afterSaveHandleXXX method, but the issue I have is that the published attribute is never dirty (expected), but is always changed (not expected). So

$object->wasChanged('published')

always returns true. this means my action happens on every update. Am I missing something? or should this work?

@chrispymm because Twill calls fill on the model with every field, wether they changed or not, Laravel might be thinking they all changed (since I think it doesn't compare values, just if the setter was called)

you can check

$fields

instead, depending on your use case

yeah, I thought that might be that case. Sorry if I'm being dense, but how would $fields help? As far as I can see fields contains the data for every field (not just the ones that have changed) and as it's an afterSave handler, I can't compare it to the value it used to be...

no worries! you could combine with the prepareFieldsBeforeSave hook to access to previous state of the model

or beforeSave

Hey folks, is there a way I can filter the list of entity items returned by a Browser? I wanted to get only those that match a condition, a column with a specific value. I tried putting a where() on the relationship function and using a custom endpoint on the browser input at the form file to see if a could change the output with a controller method, but I think I didn't quite get the use of the endpoints yet. Thanks

Don't know if this matches your use case, but I had a Category model, with a type attribute, and I wanted browsers that pulled in categories of a specific type, so I amended the

getBrowserData

method on the CategoryController like this:

adding lines 95 and 96 to query by the type. And my form field looks like:

Not sure if this was the most elegant way to achieve it, but it works 😀

@User it can be improved a bit but this is the right way to go about it

for exemple, the form field can be expressed as:

php
@formField('browser', [
    'label' => 'Categories',
    'max' => 5,
    'routePrefix' => 'settings',
    'moduleName' => 'categories',
    'params' => [
        'type' => 'event'
    ]
])

and the

getBrowserData

method as:

php
public function getBrowserData($prependScope = [])
{
    if ($this->request->has('type')) {
        $prependScope['category_type'] = $this->request->get('type');
    }

    return parent::getBrowserData($prependScope);
}

Capsule migrations work out of the box or I need to setup something for these to load?

Yes that is much cleaner 😀. Thanks

@User they should work out of the box (did you enable the capsule in

twill.php

)?

ok, facepalm, I renamed it and phpstorm renamed it in till.php as well. Thanks!

Ok, there is no special caching or anything right? (might be something stupid again, might just call it the day). But my capsule model form is still showing the old form after I replaced the directory with a same named capsule.

This cannot be possible haha

Ok, weird, it was actually cached, until I changed something in the form view

Maybe it reparses the blade files based on the last changed date

In any way, huge edge case 😄

@User That's exactly my case haha. I have a Category model with different types. Thanks a lot guys

Hi, i have a problem with medias.. i cant save project

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'ratio')

project model

public $mediasParams = [
        'project' => [
            'flex' => [
                    'name' => 'free',
                    'ratio' => 0,
            ],
        ],

anyone?