History of Bitweaver - Wiki - Bugs

Moving new page title into Wiki Page Title box when opening a new wiki page created via a link from another page. 

When changing a title, the links are updated, but with extra (()) wrapper which I think simply needs stripping so that the |text element is also retained. Currently the new name has this extra wrapper.

 

1. Moving new page title into Wiki Page Title box when opening a new wiki page created via a link from another page. 
   The default page title had been set to '' probably to shut up a warning that it was not set, so fixed it so link title is now used if present.
2. When changing a title, the links are updated, but with extra (()) wrapper which I think simply needs stripping so that the |text element is also retained. Currently the new name has this extra wrapper.
3. A few pages are proving problematic when trying to edit. Pages that were created during the transition process are messed up in some way in the new database. Currently trying to recreate the problem pages and delete the original but even that is throwing errors.
   Had thought this was no longer a problem, but I'm getting page not found again but have seen messages about 'isLocked' not being found ... in FisheyeImage! Not sure why it should have a FisheyeImage object, but isLocked is part of the LibertyBase class that all content is built off, so it SHOULD exist, so something I'm missing :(
   11/09/2025 - Just had a repeat of a problem of a page not being able to be displayed after saving. It exists, but something is not set right which is probably the same reason for these other problems. Opening using content_id seems to solve the problem.
4. Parse process that protects links is not working properly for the {function} blocks which when editing are not returned as text.
   Not sure if this is fully addressed yet, but having dropped <pre></pre> blocks into recent pages, they were returned using the parse wrapper id rather than the content. I am assuming this will fix a problem with
   wrapper as well but need to test that!
   Some element that should be protected are failing but not sure why.
5. Need to restore the protector filtering to the edit page so that I can add personal material that will only be visible to me. (Same filter is needed on fisheye, but I need to address the problem of protecting the raw storage folders in nginx, checking with the security database.)
   protector and other liberty services have now been restored although still need to address a failure to update a database update.
6. Need to establish just what punctuation is acceptable in page names
7. More wishlist, need to start playing with books and see if they work as a better way of combining the growing database of content which are ready to be books.
8.