You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 19, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+13-4Lines changed: 13 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -595,17 +595,26 @@ To change appereance and behaviour of the page add your styles to `app/assets/st
595
595
---
596
596
597
597
# Field settings and field groups
598
-
598
+
599
599
## Orphans
600
600
601
-
Sometime playing with Rails console you might end up creating orphans, which basically are components without a field setting parent. They might cause errors in some queries and they hard to track down.
602
-
603
-
To avoid the problem run the following command from your shell:
601
+
Sometime playing with Rails console you might end up creating orphans, which basically are children of a parent that doesn't exist anymore. They might cause errors in some queries and they are hard to track down.
604
602
603
+
To make sure you haven't any orphan run the following commands from your shell:
604
+
605
605
```bash
606
606
rails binda:remove_orphan_fields
607
+
rails binda:remove_orphan_components
608
+
rails binda:remote_orphan_boards
607
609
```
608
610
611
+
## Missing Field instances
612
+
613
+
It might happen that a board or component doesn't have a field even though a field setting exists. This might be caused by an improper use of the rails console. If you're paranoid about it run the following command:
0 commit comments