Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues installing Moodle plugins from moodle.org #3

Open
Jarvil opened this issue Aug 9, 2018 · 3 comments
Open

Issues installing Moodle plugins from moodle.org #3

Jarvil opened this issue Aug 9, 2018 · 3 comments

Comments

@Jarvil
Copy link

Jarvil commented Aug 9, 2018

Hello,

Some plugin creators uses the same version number for their plugin for different moodle versions.

So when you try to install plugin like this with Moodlegist it chooces the package which is at the top of the page:

Examples
https://moodle.org/plugins/pluginversions.php?plugin=local_intelliboard
https://moodle.org/plugins/pluginversions.php?plugin=mod_simplecertificate

So you can end up with a plugin that doesn't support the Moodle version you are trying to install it to.

For this reason local_intelliboard plugin cannot be installed on 3.5 Moodle ("moodle/moodle":"3.5.*",)

error message:

Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for moodle-plugin-db/local_intelliboard * -> satisfiable by moodle-plugin-db/local_intelliboard[2018090400].

- moodle-plugin-db/local_intelliboard 2018090400 requires moodle/moodle 3.2.*||3.3.* -> satisfiable by moodle/moodle[v3.2.0, v3.3.0, v3.2.0-beta, v3.2.0-rc1, v3.2.0-rc2, v3.2.0-rc3, v3.2.0-rc4, v3.2.0-rc5, v3.2.1, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0-beta, v3.3.0-rc1, v3.3.0-rc2, v3.3.0-rc3, v3.3.1, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7] but these conflict with your requirements or minimum-stability.

And same for mod_simplecertificate so it is only installable in 3.3 Moodle ("moodle/moodle":"3.5.*",) and not 3.5.

Can you do anything on moodlegist side or is this something that needs to be addressed in plugin creators side?

@mackensen
Copy link
Member

I never came up with a way to solve this; this is discussed in #1. On the local side I stopped setting a required moodle version. I should probably just drop support for moodle/moodle "package" altogether as it never worked.

@Jarvil
Copy link
Author

Jarvil commented Aug 10, 2018

So which version is currently chosen as in #1 ? a random one?

@mackensen
Copy link
Member

That's a very interesting question. Looking at local_intelliboard, they're managing their versions in a very counter-intuitive fashion. How would you even upgrade from 3.2 to 3.4? You're really not supposed to manage version.php that way. It's also strange to me that they make old versions unavailable; that makes package management with composer difficult.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants