We’re proud to announce Elgg 2.0 is now available!
For end users, 2.0 fixes several bugs and adds some small improvements.
For site owners, 2.0 includes numerous performance improvements, allows most static resources to be served without the overhead of PHP, and cleans up the plugin management page.
For plugin developers, 2.0 eases working with views, referencing static assets, and replacing the logic of individual pages. It also makes Elgg installable as a composer dependency (allowing a site-specific start.php and views directory). A thorough guide of changes that may affect you is available.
See the changelog below for more details. While there are some major changes under the hood (including the removal of a lot of old APIs), it’s far from a radical departure. Many plugins properly updated for later 1.x releases will continue to work on 2.0.
It’s our hope that 2.0 paves way toward a new focus on end user experience. We think the API improvements--along with what’s coming in 2.1--will make these big challenges easier to take on.
Many people helped to make Elgg 2.0 a reality. Developers are listed in the changelogs, but the bug reporting and feedback we received from many others was essential. We released eight preview releases over 5 months and got useful feedback all along. Thank you!
(See the Changelog for Elgg 2.0.0 here)
Upgrading? Don't forget! Upgrade to each 1.x minor release first. From 1.12 you can upgrade to 2.0.
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.
I have been working with 2.0 betas for a few months now, and launching the first 2.0 site in the next couple of days. There are two more in the pipeline. I must thank the core team for all the hard work, this release is a great stepping stone, and has already made developers' lives a lot easier, and opened up doors for many new advancements. :bow: It's breathing new life into Elgg, and I am excited about the new beginnings.
Our site is currently running 1.9.7. Would it be reasonable to go directly from 1.9.7->2.0, or am I likely to run into a lot of upgrade issues by skipping 1.10, 1.11, and 1.12?
Wow I'm falling behind, I haven't developed anything for 2.0 yet.
Congrats on the release. However, after install, I cannot activate any plugins. I get the notice:
Form is missing __token or __ts fields
Additionally, when clicking on "Statistics, Users, Settings" links are unresponsive. This occurs on MAMP and live server. Both on Mac: Safari, Chrome, Firefox, and Windows: Firefox, Chrome, Edge.
I had no problems with the previous RCs.
Regards
@Starphysique Can you please post this to the Technical Support group? Include any relevant messages you get in error logs.
@Josh upgrade only 1 minor release at a time (docs), so up to 1.12, then 2.0. I'll add this to the announcement.
The broken installation package should now be fixed and javascript should work again. Give it another try!
Elgg 2.0 with Docker: https://hub.docker.com/r/keviocastro/elgg-docker/
Downloaded from the download page and the folder says elgg-2.0.0-test. Should I be concerned about this version from the official download page?
Thanks core team for all your hard works..
A big congratulations, guys!
Awesome, I am going to test it now. I hope the plugins work for this version :)
Thank you. Great work.
Just upgraded from 1.8 to 2.0 (of course did all version upgrades in between as well) - worked quite smooth. Will go live with the 2.0 version in the next days.
Is this Elgg 2.0.0 is okay to use on live site? I just can't wait to use it :) Is that safe & okay to use it please ?
I upgraded fine.
I was learning how nginx works ,as part of it I upgraded this release on nginx. it was smooth.
Very happy to see this milestone reached! Many thanks to the folks who saw this through to the end and helped make it happen.
@kisssssss4ever yes, you can use it on a live site!
Since 2.0 is out now, will the dev team make UI/UX enhancements now? Or what is the next milestone?
@Cim I hope so but no one dictates what contributors choose to focus on. Due to backwards compatibility, some front end changes can't be accepted during 2.x and will need to be packaged into plugins (at least temporarily).
I'm currently on 1.10.4, can i upgrade to 1.11.x - 1.12.x then to 2.0?