-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Field does not save when used from inline form #92
Comments
Same problem here can't figure out what's wrong This is not a fix but a turnaround
The fields don't save when created inline, still we'll be able to develop until a solution is found |
Tried debugging this issue, but no cigar unfortunately. I think the problems lies in the Vue component. When editing the Model from it's own resource (not trough the relation) you can see the request having the language attributes within the field. When doing the same update, but now trough the parent model and by using the Morph relationship you can see the attributes are missing from the request. Hopefully these steps help a bit in reproducing the issue. I'll give debugging the Vue components a shot. Will update here on any findings. |
Did some more debugging and found a difference when the When console logging the nova-translatable/resources/js/components/FormField.vue Lines 71 to 106 in 0dd45b7
When called from a regular model: When called from trough the Morph relationship: It seems to me that that somehow within the |
Hey @miagg! Could you share more details so we could reproduce your issue? |
Hi @eugenl1nde, Also, I tried #94 and it seems to do the job. |
Any progress on this? |
I merged the solution PR-ed by @jaap and it should work a bit better now. |
In Nova4 Inline HasOne Creation has been introduced that allows to create/update a
HasOne
/MorphOne
relation from the parent resource.However it seems
MorphOne
it is not compatible with Nova-Translatable.I can see the field and the language selectors but when I update the model, the values do not get stored.
bug.mov
There are no errors on
laravel.log
or browser console.Also, validation does work but with no visual indicator on the field or error message.
If I edit the relation outside the parent resource, everything works as expected.
The text was updated successfully, but these errors were encountered: