After install: broken plugin enrol_imsenterprise

After install: broken plugin enrol_imsenterprise

by Gabriel Johannes Frank -
Number of replies: 4

Hi,

after installing Moodle on my Vitrual-Server I get an issue about "detectedbrokenplugin" enrol_imsenterprise as you can see in the Screenshot below.

File: /moodle/enrol/imsenterprise/lang/eng/enrol_imsenterprise.php seems to be okay.

What can I do?

Thanks, Gabriel

Attachment 2020-03-17.png
Average of ratings: -
In reply to Gabriel Johannes Frank

Re: After install: broken plugin enrol_imsenterprise

by Ken Task -
Picture of Particularly helpful Moodlers

Have to address 'red' checks.

First line says to edit config.php and change dbtype line from mysql to mariadb.

You are using MariaDB.  No restart of server services needed.

The second is a php extension ... php_intl ... that you should be able to
acquire via package manager of operating system which is Ubuntu 18.04.

https://zoomadmin.com/HowToInstall/UbuntuPackage/php-intl

The 'orange' checks are recommended.

Installing new php extension should require restart of web service so that it is aware of the new php extensions.

'SoS', Ken

Average of ratings: Useful (1)
In reply to Ken Task

Re: After install: broken plugin enrol_imsenterprise

by Gabriel Johannes Frank -

Oh. Sorry. I uploaded the wrong Screenshot. Here the new one

Attachment 2020-03-17 (1).png
In reply to Gabriel Johannes Frank

Re: After install: broken plugin enrol_imsenterprise

by Ken Task -
Picture of Particularly helpful Moodlers

Plugin enrol_imsenterprise is missing a version.php file from code directory.
And am guessing the second error result of the first.

Site not in maintenance mode as recommended before update/upgrade and right
now anyone browsing to your site is thrown into plugins check ... no login
required.

The check gets down to workshop ... standard core plugins ... but then
shows Assignment/Submisson plugins - standard core to be installed.
Ditto  for certain plugin on the rest of the check.

That means upgrade failed.

Probably best to restore the backup of code and SQL dump of DB for moodle to get the site back to whatever version it was prior to attempting whatever.

'SoS', Ken