Is this a bug or me not following the instruction correctly?

singleton should be auto seeded by default (when trying to access them for the first time in the CMS) unless you configured it otherwise.

you should still be able to call that from artisan tho

did you try providing its actual namespace? since Laravel only looks in the root database/seeds folder

Migrate your database & seed your singleton module:

    php artisan migrate

    php artisan db:seed AboutPageSeeder

Enjoy.

😵‍💫 Okay, I forgot about the namespace, I just copied what the instructions say on the terminal, thankyou

👍 we could make that instruction dynamic if the singleton is created as a capsule

Hi, we are heading to choose a cms for our next few project. I am currently building a demo system with Twill, and as I see, it is a really nice and simple system. Meanwhile I have some issues, which I cannot solve and I haven't find any solution in the docs. Maybe it is my fault, but please help me.

I added a block editor, with quote, text and image, but the quote does not appear in the list. Is there any other stuff, which I must set to use other block editors? Only text and image works for me

Hi @alitak these are default blocks provided as a basic example, you are meant to create your own blocks in Twill. There are a couple examples you can enable if you find them useful, by updating

twill.block_editor.use_twill_blocks

which currently defaults to

['text', 'image']

.

in

config/twill.php

oh, i see, thank you. I will check the configs

I have an other question for the blocks. Is there any way to define translatable fields within the form blade?

Or I must create custom block editor for the translatable fields?

'translated' => true

on the fields you're using in a block is all you need

yes, on the formField it works like charm, but if I want for example to translate the text block editor, can I define it from the form blade?

Do you mean the whole field? As in creating different blocks per language?

if you mean on the text block that is provided by default, you'd need to create your own text block with translated true on the field you need translated

your own from resources/views/admin/blocks will take precedence

ok, I see

maybe this should be a nice improvement in the system, if i could define some formField parameters within the blocks 🙂

i will create custom block, yesterday I tried it and it was really easy

do you mean from

@formField('block_editor')

, being able to pass options to the blocks?

Like this https://github.com/area17/twill/issues/1688?

for example, yes

or like this for translated field

ok yeah I see

or any other parameters for the inputs

can you leave a comment on that issue with this idea?

yes, of course, thank you!

Hello, what's the advantage of using

$relatedBrowsers

property? I've been using browsers for a while but I noticed this property today (also read something in docs) and wonder what is it good for. Seems it allows using

getRelated(...)

but what's the difference from using regular relationships functions?