17th January 2018 at 9:50 am #9767
I’m not making much progress I’m afraid. The Hosting service folk were of the opinion that all the PHP startup warnings were
most likely caused from using a newer php version than your code was written for and so it is making calls to functions that are not there
so they set the PHP level for my site back to 5.5! But the warnings continue. They don’t prevent the site from functioning – outwardly correctly – but are filling the error log at an alarming rate so clearly must be sorted out. You have made it clear, Nigel, that kiwitrees is tested to PHP 7.0 so if the problem really is caused by code on my site (which I have not fully accepted yet and have called for the hosting service to do some futher checking on potential problems of their making), it is probably something to do with my ‘front-end scripts’ which were originally cobbled together in quite primitive HTML many years ago, then simply ‘topped and tailed’ to run under kiwitrees. I have looked at, and tried to understand, all the changes between PHP 5.5 and 5.6, then between 5.6 and 7.0 – but as far as I can see, most refer to functions far more advanced that I have attempted to use in my simple scripts. What I really need is an idiot’s guide to the most likely problems that will be encountered in simple HTML scripts from way back when confronted with the constraints of current level PHP. Does such a thing exist? If so i may be able to work through all my old scripts and make the necessary changes. Otherwise it starts to look as though I shall have to abandon all the family history narrative material they contain and setlle for ‘vanilla’ kiwitrees, and in time, re-introduce the narrative material ‘under the covers’ of kiwitrees (as ‘stories’ probably?).
Any thoughts on this would be appreciated.
Meanwhile – the original problem that triggered this thread in the first place – my inability to update the main HTML Block – is still there – and, having effected all the ‘WT to KT’ changes, I’m not sure that it is caused by or associted with the flurry of PHP warning messages.There is no urgent need to update it and if necessary I can take the approach you suggested Nigel – editing it in the database. But it would be good to get the ‘normal’ method working again and would appreciate any suggestions.
Ron in France
kiwitrees 3.3.9; PHP 7.3.5