you can still use the configuration approach in the latest version

I think your problem is that you have a blade file under

views/admin/blocks

that isn't defined in your config, and also doesn't have any annotation in the file itself which would allow it to not be defined in config

if that makes sense

@User by block view I just meant the one that is producing the error

I'm pretty sure that all of these are named correctly

They are all directly from the tutorial, and they are named the same as in

twill.php

Yep, looks good. Can you reduce it to just one block (eg.

paragraph

) and make that work?

Sadly no, no matter which one of them I leave the error persists, when I delete everything and just leave an empty folder,

php artisan

works again.

even if you're adding

@twillBlockTitle('Paragraph')

in the block blade file itself? there might be a bug with the configuration approach (not aware of any though), but the annotation approach should definitely work

No not quite, I'm still trying to use the legacy code. I've made a sandbox Laravel application just to get into twill as much as possible because there's a different project I'm supposed to update which uses the older version of twill.

What if you delete your current blocks and run

php artisan twill:make:block mytest

, can you get that to work?

@User Yes, that worked.

After adding directives, similar to mytest.blade.php, it works, but does that mean there's something wrong with backward compatibility?

there might be, we will check what's happening

Hey what is the best option for relationships? I want to add a

category

to my

post

. Should I add a select and pass the option via

formdata

? Or is there a better way?

@User A browser field through the built-in

related

table is my favorite option

A quick update to the docs in underway, to document this use case a bit more : https://github.com/area17/twill/blob/c6a6431d52b39eebf41c2e041e06648c9b81f18d/docs/.sections/form-fields.md#using-browser-fields-as-related-items

Thanks @User ill have a look 🙂

How load to load the featured content in my controller?

I did configure it and it seems to work but I want to render it now

I can only fund this method on the repo and nothing about buckets

Aaah it is based in the model

I see 🙂

polymorphic again, your bucket could contain multiple types

Yea gotta get used to Poly's I build application where it is not really needed but in this case it is often used and I forgot it is a thing.

Also how does Poly's affect peformance?

But now I need to query 4 buckets?

Maybe I understand it right