1 | | For a long time I've tolerated this bug, but the time has come to fix it. My first guess would be that the zero-based indexing of fields within the fieldgroup (this concerns all fieldgroups) is to blame. BP's logic would read that the field your editing has a falsey value for `$field_order`, thus BP considers it new and pushes it at the end of the field list. Will investigate further... |
| 1 | For a long time I've tolerated this bug, but the time has come to fix it. My first guess would be that the zero-based indexing of fields within the fieldgroup (this concerns all fieldgroups) is to blame. BP's logic would read that the field your editing has a falsey value for `$field_order`, thus BP considers it new and pushes it to the end of the field list. Will investigate further. |
| 2 | |
| 3 | Edit: my guess was correct. Patch incoming. |