Can anyone explain how composer can help verifying plugins ?
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- Gerard@gkanters
Gerard - 0 likes
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- Gerard@gkanters
Gerard - 0 likes
You must log in to post replies.It goes through all the dependencies and their dependencies, and informs you if one your the components on your site is not compatible with the others.
If you try to upgrade your site to Elgg 1.11, but there isn't a supported version of a plugin, composer will notify that upgrading cannot be done because of the missing dependency.
If all dependencies however are satisfied, it upgrades both Elgg core and the plugins for you.
Just run composer install ?
Yes. That on the first time. After that "composer update".
Starting to sound like a nice tool? :)
Using it of course requires that all the plugins you use can be found from a composer repository like packagist. And that the plugin author is using Semver and Git tags properly.
Yes, really nice tool. Not many plugin developers are using it yet unfortunately.