Forced plugin upgrading

Forced plugin upgrading

by Alessio Niespolo -
Number of replies: 19

After login in Moodle with my credentials (administrator profile), an "Upgrade key required" message appears. I insert the correct key but the following page appears:


When I press "Continue", the following page shows me the plugin list:


But I don't want to upgrade any plugins. It seems it's not possible to skip this page and open the home page after login.

How can I open the home page after login?

Average of ratings: -
In reply to Alessio Niespolo

Re: Forced plugin upgrading

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
It's not asking you to upgrade them. It's just telling you that they are available.

Something must have triggered the update, though.
In reply to Howard Miller

Re: Forced plugin upgrading

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers
Yes, and normally you get the option to cancel the upgrade from this screen which is very strange...I suspect maybe someone manually replaced the folders on the server with the new ones - is there a reason you don't want to just go on with the upgrade?
In reply to Emma Richardson

Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
Could you please give me more details on "manually replaced the folders on the server with the new ones" ?
I would not update the plugins because it could require the updating of the database, but it's better the database is not updated.
In reply to Alessio Niespolo

Re: Ri: Re: Forced plugin upgrading

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers
1. When it says it will update the database, it just means that it will update the database related to the plugins, i.e it will just change the entries in the database to reflect the new plugins - it is not doing a full database server upgrade. After making sure you have a backup, I would recommend updating the plugins.
2. If you want to stop the message and really don't want to upgrade, you need to download the original versions that you had of the plugins and copy them over to the related folder on your server (e.g. mod plugins, will be in the moodle/mod folder, blocks will be in the moodle/blocks folder etc...)
In reply to Emma Richardson

Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
I'm wondering if the activation of the plugin check may cause some problems, considering also that I've not installed the plugins and Moodle lists some required plugins in the plugin's check page. Indeed when a message is created under the Announcements in a course, the emails don't arrive anymore to the users. I've not changed any settings in Moodle (ex. "Forced Subscription" was already set). The Scheduled task should be "Forum" and the status is "ASAP" from some days:



I think the email doesn't arrive anymore because the status is "ASAP", but why the status don't change?
In reply to Alessio Niespolo

Re: Ri: Re: Forced plugin upgrading

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers
Is cron running?
In reply to Emma Richardson

Ri: Re: Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
Moodle is installed on an unix server and there are some schedulated scripts in the crontab that runs each day successfully. So the cron is running if you mean the crontab.
In reply to Alessio Niespolo

Ri: Re: Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
I've discovered there is also a .sh script that runs this command:

/usr/bin/php -c /etc/php.ini ./htdocs/admin/cli/cron.php > ./logs2/cron-moodle-$(date +%Y-%m-%d:%H:%M:%S).log

But the .log file contains only this message: "Moodle upgrade pending, cron execution suspended."
I think the emails are not sent by the announcements because the cron is stopped, right?
I would not change the .php code of course. So am I forced to update the plugins or it's possible to execute a cron without the cron.php ?
Could I install only the required plugins instead?
In reply to Alessio Niespolo

Re: Forced plugin upgrading

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
> I've discovered there is also a .sh script that runs this command:
> ..

Where?

You might want to compare with https://moodle.org/mod/forum/discuss.php?d=431756#p1737341. Of course your directory paths will be different.

In reply to Visvanath Ratnaweera

Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
> Where?
It should stay in "Site administration -> Server -> Environment". I say "should" because I cannot see that page anymore at moment, but the page Server checks appears: it's the list of some components to install.
So Moodle doesn't allow to show the "Environment" section without installing the required plugins.
In reply to Alessio Niespolo

Re: Ri: Re: Forced plugin upgrading

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
>> Where?

> It should stay in "Site administration -> Server -> Environment".

That calls shell script? When I do it in my Moodle, Rel. 3.9, I see the browser kicks mysit/admin/environment.php. Very odd.

> I say "should" because I cannot see that page anymore at moment, but the page Server checks appears: it's the list of some components to install.

There is no Continue button below all that, to move forward with out installing?

> So Moodle doesn't allow to show the "Environment" section without installing the required plugins.

A healthy Moodle allows that. I can't remember getting stuck there. Of course you can (half) install broken additional plug-ins and get stuck.

If you ask me, listen to Emma!
wink
Average of ratings: Useful (1)
In reply to Visvanath Ratnaweera

Ri: Re: Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
I've discovered the plugin installation was not completed, because the user missed to finalized it by pressing the button "Update Moodle Database Now". I've pressed it and completed the pending operations, so the "Update key required" has disappeared and the cron started successfully.

>That calls shell script?
Yes I mean that call. I don't understand why cannot see anymore the section "Site administration -> Server -> Environment". The page is environment.php

>There is no Continue button below all that, to move forward with out installing?
No there isn't and it's not possible any actions in that page, it's just a list of the checks.This is the export of the page content
In reply to Alessio Niespolo

Ri: Re: Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
I had a mistake, because I was searching about some cron settings (like the job that execute the schedulated task) in a wrong page (Environment)! I've found it anyway
In reply to Howard Miller

Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
What kind of event could trigger the update of the plugins?
In reply to Alessio Niespolo

Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
An user tried to install the plugin Vimeo but the installation didn't completed. Could it be the reason of the trigger of the plugin's upgrading?
I'm also thinking that if some user pressed the "Check for available updates" button, it started the Plugin check and this could be another kind of trigger.
In reply to Alessio Niespolo

Re: Ri: Re: Forced plugin upgrading

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers
They apparently clicked the button to install all updates and then didn't complete...
In reply to Emma Richardson

Ri: Re: Ri: Re: Forced plugin upgrading

by Alessio Niespolo -
Yes, I've completed the pending plugin installation and the "Upgrade key required" message disappears after login.
But an issue is not still resolved: I don't see the right page by opening "Site administration -> Server -> Environment" anymore, as said before.
But there is only a list of the "Server Checks". I've exported that page here for understanding what I mean.
In reply to Alessio Niespolo

Re: Ri: Re: Forced plugin upgrading

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers
So, go into the mod folder on your server and delete the vimeo folder (I am presuming it is an activity) - that will fix your upgrade screen.