Please publish a PHP script that lists all necessary changes of a Kirby website 3.x, e.g. migrated from a formerly Kirby 2.x website, (please don’t let the script change anything!!!), so that after this changes this website will work with Kirby 3.3.0+, if the debug option is enabled.
This should also examine all parts of the website that lead to error messages not visible in the browser source code but avoids showing the webpage because of that error.
So far I have found in my website code some plugins and panel-based code which do not cause any visible error messages in the normal browser source code.
Maybe it would be helpful to uncouple the corresponding error messages from the debug option, because for me it was sometimes difficult to find the respective parts in foreign code. Troubleshooting live running Kirby 3.x sites and deprecated code may be two different things in existing sites than in development sites…
I’m thinking of an additional option that suppresses deprecated code in the debug option.