@dubbs - I respect what a PM is - private and as stated above, I was waiting on permission to post a breakdown of what we have been discussing in private.
So, some of the info is already known, whereby some of it was new to me until a couple of days ago:
Breakdown:
As I am not a PHP developer I contacted Jako and he was kind enough to explain changes and contact the Evo Dev team for me and pass on my questions.
The majority of modifications from MYSQL to DBAPI were carried out by Dimmy & Yama - thanks guys for the great work.
My questions were:
If I install the latest version on lets say PHP5.4 and my host changes to 5.5 or the very latest version, Evo should work as there are no MYSQL calls because the CMS is already installed and uses the DBAPI.
You have to switch mysql to mysqli in config.inc.php.
That is all in this part.
If I try to upgrade after my server was updated, it won't work as the installer uses MYSQL.
The installer uses mysql_… calls. Yes. So it won't work with PHP > 5.5 (you have to deactivate deprecated warnings in 5.5, it will work there).
Conclusion
Evo 1.0.15 would work with PHP 5.5 out of the box, if you deactivate deprecated warnings (see
https://github.com/modxcms/evolution/issues/413) or switch from mysql to mysqli in config.inc.php.
The installer uses mysql_ calls, but it has deactivated deprecated warnings in line 16 and it will work with PHP 5.5.
With PHP 5.6 the installer has to be changed and mysqli should be the default DBAPI extender.