BelongsTo relation in BREAD form has different form name than the generated name in VoyagerBaseController

[sten]

Version information

• Laravel: v5.6.29
• Voyager: v1.1.3
• PHP: 7.1
• Database: MySQL 5.7.16

Description

When I want to save a new entry of a model with a BelongsTo relationship, I get an SQL error that the foreign key is not included in the INSERT query and that no default value for the foreign key is set:

SQLSTATE[HY000]: General error: 1364 Field 'faq_category_id' doesn't have a default value (SQL: insert into `frequently_asked_questions` (`question`, `answer`, `updated_at`, `created_at`) values (ksdjkdj, <p>skdjlsjdjskl ;kjsdldksdjklsjdkljs</p>, 2018-07-30 18:36:38, 2018-07-30 18:36:38))

This is something that happened after I upgraded from Voyager 1.1.2 to 1.1.3. I did not change anything on my BREAD. I removed the relationship once and then reset it but the same occurs again.

I have been debugging this a bit and found out the following. When a model has a BelongsTo relationship, it appears my blade view generates a different name for the field in the BREAD form than the VoyagerBaseController expects. For example, in the BREAD form and hence also in the request, the field name for the foreign key is faq_category_id (which is also the column name in the database table). However the $row->field variable in the function insertUpdateData has the value frequently_asked_question_belongsto_faq_category_relationship. I am wondering where the difference comes from. Could anyone shed some light on this? Thank you very much!

Could it be related to the Voyager upgrade from 1.1.1 to 1.1.2 to 1.1.3 that my project went through? Do some new assets or views need to be published? Or some command run? I check the installation command but it does much more than what I need (e.g. run database migrations).

[sten]

It appears the BREAD field of the foreign key should also have the visibility Add, Edit and Delete...

This is quite illogical/counterintuitive, since to me the visibility of the foreign key field means that the foreign key field would be shown as a text box (or whatever widget) in the create and edit forms of the BREAD.

Here is a screenshot of my BREAD configuration for a frequently_asked_questions model with relationship to a faq_category model:

If all visibilities of faq_category_id are disabled, you get an SQL insert error. This is easily reproducable. I just reinstalled laravel & voyager to test this.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you have further questions please ask in our Slack group.