Elgg 6.1.5 release
A new version for Elgg 6.1 is now available in the download section.
Release notes:
Contributors
- Jeroen Dalsem (4)
- Jerôme Bakker (4)
Bug fixes
- plugins: fetching settings from inactive plugins returns default 364f8b354
- output: no longer add wrong alt attribute on img tags 9de170f5f
- icons: icon is decorative if no custom icon bd0c6e444
- site_notifications: added missing aria-label on checkbox 873076a5b
- views: urls get aria-label filled with title if empty text dafd35e6d
- notifications: correctly show discussions mute notifications action 72b07aa8a
Jerome Bakker
Developer @ ColdTrick IT Solutions
Dear Jerome (and/or others),
thank you for updating the core system.
I have 3 questions about new releases and hope that someone can help me out with information:
1. Would you recommend to always upgrade to the newest version immediately as it comes out? (I currently have 6.1.3 installed.) Or would it suffice to e.g. wait for a while and then eventually go from 6.1.3 to 6.2?
2. Can I upgrade directly from (for example) 6.1.3 to 6.1.5 or would I have to upgrade first to 6.1.4 and from there to 6.1.5?
3. I found this guide about upgrading by Nikolai. Are all of those steps always necessary if I go e.g. from 6.1.4 to 6.1.5? Or could I just download the new version and upload the files that were updated (according to the changelog on Github)? Would that break something? Example:
The "notifications" bug fix is one file (mod/site_notifications/views/default/object/site_notification.php). What if I upload that updated file manually to the folder? Is there any risk doing it that way?
Thanks in advance for a reply. Keep up the good work!
elggnoob
You can upgrade directly from 6.1.3 to 6.1.5.
Yes, you need to follow all these steps.
Keep in mind that this is a proven tutorial only if you installed Elgg without composer.
Never do this, because in addition to fixing any file, the developers also reload all dependencies and update vendors.
There is a risk that you will break something.
It's the point of installing via composer.
In this case, you only had to run 1-2 commands in the console.
Thanks for the reply.
If I installed Elgg without Composer, is it possible to change that later? I mean, if I would install Composer now, after Elgg is already installed, is that an option, or would I have to reinstall everything from scratch?
I'm not sure if this is a good solution.
But if you don't have much content and data in your database, you can try it. Of course, make all the necessary backups first.
Manual installation and update is not that bad if you follow my guide.