Twill

Hi <@865606995544375337> yes you can put 1 or multiple repeater fields of different types in a block to achieve what you're looking for

Thx for your answer ifox. Can I call this in this line: @formField('repeater', ['type' => 'full_width_image_item']) and separate the different type with a comma?

oh no sorry, there's no multi type repeater

you can put multiple formField repeater in a single block is what I meant

and you can use conditional fields if you need a repeater that can take many forms if you will

we're working on nested blocks for Twill 3 though

Oke thx. Nested blocks will be helpful. Then I'll have to be patient for Twill 3 😉

you can already play with it with 3.x-dev

https://github.com/area17/twill/tree/3.x
https://github.com/area17/twill/pull/1481

im having this error because `name` column instead of `title`

i already did `protected $titleColumnKey = 'name';`

do i have to define `title` field in my model and db table anyways?

No <@713238304954384404> but I think you need to set 'name' to be your slug somewhere.

```
    public $slugAttributes = [
        'name',
    ];
``` 
in your model

If you have specific questions (or bugs) you can also ask in <#989876822323908608>

Hi guys. Does Twill have the scheduled publish of the pages? For ex. I created the page and want to publish it on specific time

Hi <@168032303002419201> for sure, in the generated migration you may have noticed some commented columns, `publish_start_date` and` _end_date`. If you create those and add them to your fillable, the form sidebar will have datetime pickers. Then you can use the `visible()` scope when retrieving models to only take the ones that are currently published.

Thank you <@479379745856028705> . Do you have an example of it? Just to use it as a reference

HEy <@168032303002419201> you need to add:
```php
            $table->timestamp('publish_start_date')->nullable();
            $table->timestamp('publish_end_date')->nullable();
```

To your model.

<@385142776674910238> But if I have start date for publishing on the page, then method forSlug isn't working to get the page. Should I use something different?

forSlug is using the visible scope I mentioned earlier so if you pages publication dates are not including today that's normal

But I put the time just 1 minute for publishing, and after passing time line, it's still didn't give me anything

that depends on your timezone and the timezone of your Laravel app

dates are stored as UTC by default in Laravel

It's using the timezone in your Laravel config/app.php file

Im in UTC+3 zone. If Im schedule publish after 2 minutes, then after 2 mitutes it will be changed from scheduled on published

And if it's expired , i still can get the page from API  though forSlug

<@479379745856028705> Im just noticed one bug. The twill interface is changing depends on your local time zone, but actually page will be visible base on UTC timezone. How could I adjust interface to working base on UTC, and not using my local timezone

https://github.com/area17/twill/issues/919

<@385142776674910238> I think we should prioritize this, there's a lot of confusion around it when people start to use the publication dates

<@479379745856028705> how do we decide in what timezone we display the information in the tables?

Also, I think this also affects other date pickers?

This is what we want I guess? (db is utc as per app.timezone)

https://github.com/jamesmills/laravel-timezone

however, here is where the issue comes in.

or even from js (2.x) but in twill 3.x this is server side rendered.

I started the pr here: https://github.com/area17/twill/pull/1724 but this will affect date fields as well. Feels like a huge bc issue as well.

https://github.com/area17/twill/pull/1724 Added some todo's here as well

hello everyone  trying to upload image returns me this error

do you have any idea what might be causing this ?

If its a 500, it should show you stack trace in response or in network tab]

thanks you <@369183845238571010>  problem was extension:gd

I forgot how to add json repeater to settings page (text only)

if you recall let me know cause I don't think it is supported haha :/ as usual we recommend using singleton for anything settings doesn't support

haha, maybe I can use `formFieldSet` instead...

Hello, can I add custom vue js component in Custom CMS Pages in admin?