Posts made by Visvanath Ratnaweera

Moodle in English -> Installing and upgrading help -> HTTP 500 Error After Upgrading Moodle from 3.8 to 4.0 — No PHP Errors Displayed -> HTTP 500 Error After Upgrading Moodle from 3.8 to 4.0 — No PHP Errors Displayed

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
Were you able to resolve the issue? No wonder no PHP errors logged, the 500 error comes from the web server. Check its configuration. A simple double check is to put a test.html file in the root of the Moodle code directory and visit it in the browser. If successful put the usual phpinfo.php (single liner) there and visit it.
 
Either way, plan your upgrade path, Moodle 4.0 is not supported for one year now. The chart http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases shows your options. If I were you, after updating Moodle 3.8 to its final, I would upgrade it to 3.9 LTS. From then on you can march from LTS to LTS (4.1, 4.5).

P.S. This seems like an upgrading issue. Better suited for the Installing and Upgrading help forum.
Average of ratings: -

Moodle in English -> H5P -> The plugin mod_h5pactivity is defective or outdated; sorry you cannot continue.

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators

Updating a Moodle 4.5.6 to 4.5.8 throws:

The plugin mod_h5pactivity is defective or outdated; sorry you cannot continue.

More information about this error

Debug info: Missing version.php
Error code: detectedbrokenplugin×Dismiss this notification
Stack trace:
  • line 805 of /lib/upgradelib.php: plugin_defective_exception thrown
  • line 651 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1937 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 719 of /admin/index.php: call to upgrade_noncore()

The more info points to https://docs.moodle.org/405/en/error/moodle/detectedbrokenplugin.

Oddly mod/h5pactivity/ contains only a single file lib.php. Moving the directory away completed the upgrade.

What is happening?

Average of ratings: -

Moodle in English -> Installing and upgrading help -> Clarification on new directories -> Clarification on new directories

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
Welcome to The Club of the Confused. As somebody got confused before you let me tell you what I would do next time.
smile

Seriously, the difference is that unlike the definitive arrangement you described, now there are alternatives - and people mix them! This is the prescribed way in upgrading your Moodle pre-5 Moodle to 5.x.
 
Note: I assume your Moodle has a URL like https://example.com or http://something.example.com, but not https://example.com/something.

- Put the Moodle code in to /home/USERNAME/public_html just you have always been doing. In 5.x you'll see a new directory public/ in it.
 
- Now you have to a small change in the web host configuration: It should have something like web root, DocumentRoot, Base directory of the domain or something similar, which is currently pointing to /home/USERNAME/public_html. Change it to /home/USERNAME/public_html/public. That should do the trick.
 
- One more thing: Move the old config.php file out before the upgrade and put it back to /home/USERNAME/public_html (not to /home/USERNAME/public_html/public).

As always, get a full complete Site backup, in case the earth slides.
Average of ratings: -