Today, we are pleased to release ElkArte 1.1.3. This release addresses two critical security issues and few bugs identified after the release of ElkArte 1.1.2. As this is a maintenance release, the majority of the updates are focused on bug fixes and increased stability.
This is a critical security update and we strongly encourage anyone running any previous version.
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 (https://www.elkarte.net/community/index.php?topic=0.0) on the forum for a complete list of updates. (Release notes are not yet ready.)
I have to apologize to
@pi.tech for not mentioning his contribution in reporting the security issue!
Sorry, I was tired and just did a copy and paste of the previous release... where I didn't thank him for his reporting of the other security issue...
Next time I'll try to remember.
Patching procedure:
- go to the page https://github.com/ElkArte/ElkArte/releases/tag/v1.1.3 (https://github.com/ElkArte/ElkArte/releases/tag/v1.1.3)
- download the file ElkArte_v1-1-3_patch.zip to your computer
- go to your forum: Admin > Main > Package Manager > Upload Package
- click the button to upload the package
- locate and select the file you downloaded at point 2
- click the "upload" button
- follow the instructions on the screen.
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!
Nice :)
And to double note .... This is a critical security update so don't pass this one up !
So far so good. Good jobs
@emanuele,
@Spuds, and all other developers...
You might want to update this site to 1.1.3 too.
Done, done, and done. Thanks guys! 8)
/me any time release an update is always scared something it broken... O:-)
Don’t you mean New Features are in first or second point version if you’re following Semantic Versioning, using the word Major is confusing. As it’s Major.Minor.Patch
Installed with no issues mind.
I think I have not read it in a while. xD
Good point, will try to keep in mind for the next release to reword a bit the sentence, thanks!
Asking to be sure...
Doesn't update the versioning correctly?
index says 1.1.1
Detailed version check says 1.1.2 (cept lang files)
Doesn't show 1.1.3 patch in Installed packages
Can one go straight from Version 1.1.1 to 1.1.3 ?
or do I need first to install the 1.1.2 Version ?
Many thanks.
Regards, Stefan.
From the patches you have to install them all, and I'd suggest to follow that path. :)
Has anyone gotten a fresh install of 1.1.3 to work?
For me it's completely unusable because of a white screen error. (group_list does not exist in the database or something...)
Will it only work if I install 1.1.2 and upgrade?
Which version of mysql do you have on your host?
Try disabling the strict mode into mysql
It's mysql 5. I don't think I have the option to disable strict mode (if it's even on), but I'll check. My server host is AwardSpace if that helps.
Okay, so I just checked and strict mode isn't on. This is the full error:
It's also listed here (https://github.com/elkarte/Elkarte/issues/3182) on the github. It seems like a fix hasn't been discovered yet.
Is the 1.1.4 version with bugfixes and GDPR support coming soon ?
In about how many days ?
I really need to convert now my sites to Elkarte, but wanted to wait, until the GDPR support is out.
Many thanks.
Regards, Stefan.
I think it should be out in a day or two as mentioned by
@emanuele and
@Spuds last time. Just a guess as I also don't know for sure.
Now we have the 5th June and still no new version with GDPR support ?
Who is helping to finish the new version ?
How many active developpers does Elkarte have in this moment ?
Many thanks for your hard work.
Regards, Stefan.
Do you have a privacy policy conform to the EU-DSGVO? If so, you can re-open your forum no matter what ElkArte version you are using - in my opinion.
Are you sure, I thought one must have a cookie management, so that you must be able to enable ro disable all
cookies coming from external sites... ?? Hmmm...
BTW, who are the real developpers here, that decide, when a new version is released ?
Is that Emmanuel and Spruds ? or still a few others ?
A cookie is not a privacy policy.
depending on which cookies You are setting You might need one ore You might not need one. The session cookies from a vanilla Elkarte installation do - afaik - not even need to be mentioned in the privacy policy. Things might be different regarding third party cookies - but in that respect most commercial and apparently conforming websites are surprisingly lax in this respect.
I recently switched from a SMF site which had been set up intentionally (not by me, beware!) to send a lot of stuff to google in order to achieve a good page ranking to a straight 1.1.3 installation with additional privacy policy and a few features turned off (e.g. inline youtube...)
I know that's incomplete, and i'm of course also waiting for 1.1.4. But in my eyes it is better to wait a little bit longer for a release of good quality than to install a sack of bugs (Bananensoftware, die beim Kunden reift, brauch ich jetzt wirklich gar nicht. Ganz besonders, weil meine Zeit als IT-consultant vorbei ist)
Yep, mostly they both do the hard and dirty work here ;D but there are other people which are contributing to this project, you can have a look on GitHub, there is a link on the home page. You will also note that it's an active project if compared to other free forum software.
We know that an update should be released on 1 June, but in the meantime other bugs were found and I guess they choose to solve them with the next update. As you can see it's difficult to give a precise date, but personally I prefer this way, at least we get an indicative date, instead of the answer we used to see for years: "when is ready ". And the last "when is ready" is from 2011-2012 and it's still not ready :P