Changed PHP from 5.6 to 7.1 and Site is Broken
Permalink
Ok so I am looking everywhere to try and get this fixed. I upgraded the PHP through dreamhost to 7.1 from 5.6 to get ready to update my C5 install which I think is currently 5.5.1. I found one post which hinted to the same issue I am having which is here:
https://www.concrete5.org/community/forums/5-7-discussion/php7-issue...
However I am having a hard time finding out what exactly is broken as I get this code showing with no indication of where to fix the code:
Site is being hosted on Dreamhost and my only 2 options for PHP is now 7.1 and 7.2 so I can not roll back to 5.6. I have minimal php coding knowledge so any help as to how I can fix this would be very much appreciated.
https://www.concrete5.org/community/forums/5-7-discussion/php7-issue...
However I am having a hard time finding out what exactly is broken as I get this code showing with no indication of where to fix the code:
Declaration of Concrete\Core\Permission\Access\EditPagePropertiesPageAccess::save($args) should be compatible with Concrete\Core\Permission\Access\Access::save()
Site is being hosted on Dreamhost and my only 2 options for PHP is now 7.1 and 7.2 so I can not roll back to 5.6. I have minimal php coding knowledge so any help as to how I can fix this would be very much appreciated.
To add to the difficulty, some of those update steps won't run on php7 - so it will need to be updated on a clone on another system that supports legacy versions of php.
Correct, that is why I offered to do the updates for him.
My clone server has PHP versions 5.3.28, 5.6.40, 7.0.33, 7.1.26, 7.2.14, 7.3.1 and 7.3.2
My clone server has PHP versions 5.3.28, 5.6.40, 7.0.33, 7.1.26, 7.2.14, 7.3.1 and 7.3.2
Hmm
Not sure we have the correct info here, that error message you posted gave a folder path of concrete\core\permission\ and I don't think that folder path existed before version 5.7?
It still needs to be updated on a clone server though..
Not sure we have the correct info here, that error message you posted gave a folder path of concrete\core\permission\ and I don't think that folder path existed before version 5.7?
It still needs to be updated on a clone server though..
I would take you up on this offer. I just upgraded my server to PHP 7.2, and lost functionality my website built on concrete5.
I have replied to your private message...
Thanks guys for the reply. I was able to get it rolled back to PHP 5.6 so the site is now live again! The actual version is 5.7.5.1. What would guys suggest I do, or what would be proper order to upgrade it to a newer version.
Right now I have made a complete backup of both the database and directory. I know from past experience, that sometimes the update process breaks the site so I want to be uber careful in upgrading to a newer version.
I really do appreciate your time and offer. I may take you up on that sometime.
Right now I have made a complete backup of both the database and directory. I know from past experience, that sometimes the update process breaks the site so I want to be uber careful in upgrading to a newer version.
I really do appreciate your time and offer. I may take you up on that sometime.
Make a backup. Files and Database.
The rest of the process depends on how important uninterrupted running of the live site is. There are processes you could follow to guarantee zero down time, or you could flip a coin and update directly on the live site (and risk having to recover from backups if it goes wrong)
The rout to latest is to upgrade to 5.7.5.13 and then to 8.4.5. There may be another intermediate step before 5.7.5.13 you need to update through - check the release notes.
A no risk process would involve making at least one clone of the site.
Be careful if you have a lot of attributes. Attributes are often the area of update failures between 5.7.x and v8.
The rest of the process depends on how important uninterrupted running of the live site is. There are processes you could follow to guarantee zero down time, or you could flip a coin and update directly on the live site (and risk having to recover from backups if it goes wrong)
The rout to latest is to upgrade to 5.7.5.13 and then to 8.4.5. There may be another intermediate step before 5.7.5.13 you need to update through - check the release notes.
A no risk process would involve making at least one clone of the site.
Be careful if you have a lot of attributes. Attributes are often the area of update failures between 5.7.x and v8.
You need to update to 5.6.4.0 to get your site working again.
If you want this doing for you, send me a private message to establish communications.
If you want to attempt this yourself, you need to update incrementally, you cannot jump straight to 5.6.4.0 from 5.5.1