Well the title says it all?
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.
- iionly@iionly
iionly - 1 like
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 1 like
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 1 like
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 1 like
- Naol-Eon@naolsi01
Naol-Eon - 0 likes
- iionly@iionly
iionly - 0 likes
- Matt Beckett@Beck24
Matt Beckett - 0 likes
- Naol-Eon@naolsi01
Naol-Eon - 0 likes
You must log in to post replies.https://elgg.org/blog/view/2414218/elgg-200-is-released
One of the biggest benefits is the ability to install Elgg as a composer project. This allows the composer.json file to hold information of all the used third-party plugins, so it is trivial to make an identical duplicate of the site (from development to production, or from developer to another),
Another feature available only in Elgg 2 is the ability to link the cache directory from dataroot to the installation directory. This allows the web server to serve cached files directly from disk without the need to use PHP for handling the request, which makes it more efficient.
Composer also makes it much easier to keep all the source code updated. Instead of manually updating Elgg core, third-party plugins and all possible dependencies one by one, you can give a single composer command to take care of it all:
And that's it! All the code gets updated automatically to latest desired version.
And you guys are saying this all can't be equalized via plugin?
No, it can't.
If you think you can implement all the changes of 2.0 in a plugin, feel free to try...
No, there's no way to do that in a plugin.
Thanks Guys!