-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
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. |
So which version is currently chosen as in #1 ? a random one? |
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. |
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].
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?
The text was updated successfully, but these errors were encountered: