Saturday 16 of August, 2025
Still some way to go as yet, but the anonymous display is working in the main on Phpgedview. The Ancestry Chart is not displaying properly which I think is a JavaScript Ajax problem and I've disabled the paper reports as that is an almost separate package which is reliant on a pdf library that also needs a fairly major re-write.
The thing that was slowing me down originally was the level of JavaScript that was being used, and it was throwing a lot of errors. I've addressed silly things like the large number of <script"> tags, for which I've not been able to find an explanation, but they need to be clean <script> at least until I can get the nonce bit working. phpgedview is side stepping the Content Security Policy header at the moment, but at some point I will strip the header and footer wrappers and make the main body a proper central module on a bitweaver page. The navigation bar also needs to become a separate bitweaver module, but that should be relatively simple now that I know how it is actually built. It may actually be a lot simpler just to replace it with a stock bitweaver menu bar which can also be tailored for the type of user.
One more urgent area is ACTUALLY getting updates and additions to save. It is creating the correct GEDCOM object but as yet not writing it into the master or updating the database. I cheated initially. While the bitweaver installer is happily building the set of tables, populating it by uploading my GEDCOM master is not happening, so I hit Flamerobin and cut and pasted the contents of the old database into the new empty one. THAT is an area where I am at home and can hand tweak the raw Firebird database easily. I've actually ported it over twice, but the second time all of the insert files were already in the Flamerobin history so it was a lot quicker without the 'copy as insert' stage. Another fairly important step is to switch to using the bitweaver user rather than having a second login. Since the user already exists it is just a matter of replacing the checks with one's that use the $gBitUser global, so should not take to long to switch. However there is a second layer of security which can be modified for each GEDCOM file and that builds it's own .php file to control it. Again is should simply be a matter of the correct variables being used but some of it is hard coded 'define' statements which is a little more work.
It was the second anniversary of James's untimely death on the 10th August and I had hoped to have got that information added before hand, along with my parents who both passed away last year. So that is the next more urgent step ...