Twill

I'm gonna leave it at that as it is not Twill specific and as I said that rabbit hole can go as deep as you want.

Thanks <@274035668722647040> Appreciate your time and help. Have moved on to another package.. tenancyforlaravel... lets hope that works out. Thanks again. 👍

How can I change the section name from "CONTENT" to other name ?

and have multiples sections inside the same form ?

<@!560588471152934925> You can change the "Content" label by passing a variable to the form layout:
@extends('twill::layouts.form', [
    'contentFieldsetLabel' => "Hello World"
])

Have a look at the form fields section of the docs. The second example is about setting up multiple fieldsets :

in browser is possible remove max values ?

hmm my Repeater field shows records that have been deleted (deleted_at != null)

<@274035668722647040> make sure the repeated model is soft deletable

it would be if it inherited Twill's model

Hi, just saw when deleting a model the related blocks (from block-editor) wont get deleted. Shouldnt that be handled by the hasBlocks-Trait?

Hey <@!458243766814244875>, that's right, I think you found a bug!

As a quick fix, you could hook into your model's `deleted` event to clean up your blocks :
https://laravel.com/docs/8.x/eloquent#events

Btw. Model-events dont work in Eloquent-Queries (as in ModuleRepository.bulkForceDelete). So i maybe just hook into afterDelete()

True it was extending Eloquent instead of Twill's Model, thanks

<@!553620329453584414> Any reasons why ***forceDelete*** (https://github.com/area17/twill/blob/2.x/src/Repositories/ModuleRepository.php#L436) is not more similar to ***delete()*** so one can use Model-events?

I believe `forceDelete()` is coming from Laravel's `SoftDeletes` trait, not Twill

Ok, correct me if I'm wrong but you should be able to hook on to `forceDeleted` event from `SoftDeletes::forceDelete()`, no?

https://github.com/laravel/framework/blob/8.x/src/Illuminate/Database/Eloquent/SoftDeletes.php#L54

Does not work when using DB:query as in ***bulkForceDelete***. Only when using Models events are fired. So it would be better to also use Models in bulkForceDelete, i think. 
For my use-case i overrid the method and its working like it should now.

But i omit the *isTrashed-condition* which is ok for me

Ah I see, yes, the events aren't fired for bulk queries. Not sure about the original reasoning behind this but I believe it has to do with avoiding N `delete` queries to the database. Does that make any sense?

🤷 😄 
Nevermind, thanks for your help! Appreciate that!

<@305021558831710218> when are you getting this error? while saving?