SMF 2.0.14 Released with PHP7 and SSL support

[vbgamer45]

Simple Machines Forum has released a new patch to the 2.0.x line, bringing our latest release version to 2.0.14.

This patch adds both security and general maintenance fixes to your forum, so it is imperative that you install this patch quickly. You can view the changelog for this release, per usual, on the downloads page.

The quick summary of changes is as follows:
Added PHP 7 support.
! Updating session handlers
! Adding HTTPS
! fetch_web_data now uses cURL, falling back to sockets
! Ported image proxy support from SMF 2.1
! Also added HTTPS for avatars
! Added a simple exception handler
! Check session while logging in
! Sanitize some fields to help guard against XSS
! Validate email addresses with PHP’s filter method
! Fix search highlighting to not mangle/expose some HTML
! Fix password acceptance when special characters were used in UTF-8;
! Correct some random logic errors in the profile area
! Use ampersands instead of semi-colons for PayPal’s return link
! Fix sending multiple MIME-Version headers in notification mail
! Fix sending multiple Content-Type headers in all requests

Details: https://www.simplemachines.org/community/index.php?topic=553855.0

 

[lordi]

just update , thanx

 

[H-DB]

Just updated and I am working good!!

 

[zappaDPJ]

Has anyone had problems patching their custom themes?

 

[H-DB]

I had a pre-load test issue on my custom theme but they quickly told me it was not a problem as the code it was looking for to modify in my themes template was not even incorporated.

Here is that discussion...

https://www.simplemachines.org/community/index.php?topic=553860.0

 

[zappaDPJ]

I had a pre-load test issue on my custom theme but they quickly told me it was not a problem as the code it was looking for to modify in my themes template was not even incorporated.

Here is that discussion...

https://www.simplemachines.org/community/index.php?topic=553860.0

Thanks, that's very helpful

 

[GTB]

Nice changes but SMF 2.0 still does not use a responsive theme out the box. You'd think they would have focused on making the theme responsive in future releases like this because it's currently the 'stable version' for using and a big let down really for anyone who might be thinking of using it.
And have noticed some forks of this same SMF version, such as ElkArte. That has a responsive default theme.

 

[vbgamer45]

Yes that is planned for SMF 2.1. They did post an addon for the default theme that makes it more responsive.
ElkArte I like as well but too hard to get a bigger share of the marketplace.

 

[XinYenFon]

Nice changes but SMF 2.0 still does not use a responsive theme out the box. You'd think they would have focused on making the theme responsive in future releases like this because it's currently the 'stable version' for using and a big let down really for anyone who might be thinking of using it.
And have noticed some forks of this same SMF version, such as ElkArte. That has a responsive default theme.

Well Curve2 (SMF 2.1's default theme) is already responsive . Till that time you can use this.

 

[GTB]

Well Curve2 (SMF 2.1's default theme) is already responsive . Till that time you can use this.

Pretty obvious question then. Why not swap out the non responsive theme with SMF 2.0.14 for the responsive one?

Wouldn't it make sense to do that? I'm aware SMF 2.1 comes with a responsive theme, I've tested it installed 2 times at least. But SMF 2.1 is still Beta, it has been for years... still looks at least a year away from going gold (and that's being nice about it, been at Beta 2 for over 2 years now). SMF 2.0 is the stable version people should be using right now first, but that isn't responsive out the box when it should be.

Also, that theme says this: Compatible With: 2.0.9, 2.0.10, 2.0.11 (SMF 2.0.14 is out now) not listed as supported by it.

 

[XinYenFon]

Pretty obvious question then. Why not swap out the non responsive theme with SMF 2.0.14 for the responsive one?

Wouldn't it make sense to do that? I'm aware SMF 2.1 comes with a responsive theme, I've tested it installed 2 times at least. But SMF 2.1 is still Beta, it has been for years... still looks at least a year away from going gold (and that's being nice about it, been at Beta 2 for over 2 years now). SMF 2.0 is the stable version people should be using right now first, but that isn't responsive out the box when it should be.

Also, that theme says this: Compatible With: 2.0.9, 2.0.10, 2.0.11 (SMF 2.0.14 is out now) not listed as supported by it.

You mean, add the mod into a patch and serve Curve as "responsive" ? I hardly think they will do it. If you want an official answer to that ask at forums (SMorg). I'm no longer a teamie. If you are saying swap Curve with Curve2, that's another story to chase.

 

[GTB]

If you are saying swap Curve with Curve2, that's another story to chase

Yes, that is what I meant.

 

[emanuele]

And have noticed some forks of this same SMF version, such as ElkArte. That has a responsive default theme.

Actually ElkArte was forked from an "early" (actually old would be more accurate ) development version of 2.1 about...3 years ago? (Heck I forgot how much time passed since *that day* LOL) and not from 2.0.

Edit: no, it was 5 years ago!

 

[GTB]

Actually ElkArte was forked from an "early" (actually old would be more accurate ) development version of 2.1 about...3 years ago? (Heck I forgot how much time passed since *that day* LOL) and not from 2.0.

So ElkArte 1 (stable version) was a fork of an early SMF 2.1 version before they added in "front-end notifications" with it. Because both next development versions of SMF 2.1 and ElkArte uses front-end notifications that SMF 2.0 and ElkArte 1 doesn't have.

 

[XinYenFon]

Yes, that is what I meant.

Good luck with that. I hardly think anyone can do that in the team (time wise).

So ElkArte 1 (stable version) was a fork of an early SMF 2.1 version before they added in "front-end notifications" with it. Because both next development versions of SMF 2.1 and ElkArte uses front-end notifications that SMF 2.0 and ElkArte 1 doesn't have.

I'm not sure when Elkarte added responsiveness to their theme, I added it to SMF 2.1 3 years ago. By the time Elkarte created some of those features wasn't even on the table. I think its safe to say, SMF's development past 6-7 years (this is the time i think SMF 2.1 had since the very first code written for 2.1), it pretty much covered two release worth features/enhancement. That is why Elkarte 1.1 looking more like SMF 2.1 (Nightly).

 

[emanuele]

So ElkArte 1 (stable version) was a fork of an early SMF 2.1 version before they added in "front-end notifications" with it. Because both next development versions of SMF 2.1 and ElkArte uses front-end notifications that SMF 2.0 and ElkArte 1 doesn't have.

ElkArte started as fork of SMF 2.1 in late 2012, responsiveness was experimentally added in mid 2013.
"Desktop" notifications were first added to Elk in mid 2015 (and to be honest I should update them because still relying on an old implementation), not sure when were added to SMF.

Good luck with that. I hardly think anyone can do that in the team (time wise).
I think its safe to say, SMF's development past 6-7 years (this is the time i think SMF 2.1 had since the very first code written for 2.1), it pretty much covered two release worth features/enhancement. That is why Elkarte 1.1 looking more like SMF 2.1 (Nightly).

/me starts thinking at how many times he pushed to begin the release-freezing during 2012, and how many times he requested to have 2.1 live at sm.org and how his ideas were dropped the moment someone else re-joined the team (not you Antes, just to be clear) and argued release 2.1 as it was at the time was not up to the users' expectations and more features were required
And here we are.

 

[XinYenFon]

/me starts thinking at how many times he pushed to begin the release-freezing during 2012, and how many times he requested to have 2.1 live at sm.org and how his ideas were dropped the moment someone else re-joined the team (not you Antes, just to be clear) and argued release 2.1 as it was at the time was not up to the users' expectations and more features were required
And here we are.

been there done that. (btw I never re-joined the team ). I argued with the team related to going 2.2 actually... Turns out that's an insult to some people's ancestors. We can literally talk about SMF's management whole day/week the end point is I agree with you and current management not improving the software's popularity yet they refuse to accept it.

 

[emanuele]

OMG you agree with me? The world is going to end soon... darn I had a couple of things I wanted to do. xD

 

[lordi]

. Till that time you can use this.

thanx for this,