Okey i solved now

yes and there you are using the correct key,

blog

. In your previous screenshot your navigation is trying to find realEstates.realEstates, not real.realEstates

I chanced route prefix like this admin.realEstates.realEstates.index as you say

Thanks

are Conditional fields broken in 2.5.2? i've tried both examples at https://github.com/area17/twill/blob/2.x/docs/.sections/form-fields.md#conditional-fields in a couple of different modules, and nothing renders on the page. Removing the examples causes the pre-existing fields to reappear

I did amend the

true/false

option to be

true

or

false

, of course

Just did a quick test, the first example works on my end:

@section('contentFields')
    @formField('radios', [
        'name' => 'type',
        'label' => 'Article type',
        'default' => 'long_form',
        'inline' => true,
        'options' => [
            [
                'value' => 'long_form',
                'label' => 'Long form article'
            ],
            [
                'value' => 'video',
                'label' => 'Video article'
            ]
        ]
    ])

    @formConnectedFields([
        'fieldName' => 'type',
        'fieldValues' => 'video',
        'renderForBlocks' => false
    ])
        @formField('input', [
            'name' => 'video_embed',
            'label' => 'Video embed'
        ])
    @endformConnectedFields
@stop

ohhh - i think i misunderstood the meaning of

renderForBlocks

- i was setting it to

true

, thinking this would cause the field to appear if the condition was met

when I set it to

false

, it worked

sorry!

No worries. Yeah, I believe

renderForBlocks

is not really mentionned anywhere else in the docs. Could be improved 🙂

cool, cheers @User

i get this error when I run php artisan twill:dev: Twill dev assets manifest is missing. Make sure you are running the npm run serve command inside Twill. How can i fix this?

Hey @User , you may be missing this line in your

.env

file:

TWILL_DEV_MODE=true

is it .env or twill.php. Because in my twill.php i have already: 'dev_mode' => true,

Sure

'dev_mode' => true

is equivalent. Perhaps your config is cached? Try

php artisan config:clear

I already did that & php artisan optimize:clear

you said earlier you were using docker, are you sure the dev server started by twill is accessible to your browser?

we are running the twill:dev command in the docker container(also using laravel sail)

the following error message is displayed as well when editing a vue file: throw new Error('$SHELL environment variable is not set.');

Try running the command like this:

export SHELL=/usr/bin/bash && php artisan twill:dev

Not sure if it's common for containers not to define this variable... it's pretty standard otherwise.

@User This Twill doesn't support php 8.0?

it does

But when i try to install package using composer, it returns this error

try removing your lock file and vendor folder and retry, this is a known issue we're waiting a fix from the AWS sdk

okay, let me try again

Hi!

how do you deal with creating mock data for twill?

it's a pain to populate manually