after upgrading to 3.1 and moving to php7 the /my/ path gives an empty page

after upgrading to 3.1 and moving to php7 the /my/ path gives an empty page

by Dani Kaplan -
Number of replies: 4

I've upgraded from 2.9 to 3.1

and moved to php 7

The sites looks ok, but when I click on my courses - 

(site.com/my/)

I get an empty page. 

every thing else seems to work. 

(moving to older php resolves this issue - but what can I do to make it work udner php 7 ? )



Average of ratings: -
In reply to Dani Kaplan

Re: after upgrading to 3.1 and moving to php7 the /my/ path gives an empty page

by Marina Glancy -
Picture of Core developers Picture of Moodle HQ Picture of Moodle Workplace team Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers Picture of Testers

Empty page usually means that there is a fatal error and you have error reporting/display off.

You can either check the apache error.log or enable developer debugging and error display in moodle.

There may be many reasons for the fatal error after the migration to php7, you may be missing some libraries, some plugins may be incompatible with php7 and so on.

Please refer to documentation: https://docs.moodle.org/dev/Moodle_and_PHP7

Average of ratings: Useful (1)
In reply to Marina Glancy

Re: after upgrading to 3.1 and moving to php7 the /my/ path gives an empty page

by Dani Kaplan -

Thanks, I'll try to enable error display and trace what caused this issue. 

(my only problem is that the site is active, I'll have to do it late at night smile 


Average of ratings: -
In reply to Dani Kaplan

Re: after upgrading to 3.1 and moving to php7 the /my/ path gives an empty page

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
It is explained in https://docs.moodle.org/en/Debugging.
Average of ratings: Useful (1)
In reply to Visvanath Ratnaweera

Re: after upgrading to 3.1 and moving to php7 the /my/ path gives an empty page

by Jean-Nicolas Gautier -
Did you found a solution? I've the same issue when moving to php7.
I downgrade to php5 until I find a way to fix this.
Average of ratings: -