no, I fixed it. I used a constructor on the JamController, to access the JamRepository, and that's what broke it. fixed it by using app()->make(JamRepository::class)->method()

oh yes if you want to inject from the constructor you'll have to inject what the underlying ModuleController is injecting and call the parent construct

oh okay, I'll get back to that when I need it!

Hi! Tell me, does the twill media library provide for the possibility of creating folders?

Hi, I'm having some difficulties with a custom CMS page. I will receive some data from an API and I need to show it in a list for the editor to choose which one he will publish and which he won't. I tried using the twill::layouts.listing passing the data through the $tableData. Changed the publishUrl to the put route and it worked so far. But when I click in the publish it calls a route with Query parameters that break the view, it stops showing the data, in DevTolls there is an empty preview.

custom page listing

Hi, I tried out 2.8.0 today and noticed I cannot save my entities anymore due to an exception thrown by Symfony: "Input value "languages" contains a non-scalar value." - This is correct and deprecated (https://github.com/symfony/symfony/issues/44432) - the issue occurs in vendor/area17/twill/src/Http/Requests/Admin/Request.php line 49: $this->request->get('languages') => only scalar values, but languages is an array (see screenshot). It shoud rather be $this->request->all()['languages'] Anyone else ran into this issue? Or is it already a known issue at this point? 😉

Hi @nuffsaid thanks for flagging, I was not aware of this issue. I'm assuming you're using

rulesForTranslatedFields

in your form request class? I'm surprised this hasn't been identified in the recent refactoring, but we'll fix it as you describe.

@ifox exactly

you can use a different parent request class in the meantime, but we'll fix and release 2.8.1 asap

thank you!

Hey folks, I was wondering if there was an efficient way to get a property of a related model selected from a block field in the module

$indexColumns

?

The only way I could think of to do it was to create a new attribute that manually pulls the property, but it's slow as heck for obvious reasons

e.g.

public function getArtistNameAttribute() {
        $artist = $this->getRelated('artist')->first();

        return !is_null($artist) ? $artist->title : "";
    }

protected $indexColumns = [
        'artist_name' => [
            'title' => 'Artist',
            'field' => 'artist_name',
        ],

and so forth

Can I maybe use dot notation?

Hey @tfilos it looks like for something like this you should probably save your artist using a belongsTo relationship instead of the polymorphic related table

That makes sense. I haven't had much luck connecting the browser to laravel's proper relations

Are there custom hooks I need to implement in the module controller in order to use Laravel's relationships?

I suppose I can just do this in the Repository

instead of using the relatedBrowsers feature, you need to use $browsers in the repository (or manual update / getFormFields hooks) alongside the relationship in your model. It will detect if it's a belongTo or many.

Interesting, okay. Will give that a shot.

Okay, simple as that apparently!

So then is it possible to use Laravel dot notation to get that relationship value in the

$indexColumns

array? I've tried a few permutations to no success

I suppose I can just eager load the relation and call it that way

That way it takes 2.35s instead of 12.53s like before. Still a little slow but not so bad. Probably need to add a couple of indexes

yup, i don't think dot notation would work there. that still sounds very slow, did you disable pagination? or maybe this is the hardware you're running it on?

It's probably partially that I'm running it locally, no query caching. Thinking possibly an index or two is also missing on my side but will verify

Hello, I'm facing this issue where language checkbox labels are displaying strangely on production. Any hints appreciated

index tweaking hardly does anything --- I'm betting this will speed up once it's on production