I know I can go to PHP 7.1+ on my host, but Agility 3.2.2.2 was having issues (PHP warnings / errors on anything above PHP 7.0).  This was months ago and I did not log all the warnings/errors, but when looking in the forum here I saw another user asking Rick about PHP 7.1+ compatibility.  Rick indicated that it was on his "list" to make Agility PHP 7.1+ compatible.  I just don't think he got to it.  I actually have not checked in the last several months but I don't think the update ever happened.

So basically, Agility is the "old/deprecated PHP code" that is the issue.  I am asking if you, or anyone else knows if an update will ever happen.  Just grasping at straws in hopes of avoiding a costly redesign of multiple sites.

It's really too bad.  Rick really had something great here.  I tried looking at Chris's "Classic" skin to see if that would work for what we need to do but it is so limited compared to Rick's Agility.  It's like the difference between a low budget, base model, no option car and a Rolls Royce.  There is just no comparison. Rick could get people to pay good money for this Thesis Agility Skin if it was supported.

Very sad, all that work going to waste.  Both Rick's and all those with Agility installed on websites.  They will all shortly have to redo their sites.  Very sad indeed.

Thanks for the update.

I went ahead and updated a couple of sites to PHP 7.1 with WordPress 5.03, Thesis 2.7, Agility 3.2.2.2.  So far no glaring issues or errors.  It might be possible that Agility is in fact PHP 7.1 compatible.

I host with Site Ground and prior to upgrading to PHP 7.1 I ran Site Ground's Super-cache plugin's PHP compatibility test.  It came up with several errors for a number of very popular plugins I had installed.  It showed the PHP scripts and the line numbers that were an issue.  I was going to contact the plugin developers to see if they would fix the issues but first I decided to look at each line of code and see how big of an issue there was.  It turns out that all of the issues were really NOT issues.  As an example, one error reported that "mysql_" was being used at line ###, yet it was no longer supported in 7.1.  Turn's out the line of code was actually doing a test for "mysql_" or "mysqli_" to simply determine what version to execute.  The plugin was only searching for the characters "mysql_".  In this case, if PHP 5.6 to 7.0 was installed it would user "mysql_" commands, but if PHP 7.1+ was installed it would execute "mysqli_" commands and there would be no issue.

All of the incompatibility issues were similar and none were actual incompatibilities.  I upgraded to PHP 7.1 and will see if anything arises.  Watching the logs and nothing has been an issue yet.

I hope Rick does come back and not let all he has create slip away.  He is a great person with many talents.  I'll cross my fingers.