When I add columns to the User database table, and update the BREAD accordingly, they are not reflected in the edit view.
I could modify the generated view in /storage/framework/views/, but that seems like a bad idea.
Would this require manually overriding the views?
@AdrianKuriata, Issue 1100 is not related to this.
@stinklikeonion, Please review the Laravel documentation on how to override package views. Though I don't believe this would be necessary for your specific issue. Please provide a screenshot of both the BREAD editor for that table, as well as the edit form view.
I'm fine with overriding the views if need be. But I'd certainly prefer to use Voyager's bread system. It just does not appear that the edit view pulls from the same file on users as it does for all the other db tables.


Unfortunately, Voyager does use custom views for the User model. You can find these under vendor/tcg/voyager/resources/views/user/
Found a way to get this to work. It's painful, but ends up working out (nothing else tried above, or in #1100 worked fully).
Add your custom columns to your database
Create a view file to include the new columns you've created (add the inputs to the form, match the name exactly).
Take screen shots, or record the field values, on the "Edit BREAD for users table' page. It is found at 'Dashboard>Database>Users>Bread>Edit'.
DELETE BREAD for the users table.
Click the 'Add BREAD to this table' link, and match settings backed up in step 3 above.
Go to your 'Roles' page, and add back all permissions regarding the Users table and views.
This will add all your custom columns to the Bread, and let you set permissions for the new columns in the users table. It's cumbersome, but it works.
(edited to remove suggestion to edit core files). Adrian, you must be missing a step in the explanation, couldn't get it to work using your way. thx.
Those steps are way more complicated than they should be. Please don't suggest anyone edit files under vendor (except perhaps temporarily for testing purposes, or similar). Please see my previous comment for instructions on how to properly override views.
Additionally, you shouldn't have to delete and recreate the BREAD settings. All database table columns/fields should automatically show up. If they don't, you should be able to just "edit bread" for that table, and save again after configuring the new fields. You will, however, still need to override the view as I mentioned in a previous comment.
I think my solution is the best, don't editing vendor original Voyager files and working perfectly. But what i know :D
Hi @bbowser, just to let you know that currently we can order BREAD items. It's a recent feature.
Like @fletch3555 mentioned, never update vendor files!!
so it麓s necessary to make a custom User edit-add to include custom table columns to the user bread view?
You can override users.edit-add to just include bread.edit-add
Browse View is not overriden, just add your columns thorugh BREAD.
how to include a field like user has many addresses or user has many documents? How could one include this type of field? Inline?
Where I could find some examples?
Thanks...
This issue has been closed for ~18 months... please ask in slack or open your own issue
Most helpful comment
Found a way to get this to work. It's painful, but ends up working out (nothing else tried above, or in #1100 worked fully).
Add your custom columns to your database
Create a view file to include the new columns you've created (add the inputs to the form, match the name exactly).
Take screen shots, or record the field values, on the "Edit BREAD for users table' page. It is found at 'Dashboard>Database>Users>Bread>Edit'.
DELETE BREAD for the users table.
Click the 'Add BREAD to this table' link, and match settings backed up in step 3 above.
Go to your 'Roles' page, and add back all permissions regarding the Users table and views.
This will add all your custom columns to the Bread, and let you set permissions for the new columns in the users table. It's cumbersome, but it works.
(edited to remove suggestion to edit core files). Adrian, you must be missing a step in the explanation, couldn't get it to work using your way. thx.