
Community Member
April 27, 2013

Using what Thesis 2.7.1, Agility Nude 3.2.2.0. Absolutely love the flexibility and the ability to customize that Rick has built into Agility but starting to get warnings from popular plugins I am using about running on PHP 7.0.33. But upgrades to PHP 7.1+ cause issue since Agility is not compatible beyond 7.0.
My question is, is there any chance Agility will ever be upgraded again?
I hope someone can answer this. It might be that the updates needed to move to PHP 7.1+ are not that significant and I can do it myself, but that might be postponing the inevitable move to another Thesis skin or another platform other then Thesis.
If anyone has any insight I would appreciate it.
Thanks,
Allen

Moderators
Community Member
September 21, 2014

Hi
Check your Hosting client information. But I would say PHP 5.6x to PHP 7.0x. (certain server configurations can run PHP 7.2x)
Consider using PHP 7, as it offers a significant improvement to speed and memory usage over past versions of PHP. It also comes with better error handling and many bug fixes.
Before making the switch, you need to be aware of backwards compatibility issues with scripts. Older PHP coding may not be compatible with newer versions of PHP.
Using old/deprecated PHP codes or plugins may interfere for good functioning.
Pierre ( postrophe )

Community Member
April 27, 2013

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.

Moderators
Community Member
September 21, 2014

Hi
I'v received this private email (from BYOB) a week + ago.
Hi, Pierre. Rick will probably be getting in touch with you later this week and will go back to working on byobwebsite very soon. The last few months have been difficult but we should be returning to normal soon.
I'm sorry for the lack of clarity. I'd just rather that Rick explain more to you but he will be back.
No, input as today.
Pierre ( postrophe )

Community Member
April 27, 2013

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.
Most Users Ever Online: 228
Currently Online:
7 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Keith W Jones: 1401
Brian Tozer: 1004
Carolin: 979
Heidi Hafner: 478
John Cunningham: 422
Reece Morrel: 353
Newest Members:
rajul kaushik
dex175150
Gabriel Costache
shibi s
emma72784
Chris Hall
Forum Stats:
Groups: 8
Forums: 46
Topics: 6968
Posts: 34650
Member Stats:
Guest Posters: 6
Members: 6752
Moderators: 2
Admins: 2
Administrators: Rick Anderson, Rick Anderson
Moderators: Pierre Cote, Laura Nugent