Hello Seele,

I am sorry but we hit permission issue when trying to change the error reporting to maximum. Can you help me turn on the Error Reporting to maximum. To do this, you need to go to configuration.php, find public $error_reporting = 'default'; and change to public $error_reporting = 'maximum';, and let see what is the error reported.

Please be advise.
Thanks.

Hello Mohd Yasser,

I have done what is required.
thanks

here is the error

Fatal error: Call to undefined method JAdministrator::setHeader() in /var/www/vhosts/yogameditazionebenessere.it/httpdocs/libraries/cms/html/behavior.php on line 712

thanks
Seele

Mohd Yasser wrote:

Hello Seele,

I am sorry but we hit permission issue when trying to change the error reporting to maximum. Can you help me turn on the Error Reporting to maximum. To do this, you need to go to configuration.php, find public $error_reporting = 'default'; and change to public $error_reporting = 'maximum';, and let see what is the error reported.

Please be advise.
Thanks.

hello, I see that the request has not yet been taken over, I can kindly give support?
Thanks

Hello Seele,

The errors that you are hitting here is actually not related to EasyBlog at all. I believe you have upgraded from Joomla 2.5 to 3.3 and during this upgrade, the files were not copied over for some reasons. This is one of the results when I searched for your error message on Google, http://stackoverflow.com/questions/25023631/blank-joomla-administrator-screen-and-frontend-after-attemping-update-from-2-5

The question would be how did you upgrade / restore your site?

Hello Mark, in fact, the problem was caused by an error in ftp ... I uploaded the version of joomla 3.6 on the wrong site that has joomla 2.5 ruining everything. I asked the hosting to do a full restore (web + db) of the last available backup that is on 28 September, but if the web side has begun to function, no side administrator. host tells me that the log shows that the problem is caused by either a log or a component. Since the same problem I had occurred after upgrading EasyBlog I turned to you.
thanks

Hello Seele,

This is actually an error on your Joomla site and it has nothing to do with the component actually What you should do now is to request your host to restore to an older copy. I believe they have restored to a dysfunctional version where the files were already been replaced with the Joomla 3 files