soo.. i need to public setting repository from vendor?

no, SettingRepository is a class from Twill that you can import in your controller, nothing to publish

oh ok that make sense

if i want to add more inputs(keys) i only need to edit database and setting form?

no need to do anything with the database for settings, you only need to add form fields to the form blade file

i see, i will check it latter Thanks again 😄

Hey! Is there a way to apply some validation rules after save even when the translated entity is not Activated? simple Example: Let's have an Article. It has a Title (string 100) and Content (string 300) and it's translated for 2 languages (german, english). We create a validation rules - both inputs are required and max is 100 and 300. Now the validation rules aren't applied if the translation doesn't get Activated. So if the Content input is filled with 500 characters, it throws an error that "Your submission could not be processed." (bacause it can't fit into DB of course) I would like to apply some rules (max) even if the translation is not Activated so it doesn't throw this generic error but a Validation message is shown

Hey @User, you're right, the translated validation rules seem to skip non published languages. I think this should probably be changed internally but for a quick fix, you can specify your translated rules more explicitly, e.g. :

public function rulesForUpdate()
    {
        return [
            'description.en' => 'required',
            'description.fr' => 'required',
        ];
    }

actually this is intentional so that editors can publish languages individually without having valid content in languages that are not published. we could introduce an option in the

rulesForTranslatedFields

helper to remove that when preferred.

@User Makes sense, I see that both use cases can be desirable.

I understand this but also there have to be rules so publishers don't break database rules

thanks, I'll use this in

rulesForTranslatedFields()

first parameter. It seems it does the job

Cheers bro, that worked! Sorry for the late reply.

No problem, I'm glad it worked.

Hi, i have problem with New module.. i created module by command "php artisan twill:modules case", i added module to twill navigation and admin route, next i make migration and when i try to open module in admin i get "syntax error, unexpected token "case", expecting variable " what is: public function __construct(Case $model)

case is a reserved word in php

AH offcourse.. veriable..

Hey 👋 Is there a way to use a browser within a repeater with the "new" $relatedBrowsers = [...]; ?

hey @Red.js, do you mean repeaters with a model? If you are using the relatedBrowsers in the repository of the repeater model you're saving, it should work

Yes - I have a repeater for my Model (Variant) inside my Model (Product) and inside that repeater I want to use a Browser for another Model. But when I try to add something in that Browser it won't get saved. the Browsers name is set with dot notation so that the options come in correctly. I tried adding the browsers module name to $relatedBrowsers to both Models once, but i guess in Variant should be the right way. but saving doesn't work (no error). On Reload the Browser relation I set is gone 😦

dot notation in a browser name is not going to work I'm afraid

relatedBrowsers should be set on the variant repository, that's correct

you shouldn't need dot notation though

Hi all, how can i use "menus" for all content of site?

you want to build a navigation menu in your frontpage ?

yes

ok but how can i render it

I think we already had that discussion, no? you need to send a variable to the view that outputs your navigation markup. That variable is a collection of menu records that contains menu items. So it is about iterating on it and rendering links. not sure how we can help you build your html. do you have that working with static data?