Elgg Blog: Elgg 1.9.0-rc.1 released
After a couple of years(!) of heavy development the core team is pleased to announce that Elgg 1.9.0-rc.1 is available for download! Remember this is a release candidate and is meant for developers and bug hunters, so please do not use this on a production site! If you haven't been following Elgg 1.9's progress, here's an overview of the main features:
- New responsive theme - aalborg_theme
- Adds image uploading from editor
- Replaces fancybox lightbox with colorbox
- Replaces Tinymce editor with CKEditor
- Liking and friending use ajax
- Removes topbar Elgg logo and made "powered by" themable
- Allows keeping group content limited to the group
- Site notifications moved into separate plugin from messages
- Various accessibility fixes
- Improved theme sandbox
- Ajaxified the discussion reply edit form.
- Alphabetize friends/friends-of, group notifications, group owned/member lists
- Adds support for simplecache minification of CSS and JavaScript
- Adds new notification system
- Changes user directories use GUIDs rather than join date
- Adds robots.txt configuration
- Adds maintenance mode
And many, many more. See the changelog for the full set of changes.
Elgg 1.9 is a major release. Developers who have been waiting to test out their 1.8 plugins in 1.9 should take this as a cue to begin upgrading those plugins. Note that back compatibility was a big consideration in this release so upgrading plugins should hopefully not be as painful as it was for the 1.7 -> 1.8 upgrade.
As always, please report bugs in our github issue tracker: https://github.com/Elgg/Elgg/issues
Thanks to the following developers who contributed to this release:
- Cash Costello
- Steve Clay
- Evan Winslow
- Pawel Sroka
- Sem
- Brett Profitt
- Jeroen Dalsem
- Juho Jaakkola
- Per Jensen
- Ismayil Khayredinov
- RiverVanRain
- Matt Beckett
- hellekin
- Jerôme Bakker
- Aday Talavera
- Jeff Tilson
- Marcus Povey
- Rasmus Lerdorf
- Brad Smith
- Hayden Shaw
- Ben Werdmuller
- András Szepesházi
- slyhne
- Facyla
- ManUtopiK
- Emmanuel
- Centillien
- twentyfiveautumn
- Janek Lasocki-Biczysko
- Ash Ward
- Arsalan Shah
- Angel Gabriel Vargas Beltran
- Tantek Çelik
- Team Webgalli
- bwoodnz
- Danny Navarro
- EC2 Default User
- Kody Peterson
- Liang Lee
Matt Beckett
Latest comments
gushbellino on Elgg Blog: Elgg Blog is moving to the community ():
Thank you for the announcement Matt.
Awesome. Congrats on the release, and thanks to all.
Thanks for the work on cutting this release, Matt!
There were a lot of contributors and new team members who helped with this release, and I want to thank them, too. I want to especially thank Evan for making an effort for the final push of the 1.9 dev.
Let the bug reports commence!
great, thanks :)
i will start upgrading my plugins today. i read through the change log and saw several entries that i didn't comprehend. such as:
anyone know what that refers to?
is there an easy way of finding the github ticket number for the changes, other than searching for the titles?
@ura https://github.com/Elgg/Elgg/pull/5916
where do you want bugs listed? here? new github tickets? or both?
my theme used full_url() and 1.9 informs me that this is now deprecated and to use get_current_url() instead.. except that function does not exist!
Great job, you all must be feeling some releave now. I will be setting up a 1.9 server for migrating my plugins
also, on running upgrade.php, i see:
however, i am not using apache and so do not have a functional .htaccess file. (i am using nginx).
Thank you to the people who have put their valueable time for this project.
Please post bugs as github tickets: https://github.com/Elgg/Elgg/issues
This is my nginx config for Elgg 1.9 that handles __elgg_uri correctly https://gist.github.com/Srokap/7dbfc423812f09a5ee43
ok thanks. upgrade now appears to function. i logged a ticket for the missing function.
Thanks everyone for the contributions. Great to see so many come together to make this happen. Let's keep that momentum going!
awesome work .. guys :D .....
Maybe i'm missing something, but where can i find
@jdalsem That feature was reverted but it is accidentally still in the changelog. We're working to remove the reverted ones: https://github.com/Elgg/Elgg/issues/6867
i am still experiencing that ckEditor is not loading.. and possibly other js errors:
http://community.elgg.org/discussion/view/1665932/19-ckeditor-is-not-launching
Drop of "Adds image uploading from editor" feature is very unfortunate. If you already have a link somewhere, current way of "link" is OK. But if not, then "first upload, then get the link and link" process is so out-of-date user experience. Regards.
Wow this is great news!
Have no fear... ColdTrick is here to rescue you! This plugins adds the upload from editor feature: https://github.com/ColdTrick/ckeditor_extended/
IIRC, the reason we chose to drop support for image uploading from CKEditor was because the implementation tied those uploaded images too tightly to CKEditor. If you ever switched back to TinyMCE or any other WYSIWYG, all the images will be gone. The ColdTrick implementation suffers from exactly the same problem so I advise you stay away from it unless you want to be married to CKEditor forever.
ColdTrick guys might also consider thinking about a more editor-agnostic solution to the image upload problem. :)
@Evan i agree, that it ties you into CK Editor, but there currently is no better alternative (embed is not the solution), and ckeditor is not that bad. We had to deal with tinymce for years also, besides, the data is still there and could easily be moved to other editors...
Something not listed here is that we're now including translations from Transifex in every new release. If you want yours added you just have to go to https://www.transifex.com/projects/p/elgg-core/ and sign up as a translator and your contributions will be included in the next 1.9 release!
Moved to http://community.elgg.org/discussion/view/1820143/no-such-file-or-directory-error-when-installing-190-rc1