Welcome to the Elgg news blog
This is the best place to keep up to date with developments around the Elgg project.
|
Dec 15th |
v1.7 updatePosted in development | 2 comments As many of you will know, v1.7 is the next version of Elgg due for release. A few folks have been asking for an update on a potential release date. At this time, we are unable to give an exact date for release as we want to make sure we have tackled all the items we feel are important and ensure it is has been thoroughly tested. If you have been following the commit timeline, you will know that there has been significant development on the core. The aim is to sort out some of the annoying issues which have persisted in Elgg since v1.0 and to introduce better coding standards. We feel that it is worth taking the time to make sure v1.7 is the most stable version of Elgg so far and a solid platform for you to build upon. We are currently working with developers in the community to test, debug and patch any remaining or unexpected issues that arise during testing. If you would like to help out, please feel free to grab the nightly build or latest from SVN and report back any issues you find. Patches are also welcome and can be uploaded to Elgg's trac. I need to stress - DO NOT USE THE NIGHTLY BUILD OR LATEST SVN ON A PRODUCTION SERVICE. We would like to thank everyone for their patience. |
Dave Tosh 63 days ago
Hi William,
V1.7 is a serious release with substantial improvements that have been carried out to sort issues which have dogged Elgg since the beginning. It introduces full text search - a first for Elgg - the core API has been rewritten so it has a smarter and more efficient way of handling function calls, plenty of long standing bugs squashed, reworked user data directories so they no longer rely on the username, which was a bad call in the beginning, as well as introducing a much needed coding standard.
With all this going on, we want to make sure that this release is thoroughly tested before putting out a release candidate. We have been working with developers in the community to test and so far so good. If you have been encountering problems with your testing, you can report issues on Trac and we will take a look.
Even though the API has been reworked, it is fully backwards compatible. The only thing which might cause an issue is plugins that do not use action tokens (introduced in v1.5), as this is now a requirement.
This discussion details what is left to do.
Please note that development support requests will be deleted. If you are looking for Elgg community support, head over to http://community.elgg.org
William 64 days ago
Hey there - William here, first time caller, long time listener and general Elgg enthusiast... but what's the deal here guys? We've been waiting on this update for awhile now... I tried upgrading my dev env to 1.7 and things got ugly pretty quick - seemed like a lot of core functionality is shifted around and renamed which caused problems for various custom mods... we've rolled back to 1.6.1 and plan on launching our site in a couple months. Should we be thinking about trying the upgrade path again, or sit tight with what we have... currently tending towards to the latter...