I search entire repository and doesn't return anything on github.

on model.php it shows the variable.

@User https://github.com/area17/twill/discussions/1055

@User

$wasRecentlyCreated

is from Laravel's

Model

class : https://github.com/laravel/framework/blob/8.x/src/Illuminate/Database/Eloquent/Model.php#L107-L112

Other way around 🙂

$wasRecentlyCreated

will be true within the request that creates the item, and false on others

Yeah, I got that wrong since I inverted ! logic for update at my case. Ty for notice, my bad.

So the solution to my problem was that I had to write afterSave before doing anything, not after. That solved the clicking two times problem. And I just saw it on the github how you did it and solved it.

Yes, that's what I found but thought it was not part of Twill so probably was not it.

Any Twill way to get post id in the module controller? Or direct module info for that record? Edit: $this->request->route()->parameters() contains that information.

https://prnt.sc/22bnw9j Hello I have an issue with trying to make "categories" but it doesn't save 😦

I know this stuff uses many-to-many relations if I am not mistake

When you save and refresh the page, your browser field is empty?

yes

Hello again guys. Does any one knows if selected media files appear in window object?

did not quite understand what you mean

Like everything other in JS, you can manually console.log() window object. Twill uses Vuex store, which you can log on html element like this

document.getElementsByTagName('a')[0].__vue__.$store.state

(stackoverflow) Or get some vue extension for debugging

I tryied to console log window.TWILL.STORE to find selected medias on my page, but there is only input fields values and I need to have here selected medias

Check vue file for media state name, to see how is media handled

What do you mean?) Im quite new in Vue. Media fields created in blade like formField('medias' ... I need to get selected medias in my vue

Hi folks. Have people successfully deployed a Twill app to Laravel Vapor? If so how do you get around the issue of Twill looking for admin assets at a relative path rather than where they have actually been uploaded (e.g. a cloudfront cdn URL via Vapor)?

Here's what I'm seeing at the staging vanity URL vapor provides:

The CSS and JS for the admin result in a 404 because they are being called as a relative path e.g. https://my-vanity-url.vapor-farm-e1.com/assets/admin/css/chunk-common.4ff8ead5.css

My env includes these lines to make the admin show up at `/cp`:

I can see in the changelog that Vapor has been used at A17 so I'm guessing this is solveable but I can't see anything in the

twillAsset

code or in config that might help. Appreciate any advice!

Hi @User, I haven't used Vapor myself but I think a quick workaround could be to customize the

twillAsset()

helper : https://github.com/area17/twill/blob/2.x/src/Helpers/frontend_helpers.php#L32