Bitweaver upgrade process

This page originated on myhomecloud.uk and now I am wrangling smarty under control I think I can see a way to prefix a page with the site, although moving all the content to a single database is perhaps a better approach and gestore the bitweaver multisite package to select the teame used based on the domain name, something that has been working nicely in the past when my Client Management customers each had their own domain such as clientX.enquirysolve.uk and that provided them with their own set of user accounts and content tailored to their own site. This is one of the reasons that the ROLE_MODEL exists in the bitweaver code base ...something I need to document better, even if it's not as nesessary today. The idea that content was restricted to a role such as clientX.user and clientX.manager is a somewhat different context to the user/groups model that was prevelent 25 years ago.

The particular target of my development work in the past couple of weeks has been to get bitweaver working with the current version of PHP - 8.4.5 - and the third party libraries that also support that. I am getting there, but need to review just where I am heading which is part of my bitweaver upgrade process. Push that back to the main codebase may not be appropriate at the moment, but actually a major part of the initial work was to move my own codebase back in line with the way the master thread had been taken. The live sites are still running a rather old configuration which is working fine, so the real questions is "Why Change It?". The answer to which is that others have been doing the heavy lifting to PHP8.4 and while I would be quite happy running 7.3, there are niggles that have been ironed out which I could simply port back to the old code, but contributing back is then somewhat restricted.

Now I just need to work out why Smarty 5 gots into an infinite loop when it calls the display function!