Bitweaver - Phpgedview - Bugs

Listing the things that still need doing on phpgedview port. There is still a question as to how far to go porting and this TODO list concentrates on the ideal, but it may be a long way off, so as long as I can get back to updating a more standalone package that may be as far as it goes. 

1. The first step is to move the index folder which contains all of the GEDCOM data into storage so it can be backed up while the code remains as a link to the base Bitweaver code.
2. Save to update the index directory is not currently working, so I am stuck with the legacy material. Obviously making the update process functional is a critical step. What I do remember about this is that changes are not pushed to the main GEDCOM file, but rather staged via a php updates file which an admin can then commit as a whole, or individually as information is checked. I don't think this file is currently being displayed properly in parallel with he live data, but it is perhaps being updated. Something to start from.
3. Report display is not functional and seems to be reliant on a third party package that still has to be ported to PHP8.4. It may be easier to 'borrow' the report generator from webtrees and come up with a tidier integration.
4. Start to build Smarty5 templates and modules which can be incorporated in other bitweaver content.
5. Move admin over to the bitweaver management tools.