Hello everybody, We are using Twill since version 1.2 Now I have updated it to 2.4 but I can't get the repeaters to work anymore. I have migrated all deprecated configs and moved it to the view with annotations. The problem is that the

trigger

button is not rendered. It will render the form if that page has already some data with repeaters, but with new pages I cant get the repeater form to render because the trigger button isn't there. While debugging in vue-devtools I found that the

computed

->

blockType

is always empty. Also the

availableBlocks

is empty. So the trigger button in

Repeater.vue

uses:

v-if="hasRemainingBlocks && blockType.trigger"

, so I think this is the issue, but don't know how to fix. Any advice how to fix this?

I have created a new block with a repeater, for testing purpose:

blocks/test_parent.blade.php

blade
@twillBlockTitle('Test parent')
@twillBlockIcon('text')

@formField('repeater', ['type' => 'test_child'])

repeaters/test_child.blade.php

blade
@twillRepeaterTitle('Test child')
@twillRepeaterTrigger('Add test child')

@formField('input', [
    'name' => 'title',
    'label' => 'Title'
])

Hi @Daniel Ravenshorst, I'll give your snippets a try

Hi @User, thanks a lot

@Daniel Ravenshorst I've been exploring using https://phpsandbox.io/ for a while to support the community with quick shareable sandboxes, and it's really starting to be possible. They recently shipped 4.0 and there are very few issues remaining when installing Twill in there (like media library uploads and some cors issues in embeds). So for your use case this work great, here's a sandbox with your blocks configuration: CMS: https://pc34e.ciroue.com/admin/posts Credentials:

daniel@daniel.test

/

daniel

Sandbox: https://phpsandbox.io/n/shiny-surf-mppe-pc34e Not sure what's happening for you, as this is working great in this fresh application. Make sure you updated your Twill assets using

php artisan twill:update

or

php artisan twill:build

if you're using custom Vue components.

does anyone have any suggestions on how I can use a different set of ENV keys for my S3 data for Twill?

I already am using spatie's media library with AWS, I was wondering if I could override the ENV key name that pulls the S3 info into Twill so I don't have duplicate keys in my ENV file

you can use a bunch of different env keys for S3 in Twill

oh I noticed the AWS_KEY but not the 3rd one, those are the same as the spatie ones! awesome

nice

thanks

I just started up my twill app and I'm following the basic tutorial but when I try to create a new Page it just says CSRF token mismatch

that's probably due to laravel config, did you start from a fresh laravel app?

Hello there!

I've just installed a blank Laravel project (latest version) and I've got a bit of an issue while setting up Twill

I'm unable to create a superadmin account, I've tried using both

php artisan twill:install

and

php artisan twill:superadmin

but I keep getting the instant 'Aborted' message.

I'm on Windows 10(x64)

it's not a fresh app, no

Right, found a fix if anyone else encounters the same problem:

php artisan twill:superadmin myemail@mydomain.com

and you will get prompted with password input.

how would I go about diagnosing this issue? it's not a fresh app but if this is a known issue with Twill what is the fix?

ah looks like clearing some caches etc. fixed it

sounds like you are dealing with another issue though if artisan commands are failing

does the block editor come with any built-in blocks?

there are 2 by default (text and image), but it's really meant for you to have full control

you can compose any form fields in a block

and nest repeaters in blocks

well text and image are great but I don't see them in my editor.. I used the -B option when creating my module

did you add the

block_editor

form field to your form view?

no but the block editor button is there