hi @Sami with relatedBrowsers you do not need a pivot table that you create yourself since they use the twill provided related table, also they allow multiple modules to be selected from in the same browser field

okay, I though I'd need to create pivots anyways, that sounds good. Multiple modules could be maybe done using polymorphic relationship but why to reinvent wheel. Thanks!

yes polymorphic browsers are also possible without the related table, its just that with that HasRelated trait everything is handled for you

Hello. I have an error in SEO. When I set seo, it doesn't work and I get this error:

Hi, I was trying to search for this question, but didn't found it on discord search feature: Is there a way to set the max option on browsers to infinite instead of a specific limit?

@ifox any solution??

Hi @onepiece no need to ping with multiple interrogation points 🙂 please be patient, you posted your question 10 minutes ago

Im sorry🙏

the SEO package is not maintained by the core team, so you should submit an issue on GitHub. Is the model you're using it on translatable?

Yes its use A17\Twill\Models\Behaviors\HasTranslation;

#twill-api (understand that it is still under development)

composer require area17/twill-api

Hmm seems like an odd issue with the post install scripts. Im sure that this package handles configs with the artisan command (servers), but that is not resolved before

php artisan package:discover

which throws this error

As a debug advice, I would start by removing

json
"scripts": {
    "post-autoload-dump": [
        THIS -> "@php artisan package:discover"
    ]
}

and after that I would try to install

twill-api

and manualy I would deploy server configs. After that revert that change in composer.json.

You can also manualy copy/paste that config before install of package from

twill-api

. Also here its explained how this works https://laraveljsonapi.io/docs/2.0/servers/

thanks for flagging this, cc @patrick

also opened a #1007065780724174909 channel

Hi guys. Im trying to overwrite MediaField component (just want to add some new buttons), and i put it in resources/assests/js/components (I already have some overwrited components there), but it's not working for me. Seems like twill is not working with my overwrited MediaField and using default one

Did you run

php artisan twill:build

after that? Components are compiled into JS builds.

Of course. I’m usually using twill:dev , but this time tried also twill:build

Hi all, is there any chance, to store files to module? I generated via cli, selected to attach files, but unfortunatelly it does not work.

the model uses the HasFiles trait and the repository uses the HandleFiles trait also

i added the files input to the form and the files input appears, I can even select file, but after the update process, it disappears

Hello, you will also need https://twill.io/docs/crud-modules/models.html#hasfiles

php
// app/Models/YourModel.php

public $filesParams = ['file_role', ...];

file_role

is the name of your form file input.

ok, this part wasn't clear for me, thank you for your advice

it works indeed 🙂

btw i have checked the demo few times, is there a repo for its source code? I think it would answer some of my questons.

Sorry, but its not available. Twill company keeps it private for their reasons. But you can always link us / screenshot us page of interest and we will help you.

ok

But soon on 3x release blog example project will be released for starting projects and can be used as orientation.