Moodle Plugin Upgrade from 2.9 to 3.4

This forum post has been removed

Number of replies: 24
The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

Have you tried the newest versions of these plugins in 3.4? Often the lack of a suitable version in the plugins database just means it has not been tested (yet).

Failing that, track down the github page for the plugin (linked from the plugin's details page) and see if there is a newer 'master' version. It may not be officially 'stable' but it will still quite probably work fine for you. 

In reply to Howard Miller

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

All of them? One of them? What does "it doesn't work" look like?

Unless you tell us what happened how can you expect us to help?

In reply to Howard Miller

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

Nope. That's not the problem. You didn't do it right. The files are 'missing from disk' which means what it says - they are not there. Or, at least, not where Moodle expects them to be. 

The new files (for the plugin you mention) should be in the location enrol/approval. Oddly, your screenshot lists it as 'approver' which means it's either been renamed wrongly or that's not the right plugin. I'm guessing that you renamed it incorrectly after copying the files. 

In reply to Howard Miller

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

I couldn't either. Could it have been a custom development? Do you still have the original code (could you zip it up and attach it?)?

Can I see the entry for the plugin (in the plugins overview) on your 2.7 site please?

In reply to Howard Miller

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

Sorry... one-to-one support is my day job. 

If you don't have a backup of the original site then you might have a problem. Didn't you keep a copy of the 2.7 code in case of difficulties?

How did you upgrade? Did you just delete the 2.7 code and replace it with newer (presumably 3.0 in the first step)?

In reply to Howard Miller

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

so what's in the 2.7_old/enrol/ directory??

In reply to Howard Miller

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

...and this is the 2.7 backup? You don't have an 'approver' plugin there either. Are you *sure* this matters? As Ken has pointed out, it was showing as disabled anyway. Does your new site work without it? Have you actually tried it?

In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Ken Task -
Picture of Particularly helpful Moodlers
In reply to Ken Task

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

...but as enrol_approver doesn't seem to exist, it's down to you to explain where it came from or provide the files (directory enrol/approver/) from the backup of your 2.7 site. I don't see that there's a lot else we can do.

In reply to Ken Task

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Ken Task -
Picture of Particularly helpful Moodlers

Screen shot shows that addon is disabled (as well as missing from disk).

'disabled' means not in use.

So do you need to upgrade it?

Go to the servers Enrollment plugins:

/admin/settings.php?section=manageenrols

There's a column for Instances - indicates usage ... and enrollments ... shows how many students were enrolled by that plugin.

'spirit of sharing', Ken

Average of ratings: Useful (1)
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Nilesh Pathade -

Hi Kamlesh,

I guess this all plugins are out dated. which is not supported 3.4. But as you send screenshot  it's means "The files are 'missing from disk' which means what it says - they are not there." as Howard said. 

In reply to Nilesh Pathade

This forum post has been removed

The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

https://github.com/netspotau/moodle-local_cohort_automation

...is the middle one, although it hasn't been updated in 4 years so has probably been abandoned. This is a chance you take using optional plugins. If you really need it, you might have to find/pay a developer to bring it up to date. 


The other two don't seem to exist at all. Is it possible that they were custom developments just for you? 

Getting a bit fed up of repeating myself, but unless you can provide the old (2.7) code for us to look at there isn't much more we can do to help. 

In reply to Howard Miller

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Nilesh Pathade -

Hi Howard,

Can this possible to change version.php file and try to install? May be this is not permanent and GOOD Solutions. but I have change this and I am able to install at least... 

$plugin->version   = 2018012000;
$plugin->release   = '3.4.1';
$plugin->maturity  = MATURITY_STABLE;
$plugin->requires  = 2014051200; 
$plugin->component = 'local_cohort_automation'; 

I have try this in 3.4.1

In reply to Nilesh Pathade

Re: Moodle Plugin Upgrade from 2.9 to 3.4

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

There's no need to change version.php. The original version of that file (looking at the Github repo) said $plugin->requires = 2013051400;

3.4.1 is loads newer that 2013051400, so there's nothing in the version file to stop it installing. 

Local plugins have not changed much so it will probably work. The only risk is really it (trying to) call deprecated functions. The only way to establish that is to try it. 

Average of ratings: Useful (1)