Is it possible to add a browser field to a settings section?

Only in Twill 3

in twill 2 I'd recommend a singleton module instead of a settings page

Ok

Yes, I was thinking about Singleton too

Would you recommend the https://github.com/cwsdigital/twill-metadata for SEO fields?

I don't know if it is owned by Twill or not.

It isn't but it's great and still maintained, they already added twill 3 support

Nice ok!

Hello! Is it possible to write validation rules for a specific crop of a

medias

form field? my usecase would be validating that a block-editor block with a medias form field, has at least X amount of images attached in a single

medias

form field Something along the lines of this:

php
@twillBlockValidationRules([
    'medias.cover' => [
        'required',
        'min:12'
    ],
])

EDIT: Nevermind I figured out how to target the medias.cover properly. Ended up using this:

php
@twillBlockValidationRules([
    'cover' => [
        'required',
        'array',
        'between:12,16'
    ],
])

where the medias form field name is

cover

Hi all. I'm new with Twill. I would like to get low quality placeholder for my images. Is there any way to generate LQIP after I upload an image into media library? Now I need run artisan command manually. Twill 2.12.4

I store my images locally

Hi, would i be able to include my own component view in say getSideFieldsets in my controller to show on the edit page sidebar? I would like to get some data from my model and output like a summary.

Hi @david HUN you can either decide to it in

afterSave

on a module repository, or globally using the EventServiceProvider. The

cms-module.save

event is triggered any time you make a change. So you can listen to that event and trigger the command.

Hi @jefsev you can use

BladePartial

for that

thx great 🙂

Thank you, that is an awesome idea!

How would i share variable to the view useing BladePartial? It doesnt work like normal view()

@jefsev

BladePartial::make()->view('view')->withAdditionalParams([...])

I think we should amend that to take data in the view method to avoid the confusion with a normal view method

thx again

🙂

I cannot achieve to get the nestedSlug for a nestedpage.. It only returns the top parent.. I implemented the hasNested trait, installed the package etc, so that all should work.. I also added the following in my admin controller:

protected $showOnlyParentItemsInBrowsers = true;

    protected $nestedItemsDepth = 3;

    protected function form($id, $item = null)
    {
        $item = $this->repository->getById($id, $this->formWith, $this->formWithCount);

        $this->permalinkBase = $item->ancestorsSlug;

        return parent::form($id, $item);
    }

And I also added the following to the frontend controller:

$page = app(PageRepository::class)->forNestedSlug($slug);

However it still only returns my top slug..

how did you setup the route to your frontend page controller?

Route::name('page')->get('/{slug}', [PageController::class, 'index'])->where('slug', '.*');

when you dd $slug in your page controller, do you see a nested slug?

Hi. I have problem with creating new Block (twill 3.0.0-rc4)... im following docs, created "article" block and I cant do it readable by Vue component in CMS. I allso try to append others from vendor\area17\twill\src\Commands\stubs\blocks\* but I see on frontend only two natives: image, text. I also try to move "article" block to views\twill directory and it didnt help. Any idea?

I think I know what the problem is.. I added a general navigation to my provider with a browser which loads the pages, this all works perfectly, but if I loop through the items, I don't think my item is connected to my repository so I miss this part:

$page = app(PageRepository::class)->forNestedSlug($slug);

And therefor it does not know it is a child..

Hi, for a client's website I need to display a datatable () but there's no specific formfield to do this. It's also not available in the wysiwig according to the docs. What do you recommend? All datatables contain a lot of numbers and most of them have different headers.

Hello, definitely I feel ur need, since I stumble upon this always. Twill offers currently fields to manage data, but none to only display something like tables. I resolved this by creating custom vue components, but its something Twill really needs.