ooh from CWS ok

really im blind..

2am..

there is version without taiwind?

Don't think so but that's pretty standard html to style and that's a bit out of our scope for support here. how you decide to style your frontend is really up to you

i think i have old files becouse i have site without components

If you have only one language in translatable.locales and you make a setting translatable, it does not work properly. Is this intentional or should I file a bug report/attempt a fix?

im using main branch.. not 2.5

@`Sebastlan there was no view in their main branch for the menu but I think you should dd what the view composer outputs and render that however you like

i think there's already an issue for this. It is a bug, but we also intend to refactor settings entirely to be compatible with all fields so might not want to invest too much into fixing edge cases on the current implementation

if you see a quick fix though, go for it

I found this: https://github.com/area17/twill/issues/50, but might not be 100% related. Anyway as it is in for refactoring I wont spend much time.

3.0 is in active development and soon (ish) expected?

It's main feature, the advanced permissions system, is already available to test. There will be more 2.x releases before 3.0 where we will introduce breaking changes which we are currently roadmapping and will share with the community soon to get feedback and make sure everyone can prepare for those changes (mostly naming and better defaults that have been discussed already on different GitHub threads, no structural changes). We have opened Projects on GitHub where you can get an idea of where we are going (still very much incomplete but trying to give visibility more as we go). We don't want to make promise for when 3.0 will be released but we are currently aiming for Q1 of 2022 and will actively develop everything publicly.

really i dont know what to do.. tutorials are different.. docs.. videos and files in gitgub. every project is made in diferent way

Ok @User , I will read a bit into the stories/issues on Github. Thanks for the elaborated response. And I am happy to help testing once possible.

Hey there 🙂 I was wondering if there is a way to get rid of the App\Models\ in Browsers to just have the Plain Text there e.g. in the second one just Product

@User : https://github.com/area17/twill/blob/377e5e0b27916861caa448ef899ea0e3fbeff648/src/Repositories/Behaviors/HandleBrowsers.php#L181

short answer I will say no 😄

morphmaps

if you set a morph map on your models, it will use that there

Works like a dream, thanks 🙂

it seems like saving then doesn't work anymore, currently trying to find out how to fix this 😄

@User in you database you may have old path => App/Model/Something

I aleady removed the entries from the table and tried to create new ones ^^ There is no other relation for that isnt't it ?

creating them as new ones doesn't work ^^ 😄

@Red.js how do you save the browser field in your repository?

$relatedBrowsers = ['access_recommendations', 'products']; using the related table (from 2.x doc)