An unexpected error occurred.

Permalink
Dear community,

I woke up this morning to this error on my website : An unexpected error occurred. An error occurred while processing this request.I did not touch my webiste for the last week and everything was working fine until now.

Does anyone know how to fix this issue??

Please not : I dont even have access to my dashboard because of this error. My concrete 5 version is 5.6.3.4

This is an urgent request, please let me know if you have any clue on what happened

View Replies: View Best Answer
ConcreteOwl replied on at Permalink Reply
ConcreteOwl
Your hosting company has updated the PHP version running on the server to one that concrete5.6.3.4 does not support.
AMohssine replied on at Permalink Reply
Hi Concrete Owl,

I thought so but when I went to check, I have found that they are still using PHP 5.6.40.

2 other concrete5 website are hosted on the same folder and they are both under Concrete 5.6.3.4 but they are working.

What do you think?
AMohssine replied on at Permalink Reply
cPanel Version 90.0 (build 14)
Apache Version 2.4.46
PHP Version 5.6.40
MySQL Version 10.2.34-MariaDB
Architecture x86_64
Operating System linux
ConcreteOwl replied on at Permalink Reply
ConcreteOwl
Are there any log files on the server showing an error?
AMohssine replied on at Permalink Reply
This error :
[20-Mar-2018 09:57:54 UTC] PHP Fatal error: Call to a member function query() on boolean in /home/bestdk/public_html/concrete/core/models/package.php on line 66

This error keep occurign from time to time
JohntheFish replied on at Permalink Reply
JohntheFish
Have you by any chance deleted a package's files without uninstalling the package first?
AMohssine replied on at Permalink Reply
I did not touch anything on the website.
AMohssine replied on at Permalink Reply
Any thoughts?
JohntheFish replied on at Permalink Reply
JohntheFish
It may still be worth updating to 5.6.4.latest from GitHub. There have been other fixes in the 5.6 legacy code base, including fixes for MySQL version compatibility (which is another thing hosts can surprise you with).

A further random problem that can manifest in weird ways is if session files or other temporary files are not being cleaned up, possibly blocked from erasure by a host OS permissions issue.
AMohssine replied on at Permalink Reply
hi Owl,

Any thoughts?
ConcreteOwl replied on at Permalink Best Answer Reply
ConcreteOwl
I would start by looking in the database 'Packages' table and compare that list with your addons in the packages folder to see if anything is awry.
AMohssine replied on at Permalink Reply
Thank you for your replay.

So I compared the DB table : Packages with the Folder Packages.

There is one file named : dynamic_iframe , existing on the folder Packages but that doesnt exist on the database.

Is that helpful??
AMohssine replied on at Permalink Reply
Hi Owl,

Finally the host fixed the problem.

What happened is that it was a conflit between an Add-on called : page-password and the new version of Mysql.

The add-on is deactivated now and the website is back online