Today, we are pleased to release ElkArte 1.0.5. This release fixes a number of bugs and issues that were found or reported since the release of 1.0.4. As this is a maintenance release, the majority of the updates are focused on bug fixes and increased stability. This is a recommended update for everyone running the 1.0.4 version.
Some notable updates in 1.0.5 include:
added @ mentions to the quick modify as well
fixed bbc parser not working 100% correctly with tags having multiple parameters
updated FontAwesome to version 4.4
made the packages list sorted alphabetically (instead of the "almost random" one)
added a confirmation step to the "remove like" function to avoid mistakes
fixed editing of the agreement in multiple languages
restored the alphabet strip in the members list page
fixed a query in personal messages for PSQL
fixed the local moderators in admin reports
several other minor fixes
This release follows our
semantic version (http://semver.org/) (MAJOR.MINOR.PATCH), meaning that third-point (x.x.X) releases should contain backwards-compatible bug fixes and enhancements, so for the most part you will not find new features in this release. Major new features will be reserved for second point versions (x.X.x).
Refer to the release notes (http://www.elkarte.net/community/index.php?topic=2941.0) on the forum for a complete list of updates.
Patching procedure:
For any question you may have, feel free to ask on the support forum (http://www.elkarte.net/community/index.php).
Of course you are encouraged to update to this release since it contains a lot of fixes and improvements, thank you for your continued support!
Great work. Congratulations and many thanks to the developers.
When I go to install this patch it tells me:
DAAAARN!
I forgot to update the package id...
Please download again the file, now it's fixed. :-[
I had to re-publish the release because I tagged the wrong commit... okay, I did a bit of a mess this time! xD
That works now. Thanks a bunch!
Awesome !!!
Well, the [# ] were not supposed to be there, I forgot the correct procedure was:
post the first part,
announce (with admin account),
* add the notes
ohhh well, I did so many mistakes today. LOL
goes to report bugs in release bot ;D
And the link points to the old release notes... xD
Updated the front page download link and the news fader to point to 1.0.5
Thanks! :D
What's up with:
Something odd seems to be happening, or perhaps Skull Knight is your alter ego....
Update: Never mind, I found this:
It was a little unsettling when I first saw it.
Brilliant !!
I tried to follow the link in email ( https://github.com/elkarte/Elkarte/releases/tag/v1 ) and tried to download the 1.0.5 update patch. But it gives 404 error. What to do ?
The link wrapped and broke ... Just go to https://github.com/elkarte/Elkarte/releases/tag/v1.0.5 and get the patch file ( like the first post in this thread indicates ) upload that to your forum and install. There is also a full install available at this link
Great release congrats team. :D
@Spuds ,
Successfully updated. Thanks
Congrats everyone, great work :D
Awesome!
Congrats :)
great release.
I am getting the following error when trying to update from 1.0.4 to 1.0.5.
Trying the second option, packages directory is writeable, sub folder temp does not exist?
Try creating the temp directory inside the packages directory and see if that fixes the issue. The system should do that automatically but perhaps there is a permissions issue. Once created try the package install again.
Installed the patch in two boards and both show 1.0.4 in their footer. :o
Oh, I checked the version number in SSI.php right at the top. It seems I have the same problem I had with SMF. >:( It seems the package manager couldn't change the files but says: "patch installed, all good!" :-X >:( :-X
Not unlikely, though it's always odd to think that you updated since 1.0.4 without problems and then the problem appear... :-\
Anyway I tracked that one a while ago, though not being sure the "fix" is right, I postponed it.
https://github.com/elkarte/Elkarte/issues/1463
I can provide full access if you want to examine this situation?
Honestly, I wouldn't know what to look for.
I think I know the problem (i.e. when files are not writable the package manager doesn't return an error and goes on without doing anything), but I'm pretty sure I wouldn't be able to find out why files switch from writable to non-writable... :-[