Bitweaver Bugs

Created by: Lester Caine, Last modification: 11 September 2025

Need to sync this with pages such as lsces site bitweaver bugs tracker but starting point now is github kernel codebase.

I have now started to create a separate page for each package, and these will be supported by a new description file with links to the historic material.
( Page title style ... Bitweaver - Package and Bitweaver - Package- Bugs )

  1. Blogs
  2. Contact
  3. Fisheye
  4. Kernel
  5. Phpgedview
  6. Protector
  7. Search
  8. Themes
  9. Wiki
  10.  

These are a few things that have now been cleaned up on the live sites. While they could be assigned to a specific package, they are a little cross package. This is mainly core Kernel and Liberty functions with a little Themes(Smarty)

  1. Dates being displayed as second count on some areas This was simply I'd removed the 'bit_short_datetime' tag in the smarty template probably while the date stuff was messed up. New bug is to sort date handling better as too many libraries used. Would prefer to use ADOdb as a base here.
  2. Style sheet needs to hide list numbers on the backlinks list. This is a theme problem which is different for each site. Again a little hackie and need to basically create a better generic style sheet to override the stuff from colourstrap.
  3. The user protection settings are messed up a little so a couple of checks such as if pictures can be displayed have been disable temporarily so all pictures can be seen. Need to check the permission grid, but that page is one of the admin tools that is still not functional.
  4. Lots of other admin pages need to be reworked to the new format. Most pages have now been converted but still need to verify all funtions are operational.
  5. Error checking throws warnings about stuff that in the past was simply ignored. Essentially having to add 'empty' checks where in the past that simply happened automatically. Having now in many places to create dummy arrays to avoid warnings about 'null' arrays but in practice some of that did need looking into anyway. Only enable elements of the smarty templates if the content actually exists, but this is a problem when one actually want to add that information.
    In many cases this was just a matter of returning to the original 'Content' object information. Several different 'copies' had appeared in different packages, but a move back to simply using 'Content->mInfo' directly sorted a lot of the problems out.
  6. Titles on right hand modules are not displaying properly on all sites. lsces.uk they all appear as 'Global Search'. Know that the problem here is an incomplete conversion of the way module parameters were passed and currently not sure what is and is not fixed.
    This was actually another of the mixed copy array problems. $moduleTitle was not being populated much of the time as it was still using the old $module_params array rather than the new $moduleParams format. In this case, why not simply use the $moduleParams.title value directly.
  7.