this will get merged with the built-in styles

i would also like to rearrange the output a bit and add my own wrapper

Ah ok. I don't think you can publish the package's blade views but it would be useful to add!

I think any package views can be overriden by putting them under resources/views/vendor/package-name/...

i think, not sure

@User just did a quick test and it works! I had to adjust to

resources/views/vendor/image

, to fit how the package registers its views.

@User so you could add your wrapper by overriding the

picture.blade.php

view (which you may have figured out by now 😄 )

I'm having trouble getting my crops to work in my blocks. Is this correct usage in the twill config?

@User Yep, looks good

Do I need to define the crops that the block can use somewhere in that case? I have them in the site renderblock, but in my admin block definition I just use a media formfield tag

eg.

Ah, I see! So you would need to use

'name' => 'photoblock'

in your

medias

field to use your crop configuration

Oooohhh okay

Okay that seems to work now! 🙂 Awesome. But how do I distinguish multiple of these photo's in that case? Do I need to create 4 different crop configurations in the Twill config in that case?

Not sure if there's a better way but what I do to reuse crop configs across blocks is with a simple variable:

'block_editor' => [
        'crops' => [
            'single_image' => $single_image_crops,
            'image_left' => $single_image_crops,
            'image_right' => $single_image_crops,
        ],

        ...
    ],

Seems great to me, thanks! Will use the same method

nice! another way to reuse across blocks and models is to use constants in a php file

eg

Crops::SQUARE

Thanks. I incorrectly registered the path for redefinition

after an update to 2.5 we get an error during

php artisan package:discover

=>

PHP Fatal error:  Uncaught Error: Class "App\Exceptions\Handler" not found in /root/development/iu/repos/website-twill-academy-mvp/vendor/area17/twill/src/Exceptions/Handler.php:10

What are we doing wrong?

hey @Shiftless that might be our fault. Do you not have the default Laravel exceptions handler at

app/Exceptions/Handler.php

in your Laravel app?

yes we do have one.

<?php

namespace App\Exceptions;

use A17\Twill\Exceptions\Handler as ExceptionHandler;
use Throwable;

class Handler extends ExceptionHandler
{

uh oh, sorry about that. looking into it! cc @antonioribeiro

in the composer.json there is

"App\\": "vendor/orchestra/testbench-core/laravel/app"

@Shiftless did you set

twill.bind_exception_handler

to false?

let me check

in your composer.json? Or Twill's?

twills composer.json

it is set to true

that's for our tests suite, but this might conflict with extending the handler now that it depends on yours