Are we talking about self nested or parent-child?

parent child this is

In self nested, we have

showOnlyParentItemsInBrowsers

Ok

I think we've been using the

adminEditUrl

accessor on the model manually for this use case

How would that fix this? 😄

it wouldn't in your case, my bad

Managed to fix JSON browser data to generate, but now CMS returns 404 for that route, I mean wtf 😄

Seriously, why is thing happening. If I override

browser

method or directly manipulate returned data with something else then

Response::json

endpoint is reached and data is returned on GET request. But if response is returned via

Response

facade, CMS gives 404 on that route. Any idea?

what do you mean by response facade?

Lost too much time on this, gonna implement alternative sadly.

you said: if response is return via response facade, CMS gives 404

do you mean another method than ::json?

I fixed it, but not so great solution. Manualy override of all browser feature methods and concat all to make a JSON response.

Finaly made it to work as it is, but definetly something from L9 is causing this, since this project was on L8 few days ago. 😄

Good afternoon! Previously, a question was asked about field validation in this order: blocks->repeaters->field. I found a way to validate such fields, but there is a problem with displaying error messages. How is the output of errors organized under the field (which has a red color)?

class TestRequest extends Request
{
    public function rulesForCreate()
    {
        return [];
    }

    public function rulesForUpdate()
    {
        return $this->rulesForTranslatedFields([
            'blocks.*.blocks.repeater_main_banner.*.content.color' => ['required'],
            'blocks.*.blocks.repeater_main_banner.*.medias.image'=> ['required']
        ], [

        ]);

    }
}

hey @BA7YA Could you test https://github.com/area17/twill/pull/2047 for fixing your issue https://github.com/area17/twill/issues/1957 ?

You can use https://github.com/cweagans/composer-patches with https://github.com/area17/twill/pull/2047.patch

@Harings Rob Nice solution with deleting fields' values , thank you!

It works? 😄

By the code - seems yes, but need to update the app and check:)

Hi! Thank you very much! It's working!

awesome!

nice, will tag a new 2.x version today as well

I found one bug with fix in frontend/js/components/ConnectorField.vue file. After this fix , second level of condition fields are not working . For example : 1) I have I select with colors (blue, white, black) 2) Below I have checkbox which will show up when selected color is white 3) Below checkbox I have input which will show up when checkbox above is true After fix it's stopped working, like if you will tick checkbox to true and then select different color, input still shown and not hidden

I am curious if this was ever supposed to work, might have been an side effect of the regression we fixed 😄

you are putting connected fields inside another right?

Right!)

@BA7YA https://github.com/area17/twill/compare/backport-connected-field-fix?expand=1 this should fix it