yes, block controller (TwillBlockComponent)

hmm i think something is broken 😄 currently no block saves / get data. the post request has all fields but then it gets lost

Just checking: do you have HandleBlocks and HasBlocks traits on your repository and model respectively?

yes

it must be something different, now page inputs dont save anymore (without the blockeditor)

did you update your twill build after your last composer update?

fresh install, two block components with same fields.

public function getForm(): Form
    {
        return Form::make([
            Columns::make()
                ->left([
                    Input::make()->name('title')
                ])
                ->right([
                    Wysiwyg::make()->name('text')
                ]),
            Input::make()->name('test')
        ]);
    }

public function getForm(): Form
    {
        return Form::make([
            Input::make()->name('title'),
            Wysiwyg::make()->name('text')
        ]);
    }

database:

"blocks": [
        {
            "blocks": [],
            "browsers": [],
            "content": {
                "text": "<p>text</p>",
                "title": "title"
            },
            "editor_name": "default",
            "id": 1676230583471,
            "is_repeater": false,
            "medias": [],
            "type": "a17-block-app-test"
        },
        {
            "blocks": [],
            "browsers": [],
            "content": {
                "test": "test"
            },
            "editor_name": "default",
            "id": 1676230585590,
            "is_repeater": false,
            "medias": [],
            "type": "a17-block-app-column"
        }
    ],

strange is, that the title field get the value from first title field

I found the bug

column field dont have a block id

Everything is in dutch but the titles are taken from the EN lang. And if i don't give them english title there are none and i cannot click them to open them. Something else, i cannot delete usint the 3 dots only when selecting on the left side and using the bulk dropdown to delete.

@jefsev delete using the 3 dots is fixed on rc4

nice 🙂

Is it pretty save to upgrade to rc4?

Regarding the locale, as I mentioned last week, your first locale in translatable.php should match your twill and app locale

yes

Ok ill check that again, i thought i changed that to default NL But maybe i forgot a place

Column is an artificial field though, it doesn't have any value to save for itself. It's only rendering the fields wrapped in elements with css classes and the form submission would result in the same thing wether you use columns or not

@ifox normals fields

<input data-v-9edd5ab6="" data-v-0d108f70="" type="text" placeholder="" name="blocks[5][test]" id="blocks[5][test]-1676318057641" autocomplete="on">

fields in columns:

<input data-v-9edd5ab6="" data-v-0d108f70="" type="text" placeholder="" name="title" id="title-1676318060913" autocomplete="on">

there is no "block[]" index

ok I see what you mean now, sorry I didn't get that's what you meant at first

definitely sounds like a bug

no problem^^

I have multiple layers. Like: /en/knowledge-base/faq-slug/ /en/knowledge-base/faq-slug/faq-page-title but twill generates the faq-page-title slug as follows: /en/faq-slug/knowledge-base/faq-page-title It switches faq-slug and knowledge-base for the two under Frequently asked questions Any idea why? Maybe something is going wrong when using an empty permalinkbase? protected $permalinkBase = '';

@ifox should I open a git issue?

Hi guys! Are you planning to implement pagination for Sortable models?

Hi, i get the following error when using laravel scout:

Trait method Laravel\Scout\Searchable::usesSoftDelete has not been applied as App\Models\Page::usesSoftDelete, because of collision with A17\Twill\Models\Behaviors\HasNesting::usesSoftDelete

use Laravel\Scout\Searchable; Adding Searcable from scout to a model results in a http 500 error when trying to create a post

Interesting, that's not our experience, we have plenty of twill sites with scout

could be only affecting models that use HasNesting

Happy to if you have a solution for it, as I'm really not sure how a listing that can be reordered with drag and drop could be paginated? How would you move a record from a page to another?