Simple Machines Community Forum

Dear Members,

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 (http://download.simplemachines.org/).

The quick summary of changes is as follows:

   
• Added PHP 7 support.
• Ported image proxy support from SMF 2.1.
• Also added HTTPS for avatars.
• Accept email addresses with long TLDs.
• See the changelog (http://download.simplemachines.org/index.php?thanks;filename=smf_2-0-14_changelog.txt) for more.

If you are running version 2.0.13, you can upgrade your forum to the latest version by using the package manager. As usual, you should see the upgrade notification in the admin panel notifications and in the package manager, which will allow you to download and install the patch seamlessly.  If you do not see the notification about the upgrade patch, please run the scheduled task "Fetch Simple Machines files" from the Scheduled Tasks page (Admin > Maintenance > Scheduled Tasks > Fetch Simple Machines Files (check the "Run Now" checkbox and click the "Run Now" button)).

The PHP version requirement for this patch is 5.4.0 or newer. Please ensure that your host is currently in compliance with this or ask them to upgrade your PHP version.

If you use older versions of SMF, you can upgrade directly to 2.0.14 from whichever version you are currently using by using the "full upgrade" archive from the downloads page. Be aware that using this upgrade method will require you to reinstall any customizations that you have added to your forum, so if you are running a version of the 2.0.x series, it is recommended that you apply the successive patches instead of using the full upgrade.

Please do not use this topic for support requests.
You will receive a much quicker and better response by posting in the 2.0.x Support Board (http://www.simplemachines.org/community/index.php?board=147.0).

If you are having problems downloading the patch from the admin panel, you can download the patch package from the upgrade patches page (http://custom.simplemachines.org/upgrades/) and install it via the package manager, as you would any other mod package.

Please refer to the Online Manual for more details about:

   
• Upgrading (http://wiki.simplemachines.org/smf/Upgrading)
• Patching (http://wiki.simplemachines.org/smf/Patching)

Thank you for using SMF!

Regards,
Simple Machines Forum Team

Thanks, PHP 7 support is great.

Congrats!

Congratulations! PHP 7 support, good job.

Good job team, thanks to everyone for their hard work :)

YES. GG fellas installing as soon as I can. Gonna test how proxies run. Cheers fellas!


Edit -- Just noticed when I used the Large Upgrade utility that the footer still displays "SMF ©2015, Simple Machines", just a heads up!

Excellent work!  Congrats!

I think the changelog may still need an update?

Is the patch supposed to be a zip file like all the previous patches. When I download the file it is .gz so am puzzled.

Quote from: shawnb61 on May 14, 2017, 05:31:53 PM
I think the changelog may still need an update?

Yup, they're working on that now! :)

Quote from: assemblytube on May 14, 2017, 05:33:13 PM
Is the patch supposed to be a zip file like all the previous patches. When I download the file it is .gz so am puzzled.

It's supposed to be a .tar.gz for this release. :)

Thanks for this release time to update my final servers to php 7!

Quote from: shawnb61 on May 14, 2017, 05:31:53 PM
I think the changelog may still need an update?

Fixed

I did see an update for custom themes using a login form is this required?

<input type="hidden" name="', $context['session_var'], '" value="', $context['session_id'], '" />


vbgamer45,

Yes.  This is an improved session check on the login form.  Custom themes that modify Login.template.php and the login on index.template.php will need to apply the patch.  If the code matches, the patch can apply the update to the custom theme.  Some custom themes won't match.

Ok good to know. A warning to some users might be needed. I noticed when I had one custom theme fail.

Congrats! 😁😁😁

Quote from: vbgamer45 on May 14, 2017, 06:34:41 PM
Ok good to know. A warning to some users might be needed. I noticed when I had one custom theme fail.

Same thing happened to me. I applied the patch after recording the failures that I needed to manually alter but the callouts weren't available.  Can't login to my forum now :)

Quote from: charlottezweb on May 14, 2017, 06:43:54 PM
Can't login to my forum now :)

Using the "login" function from the menu, or something else?
I applied it on a theme that was also giving the error, but looking in the files: didn't contain the feature at all.
So ignored the error, applied patch: and everything still works as intended. :)

Couldn't login to my forum from the particular theme's login on the site menu.  (Note: I'm using a custom social media login plugin so that's likely needing an update first).  I reverted my theme files in the meantime as well as /Sources to be able to get back in.  I think I'll just do a full/large upgrade tonight to 2.0.14 to do a little housekeeping until that theme and mod are updated to be compatible.

Good stuff team.  I appreciate the updates!

The plugin you have may need to be updated to do the session check properly.

The patch is very generous on the code it looks for.  Most themes should update if they have a global login form.  A few themes may have edited the code we are looking for.

Congrats everyone! ;)

Also template/mod site need 2.0.14 going to update a bunch of these with that update if they need it.

Good work!

If I want to use MySQLi, do I change the $db_type to just that in Settings.php?

Why you still not use utf-8 as default for mysql database type? SMF have support for 7.0 now, but does not work correctly with Cyrillic languages on PHP above 5.3.

....   I believe this has already been explained to you several times.

Quote from: Kindred on May 14, 2017, 08:57:04 PM
....   I believe this has already been explained to you several times.

SMF is only for English. I understood.

Quote from: digger on May 14, 2017, 09:02:38 PM
SMF is only for English. I understood.

Where do you get that?  When 2.0 was developed UTF-8 support wasn't as much of a need besides international forums and as well the added cost of storing the data was higher. Not to mention the CPU requirements for those days.  2.1 is defaulted to UTF-8 and only officially supports it.  For new 2.0 installs it's a simple checkbox.

Quote from: digger on May 14, 2017, 09:02:38 PM

Quote from: Kindred on May 14, 2017, 08:57:04 PM
....   I believe this has already been explained to you several times.

SMF is only for English. I understood.

No one has ever said that... it is as sleepy said... and as we have explained to you several times now...
so, for you to make that statement is disingenuous.

Anyone?

For support inquiries, as the op already states, please open a topic in the appropriate board.

Possible bug in proxy.php in the release https://www.simplemachines.org/community/index.php?topic=553863.0

Thanks, the devs will have a look at that! Despite very extensive testing both here on our own site and on other sites, it may be that a bug still managed to slip through the cracks for this new feature.

Very beautiful! Nice work. Thank you for this.

Great work SMF Staff and vbgamer45! (on the proxy issue)!

Everything is working!!

Error 500 does not arise after upgrade?

Quote from: gorbi on May 15, 2017, 03:25:47 AM
Error 500 does not arise after upgrade?

Please open a topic in the support boards with as much detail as possible, including what you were trying to do when you got error 500 and maybe we can tell you if it fixes it.

Thanks for all the work!!!

Gran trabajo!!! Gracias!!

Thanks team! Good release :)

A big thank you to all involved in making/testing this patch.

What a wonderful news!

Quote from: CoreISP on May 14, 2017, 05:24:20 PM
Good job team, thanks to everyone for their hard work :)

Agreed, thanks and well done to all. :)

Quote from: Pause on May 15, 2017, 06:14:48 AM

Quote from: CoreISP on May 14, 2017, 05:24:20 PM
Good job team, thanks to everyone for their hard work :)

Agreed, thanks and well done to all. :)

Agreed. :P gz team.

Great! updating right now

Thanks for the upgrade, and thanks to all the team members for all the hard work and long hours they put in here, I appreciated the group..

Ron..

Thanks for the hard work. Great!

Installed without a hitch.
Many thanks!

Thanks guys, installed without any issues.

Great work, my sites are now fully https without mixed content.

Just one question, are the language packs going to be updated?
I just downloaded the last language for my forum (spanish_es-utf8) and although they have the $txt entries, they are still in english.

They are not much of a deal for me, but for some site owners (a couple that I help in) might be useful have it right.

Quote from: Gluz on May 15, 2017, 01:51:58 PM
Great work, my sites are now fully https without mixed content.

Just one question, are the language packs going to be updated?
I just downloaded the last language for my forum (spanish_es-utf8) and although they have the $txt entries, they are still in english.

They are not much of a deal for me, but for some site owners (a couple that I help in) might be useful have it right.

Language packages are updated once the translations are done, so you'll probably need to wait until someone translate them. I'll see if I can do it during this week.

Hi team... very very thanks for this wonder news.... tomorrow i will do that upgrade :) Thanks again and keep this fantastic project alive and on top as until now!

Regards

There's a bug in the package, the last edit to Login.template.php adds another submit field to the maintenance login form:

<span class="lowerframe"><span></span></span>
<input type="hidden" name="', $context['session_var'], '" value="', $context['session_id'], '" /><p class="centertext"><input type="submit" value="', $txt['login'], '" class="button_submit" /><input type="hidden" name="hash_passwrd" value="" />
</div>
</form>';

Both the opening paragraph and the submit button shouldn't be there.

Quote from: Nibogo on May 15, 2017, 06:41:26 PM
There's a bug in the package, the last edit to Login.template.php adds another submit field to the maintenance login form:

Code Select Expand

<span class="lowerframe"><span></span></span>
<input type="hidden" name="', $context['session_var'], '" value="', $context['session_id'], '" /><p class="centertext"><input type="submit" value="', $txt['login'], '" class="button_submit" /><input type="hidden" name="hash_passwrd" value="" />
</div>
</form>';

Both the opening paragraph and the submit button shouldn't be there.

Think that was mentioned here, https://www.simplemachines.org/community/index.php?topic=553881.0

The long awaited patch!
Awesome!

Looks like I know what to do in the weekend :).

Fantastic guys, thank you so much for all your great work!! Tested first, no problems installing. Then installed it at my production site with no problems at all. Well done!!!

Not sure what happened. I installed the patch and now the forum displays a blank (white) page.
Unfortunate. Maybe someone has had the same problem. Any info would be appreciated.

Quote from: pgauthier on May 16, 2017, 08:46:39 PM
Not sure what happened. I installed the patch and now the forum displays a blank (white) page.
Unfortunate. Maybe someone has had the same problem. Any info would be appreciated.

Please have a look in the support for 2.0 board. If no similar threads, open one.
But this topic is not for support. ;)

Thanks!

Excellent work, everybody! :D

QuoteAdded PHP 7 support.

Great news !!!
Many thanks !!!

Thank's for the Update. It's working like a charme.

I saw in the language files smf_2-0-14_german that the file index.german.php is still with version 2.0.12 and shown inside administration as red version.
Only cosmetics, so i changed it to 2.0.14 and now everything is showing normal :-)

Is the release expected to be 2.0.15?

any future patch will have a bump in version number, so the next patch would be 2.0.15.

Quote from: Illori on May 18, 2017, 05:02:38 AM
any future patch will have a bump in version number, so the next patch would be 2.0.15.

will wait

Quote from: Illori on May 18, 2017, 05:02:38 AM
any future patch will have a bump in version number, so the next patch would be 2.0.15.

Also do not forget about this error: https://www.simplemachines.org/community/index.php?topic=553283.0

So there's that, the SSI_login bug... the warning in the installer, status.php needing updated...

And sendtopic.php bug, maintenance mode double login button

we have a list in the team boards of these issues and more we are working on getting fixed.

Is there possibilty to proxy every image?

For example forum avatars at simple portal home page aren't proxied. When you use <img src> to put image on forum board isn't proxied too. Any fix for that?

Quote from: matedgo
Is there possibilty to proxy every image?

For example forum avatars at simple portal home page aren't proxied. When you use <img src> to put image on forum board isn't proxied too. Any fix for that?

I'm fairly sure you aren't supposed to use this topic for support.

From the first post:

Quote from: Colin on May 14, 2017, 05:16:14 PMPlease do not use this topic for support requests.
You will receive a much quicker and better response by posting in the 2.0.x Support Board (http://www.simplemachines.org/community/index.php?board=147.0) ...

Update went clean, had to update a few areas of our website.

What MySQL function did SMF go in favor of, and why do some SQL functions still exist in like Subs-db-sql? For example, a lot of @mysql_error to silence the call, however when removing the @.. we see no errors in our logs making us believe these aren't even used any more just there?

(Asking about function as one of our mods use mysql_ we moved to mysqli_ but for consistency, would like to follow what SMF is doing.

you would be best to open a topic in the coding board to discuss this. it may take a bit to answer it and this topic IMO is really not the place for this discussion.

Quote from: matedgo on May 18, 2017, 02:30:50 PM
Is there possibilty to proxy every image?

For example forum avatars at simple portal home page aren't proxied. When you use <img src> to put image on forum board isn't proxied too. Any fix for that?

Can someone split this into a support thing?

Yes, it is very possible. You will, however, need to do some programming yourself if it isn't included within the mod by default.

As he has been asked to start a new topic, it is better to stick with that decision at this juncture.

After upgrade (from 2.0.13 to 2.0.14 using patch from builtin smf package manager),
users cannot login anymore,  only users that did not exited forum can use it.
When anybody try to login, after entering login and pass and pressing enter,
SMF gives warning — session timeout ($txt['session_timeout']), and it is imposible to login.
Downgrading to 2.0.13...

please dont use this topic for support. please open a topic in the proper support board so that we can assist you further.

I don't need any support,
I am experienced user, but I don't have time to debug this problem now (I already downgraded to 2.0.13),
when I'll have it (time), I'll try to install this patch manually, from vim in console  :'(, I'll write changes to every single line,
and then test login after each editing, when I'll find what is a problem, I'll try to do not forget to create a thread with a solution,
somewhere here on simplemachines.org...

The issue you are facing is already answered in several topics, just search.

I will be very grateful, if you send me a private message with a link on topic with a solution (or, if it is possible, please post it here),
I am not a native english speaker, so it is hard for me to clearly describe this problem in few words for a search query,
I already tried to "google it", but found nothing.

And this is what we mean, this topic is not for support period support is done in the support boards and many people have already solved the issue with the posts in the support board

I understood, but IMO few offtop messages can be easelly removed by moderators (or by message authors) at any time ::) ;)

Anyway, thanks to all for developing SMF! It is a great forum engine!

Thank you for all the work done, I upgraded

This proxy is a mistake, a huge mistake! ::)
Don't use it!


Thanks for PHP7 support! :)

Quote from: alexetgus on May 21, 2017, 01:20:05 AM
This proxy is a mistake, a huge mistake! ::)
Don't use it!


Thanks for PHP7 support! :)

Hmm, why is it a mistake?

Quote from: alexetgus on May 21, 2017, 01:20:05 AM
This proxy is a mistake, a huge mistake! ::)
Don't use it!

I happen to think the Proxy is one of the best SMF features right now... Especially considering how easy it is to implement in your scripts within and externally from SMF.

Not sure if you're trying to be funny or something. lol

Had a small issue with the update... new users couldn't register anymore, the forum logged the error message

Database Error: Field 'timezone' doesn't have a default value
File: /home/forum/smf/Sources/Subs-Members.php
Line: 771

Field 'timezone' from smf_members had a NULL default, setting default to 'Europe/Berlin' fixed this. After that, I had to set defaults for timezone_offset and timezone_update too (I used 0).

All seems to be fine now. - Am I the only one who was bitten by this, or did I do something wrong...?

Quote from: Steve on May 18, 2017, 03:43:45 PM
From the first post:

Quote from: Colin on May 14, 2017, 05:16:14 PMPlease do not use this topic for support requests.
You will receive a much quicker and better response by posting in the 2.0.x Support Board (http://www.simplemachines.org/community/index.php?board=147.0) ...

Read more closely. Since all is fine (for me) now, that was somewhat obviously not a support request. It's more like a heads-up that there might be circumstances under which the 2.0.14 update has issues. Do with it whatever you want.

Quote from: Hurga... that was somewhat obviously not a support request ...

You asked for confirmation that what you did was correct. That's a support request :)

Quote from: Hurga...Am I the only one who was bitten by this, or did I do something wrong...?

yes
thank you
Nice work

Thanks for the update. Unfortunately, it stopped my forum working. After upgrading from 2.0.13, every request failed with a "Function name must be a string..." error message on this line in the reloadSettings function in Load.php:


$request = $smcFunc['db_query']('', '
SELECT variable, value
FROM {db_prefix}settings',
array(
)
);


The problem seems to be caused by the new SMF_DB_MySQLi class, which is setting db_query to an array instead of a string. I have disabled that class in smf_db_initiate for now, and the forum is working again.

I'm running Centos 6 with its default PHP 5.3.3. Perhaps the new SMF_DB_MySQLi class's smcFunc settings require a higher PHP version?

Yes, it requires PHP 5.4.

If you need more help feel free to create a topic. Simply ask your host to upgrade to PHP 5.4 or higher.

Why upgrade script says that release requires at least PHP 5.3 if it really need PHP 5.4 to work? Everyone who updated forum with php 5.3 get it broken after.

a mistake was made, we are aware of it.

Disabling the SMF_DB_MySQLi class seems to be working fine. Am I missing anything important by not having PHP 5.4? If not, I hope the next SMF update will restore support for lower PHP versions by disabling the SMF_DB_MySQLi class itself if the version is lower than 5.4.


// Checck for MySQLi first...
if (function_exists('mysqli_connect') && @version_compare(PHP_VERSION, '5.4') >= 0)


yes security updates site speed are huge benifits for new php versions

Quote from: ian on May 24, 2017, 12:12:19 PM
Disabling the SMF_DB_MySQLi class seems to be working fine. Am I missing anything important by not having PHP 5.4? If not, I hope the next SMF update will restore support for lower PHP versions by disabling the SMF_DB_MySQLi class itself if the version is lower than 5.4.

Code Select Expand


// Checck for MySQLi first...
if (function_exists('mysqli_connect') && @version_compare(PHP_VERSION, '5.4') >= 0)


Don't plan on it. Please update your PHP.

QuoteAm I missing anything important by not having PHP 5.4?

Only that your server is fundamentally insecure as PHP themselves don't support PHP 5.4, or 5.5 for that matter.

RHEL/Centos 6 is still supported by Redhat, who backport security fixes to their packages*. RHEL/Centos 6 is still used by a lot of people, so I don't think it would be a good idea to drop support for PHP versions below 5.4 unless there is no way around it. In this case, there does seem to be a way around it (disable the SMF_DB_MySQLi class for lower PHP versions).

* https://access.redhat.com/security/updates/backporting

It's a tough call to make on one hand support old software that is years outdate. Or we can use newer PHP versions which has some better functions which can lead to better designed forum software long term.

If you're stuck on EL6 and can't update, I recommend using the IUS repositories (https://ius.io/). They are managed by a solid community and do not replace system packages, but conflict with them so you have to actively replace the old ones. Just install the repo and replace the php packages with the php56u, php70u, or php71u ones.

If you don't want to replace system packages, you could look at Software Collections (https://www.softwarecollections.org/), a project managed by RedHat to allow side-by-side installs of different software versions. It's a bit more complex, but could work very well if you can't replace system PHP packages.

wooohooo .... It crashed my forum.... happy with 2.0.13 ... and will be so for a while longer. :) ..  maybe 2.0.15 for me.

Thank you so very much for this update. You guys are the best of the best.
For all those who might want to know... Softaculous did not automatically update.
System sent an email.
Had to do manually in the Softaculous backend.
*Remember to delete your update.php

 8)   many Thanks  for this udge upgrade  to give us the OK!  to move our server to PHP 7   :) 

Thank you very much guys for this new awesome update.

Quote from: Colin on May 14, 2017, 05:16:14 PM
Please do not use this topic for support requests.
You will receive a much quicker and better response by posting in the 2.0.x Support Board (http://www.simplemachines.org/community/index.php?board=147.0).

N.B. This was posted in response to a message asking for support which has since been removed.

Quote from: bobtorre on May 25, 2017, 09:18:08 AM
wooohooo .... It crashed my forum.... happy with 2.0.13 ... and will be so for a while longer. :) ..  maybe 2.0.15 for me.

Make a post a support post and we can take a look.

It'll be the lack of PHP 5.4... again.

Looks like the

Quote! Fix search highlighting to not mangle/expose some HTML

is not fully resolved. See https://www.simplemachines.org/community/index.php?topic=554286.0

Quote from: spiros on May 31, 2017, 10:26:25 AM
Looks like the

Quote! Fix search highlighting to not mangle/expose some HTML

is not fully resolved. See https://www.simplemachines.org/community/index.php?topic=554286.0

it was causing more issues as i said in your other topic. we had to fix the search to restore it to work.

I'm not sure if it's related to this or not, but as soon as I updated to 2.0.14 I started getting a bunch of spam bots on my forum. I had only installed a theme recently but it's been removed anyways.

No that's not related :)

Quote from: Colin on May 14, 2017, 05:16:14 PMThe PHP version requirement for this patch is 5.4.0 or newer. Please ensure that your host is currently in compliance with this or ask them to upgrade your PHP version.

Not happy with this!

Why this choice has been made on a small update and not only on a branch update??

For some sites i must stay to smf 2.0.13 for now so. Great news thanks.

It's hardly a small update and it's the decision the team made. Sorry it's causing you grief.

It should have been a branch choice (upgrade) and not in a patch update or anything else. An add is surely good (php 7), but a remove is never a small choice....for smf users too!

Really sad and angry on this choice of update.

You should upgrade PHP or ask your host to. PHP 5.3 is really old (EOL'ed quite a while ago), insecure and should generally not be used in production anymore.

And it could not always be updated. It should have been removed on a branch choice.  I will remove smf from certains sites on certains hosters cause your update on the branch 2.0. It should have been for the 2.1 branch this remove. Remove done now.

A host that has PHP 5.3 still and don't offer the possibility to change to 5.4, 5.5 or 5.6 is a bad host IMHO, most of the ones I saw helping others have at least the possibility to change, and most of them get 5.4, 5.5 and 5.6

As you can see, a branch choice was not the way to go. If we can't change your opinion, so be it but the situations presented are quite clear. Besides, out of thousands (millions?) of users, you are the only one insisting on this. That alone should tell you something. ;)

Of course i'll be alone. ;) and the problem will be my opinion.... ;)

I have facts, i have to manage with my facts, so i'll do what i have to do. No problem. all is quite clear. ;)

Quote from: Steve on June 03, 2017, 07:57:09 PM
As you can see, a branch choice was not the way to go. If we can't change your opinion, so be it but the situations presented are quite clear. Besides, out of thousands (millions?) of users, you are the only one insisting on this. That alone should tell you something. ;)

Other than the small fact that it was totally possible to do this without breaking 5.3 compatibility. it was just perceived to be easier to grab 2.1's code and jam it in rather than taking the hour or so to change how Db-Subs-mysql.php worked.

I'm confused ... PHP 5.3 "end of life" was almost 3 years ago - why would any webhost still be offering it as an option?

Precisely because people have software that won't necessarily work on newer versions.

Quote from: Arantor on June 04, 2017, 12:03:16 PM
Precisely because people have software that won't necessarily work on newer versions.

;)

Quote from: MobileCS on June 04, 2017, 12:01:28 PM
I'm confused ... PHP 5.3 "end of life" was almost 3 years ago - why would any webhost still be offering it as an option?

Older servers still host things. Some distributions offer long term support and still provide backported security fixes for PHP 5.3 (such as RHEL or CentOS 6, until 2020). Ideally, people should be on newer PHP and other software versions, but that isn't always an option. Any hosting company offering new systems that only support up to PHP 5.3 as a default is negligent.

Speaking personally, I'm very against pushing new minimum requirements on a bugfix. This shouldn't have been done unless it was the only way to provide a fix, which it wasn't in this case. Hopefully the forum development team will properly move compatibility back in the next hotfix to avoid stranding users. That, or drop support for the 2.0 series and state that they can't properly maintain it.

I hope and if it's the case, it must be patchable from 2.0.13 version...

I really hope php 5.3 will be still supported on the 2.0 branch. It could be upped for the 2.1 branch, but not sure it's an interesting option too. (but if it will be the case i can understand)

Quote from: Colin on May 14, 2017, 05:16:14 PM
Please do not use this topic for support requests.
You will receive a much quicker and better response by posting in the 2.0.x Support Board (http://www.simplemachines.org/community/index.php?board=147.0).

Quote from: Illori on June 05, 2017, 09:10:50 AM

Quote from: Colin on May 14, 2017, 05:16:14 PM
Please do not use this topic for support requests.
You will receive a much quicker and better response by posting in the 2.0.x Support Board (http://www.simplemachines.org/community/index.php?board=147.0).

Sorry.  Removed my post and moved it over to the above.

Quote from: CoreISP on June 03, 2017, 07:11:00 PM
You should upgrade PHP or ask your host to. PHP 5.3 is really old (EOL'ed quite a while ago), insecure and should generally not be used in production anymore.

Well, PHP himself may have EOL'd the 5.3, but some distros still do maintenance updates to PHP 5.3 (basically meaning, they patch the PHP 5.3 themselves for found security issues). Perhaps most noteworthy distro to do so is RHEL/CentOS 6.0 (maintenance EOL november 2020). RHEL/CentOS 7.0 has 5.4, so that should still run SMF (but how long, if support for older PHP's is not a consideration?). I'm sure there are other distros and operating systems that have PHP < 5.4 supported and maintenanced, but frankly I'm mostly familiar with CentOS.

And CentOS is really popular as it is free, really stable, and has a very long support. One of the reasons that it is stable, is that they provide support for their packages, and thus does not force to upgrade major PHP versions for example. This is a huge deal to admins who has to keep these servers running. For example every PHP version upgrade is a pain, since you need to ensure that every software running in these servers is compatible with a new major PHP version. And many times they aren't, and then you have to patch that software by hand if possible and maintain that patching it in the future.

So yes, as a sysadmin it is a sad day to see SMF pumping up the requirements, hope it is for a good cause. Basically this means that SMF will not be hosted on these servers that use distro that has PHP 5.3 or older, or sysadmin has to start compiling and patching the PHP himself (sure there are 3rd party repos with newer PHP versions, but their maintenance is often shaky, and how much do you want to trust 3rd party repos?).

So as a sysadmin you want to keep things flowing from the distro's own reporitories, as it is the easiest and most safe way to keep your server secure and in working condition. And often this means that you may not have the most fresh versions, but as I explained, it makes sense and there is nothing wrong to it.

Often times I've found that easiest solution for me is to patch the software that requires a new major version of PHP for example to still support the older version. Couple of time I've found myself very baffled that why developers have sacrified the PHP 5.3 support for usage of array shorthand syntax in couple of lines of code  :o

I hope SMF will reconsider it's pumped up requirements for the project.

It wasn't even shorthand syntax as such, it's actually the result of array dereferencing support for variable function calls being introduced and literally no one testing it on 5.3.

That said, just because CentOS supports old versions doesn't negate hosts being able to offer newer versions as well, such as being able to offer 7 support which will mean you can give users a performance improvement that is really worth having.

Also, WordPress is looking st raising their minimum requirements, and they're already talking about promoting 7 as recommended rather than their current recommendation of 5.6.

Quote from: Arantor on June 06, 2017, 11:01:06 AM
Also, WordPress is looking st raising their minimum requirements, and they're already talking about promoting 7 as recommended rather than their current recommendation of 5.6.

I'm not surprised, the performance increase PHP 7 offers over 5.6 is night and day. All my forum pages load instantly now.

I'll never get tired of seeing this at bottom : Page created in 0.008 seconds with 16 queries.

Quote from: Arantor on June 06, 2017, 11:01:06 AM
It wasn't even shorthand syntax as such, it's actually the result of array dereferencing support for variable function calls being introduced and literally no one testing it on 5.3.

....

Yes, not saying it was in this case, was talking about different software.

However, I'm now moving SMF to different server, and there with 2.1.4 update notes using updater in admin panel states following about the patch:

Quote
This release requires at least PHP 5.3 to function. Most hosts should have it or something newer. You can check which version of PHP that you are running by visiting the "Support and Credits" section of the Administration Center.

Is this incorrect information, or was testing/modifying done to support 5.3? In original post it says 5.4 is required.

2.0.14 requires 5.4 at this time.

the patch has not been updated to change the version stated.

Sounds Good!! Congrats and all the best!

Logged in to report that 2.0.14 crashes on PHP 5.3, but after reading last pages... well...
You guys are awesome... best of awesome... awesomest of the best... :-P
I would at least put a big hairy warning in the upgrade notice.

For those who're looking for a quick fix: http://cs.ozerki.net/zap/Subs-Db-mysql.diff
So far this worked for me.

Wouldn't a better warning about PHP 5.3 be reasonable for a change in the current 2.0.14 patch, till 2.0.15 comes? Just put a warning in big red letters so it's harder to miss. That wouldn't affect the code, only the readme. Could save a few people the trouble.

At this point I'd suggest 1) fixing the big upgrade package so it says minimum 5.4 instead of 5.3 (may have been done but some recent topics suggest not) and 2) including an actual file which runs first in the installer in a <code> entry and checks, and fails to install if insufficient version found.

As long as no other changes or fixes were introduced, i.e. this is otherwise identical to install, I see no harm in changing the package this way.

Hello! Has purchased the kit, showing the version is not compatible! Is there a technical support or a paid installation? （SMF1.0.14）

Quote from: vbgamer45 on May 14, 2017, 06:17:38 PM
Thanks for this release time to update my final servers to php 7!

Quote from: vbgamer45 on May 14, 2017, 06:17:38 PM
Thanks for this release time to update my final servers to php 7!

Hello! You have already purchased the SMFHacks suite, the display version is not compatible! Is there a technical support or a paid installation? SMF1.0.14

Do you need help with upgrading SMF? What  SMF version are you on?

please do not use this topic for support. please open a topic in the support boards.

Quote from: chyg on June 14, 2017, 11:03:29 AM
Hello! Has purchased the kit, showing the version is not compatible! Is there a technical support or a paid installation? （SMF1.0.14）

Quote from: vbgamer45 on May 14, 2017, 06:17:38 PM
Thanks for this release time to update my final servers to php 7!

I am sorry, but that sentence did not make much sense. What did you purchase? And also this thread is not for support requests

The fact it requires a specific version is fine, and makes sense, and you can make it in big red letters for people to not miss and people will still miss it.

Something to consider next time: bumping the minor version would also have made sense here or, if possible (I don't know what new code has caused this requirement), have two seperate releases. One for the patch fixes, and then a minor version upgrade for the new PHP version (which is still old so you've got the ability to be backwards compatible to a degree).

Personally, I saw this as a patch upgrade and assumed it would be upgrade without fault. Every other SMF patch upgrade has, until this one.

No, bumping the minor version would not have made sense given that there is already a 2.1 with literal years of more development.

The new code that caused this requirement was code backported from 2.1 that fixes some issues with PHP 7, except no-one checked it required PHP 5.4 before releasing it (and it was too late to redo it in a more compatible way, though I gather SMF 2.0.15 will fix that)

I guess I'll keep asking this until someone answers. If I'm on 2.0.13 and PHP 5.3 with no way to go to 5.4, how do I get to 2.0.15 if .14 isn't going to work on my forum?

And yes Kindred, I know, I know, not for support. Sorry.

I guess you would install 2.0.15 instead of 2.0.14 if that is the goal?

 ;) glad it is still being actively updated

I make my update from 2.0.13 to 2.014 today.

Then i have problems with my database connection.

Solution:
The database must be also a higher version.
Server-Version: 5.5.47-0+deb7u1 - (Debian) ----- don't work

Now i have
5.7.12 - MySQL Community Server (GPL) ----work now


Perhaps you can write this to the requirement:
php must be higher 5.4
mysql must be higher than ???

mfg
andi nagl

I don't think it's entirely about the server version; there is no reason why 5.5 wouldn't work (I still have one deployment on MySQL 5.5 and it seems to work out OK), but I asked for more details in your support topic.

Nice Work Thank you

Works great, thanks for the update guys!!

So when are we getting the bugfix release?

Still some work left to do. Developers are busy this days.

Quote from: d3vcho(); on July 15, 2017, 01:25:13 PM
Still some work left to do. Developers are busy this days.

Not being funny, but it's been 2 months since this release went out with a number of bugs... any news?

No news so far, Arantor. We're still waiting for the developers. Hopefully, we'll get news soon.

Hi, have just installed the latest version and the installation went well. But when everything is clear to get up this environment. And with an IP-address 127.0.0.1

What do I do now?

See picture

http://imgur.com/V4AGg8A

you need to create a new topic as this is not for support

Thanks

Quote from: d3vcho(); on July 15, 2017, 02:40:06 PM
No news so far, Arantor. We're still waiting for the developers. Hopefully, we'll get news soon.

It's been 3 months now, any news on the patch?

No, sorry.

Hi, I just joined this forum since I have to manage a forum as Admin that uses SM: could u tell me how to download and install the    SMF 2.0.14 ?

I am on:

SMF 2.0.12   SMF 2.0.14
Sources   2.0.12   2.0.14
Default Templates   2.0   2.0.14
Language Files   2.0.12

Thanks.

Cedar
-edit- snip

Quote from: Illori on June 14, 2017, 11:21:11 AM
please do not use this topic for support. please open a topic in the support boards.

Dear Colin

Due to update SMF 2.0.14 automatically my SMF Forum is down due to not all the files have not been loaded and struck on 2.0.13 due to php files not up loaded right it shows the problem below:

My SMF is  ijlb.org forum  I no have access need help asp

I am admin for the site just took over a month ago


Kind
Regards

Colin H

removed username and password for security -d3vcho

Quote from: Illori on June 14, 2017, 11:21:11 AM
please do not use this topic for support. please open a topic in the support boards.

Please, use the right board to post your issue

which board please

https://www.simplemachines.org/community/index.php?board=147.0

Thanks for your new release, But How much time letter you release next release?

Thanks
Jhon

Release timeframes are never given out. It will be released when it's ready.

It's been over 4 months now. It is just me or is this an abnormally long time for a bug fix?

Is there something going on behind the scenes that perhaps the community should be aware of? This seems much more than a "developers are busy" issue.

I am glad they released 2.0.14 SMF updates... Seems normal to upgrade ASAP. :)

Quote from: MobileCS on September 15, 2017, 04:14:07 AM
It's been over 4 months now. It is just me or is this an abnormally long time for a bug fix?

Is there something going on behind the scenes that perhaps the community should be aware of? This seems much more than a "developers are busy" issue.

Well I guess that answers that question ...

There's no point on answering here each month to see if we "reveal" something new. Our position is going to be the same; We're still working on it.

I'll agree that things are being worked on. The plan is to get this patch right :)

Quote from: d3vcho(); on October 04, 2017, 04:11:43 PM
There's no point on answering here each month to see if we "reveal" something new. Our position is going to be the same; We're still working on it.

The thing is I never asked how long until it was ready - or if you guys were still working on it.

My question was :

Is there something going on behind the scenes that perhaps the community should be aware of? This seems much more than a "developers are busy" issue.

Quote from: MobileCS on October 08, 2017, 02:29:31 PM
My question was :

Is there something going on behind the scenes that perhaps the community should be aware of? This seems much more than a "developers are busy" issue.

Nothing that the community should be aware of.

QuoteIs there something going on behind the scenes that perhaps the community should be aware of?

The usual.

Quote from: Arantor on October 08, 2017, 03:06:50 PM

QuoteIs there something going on behind the scenes that perhaps the community should be aware of?

The usual.

Sad, but undoubtedly true. :(

I'm not sure what's sad about development and testing taking place as usual. :)
Even more extensive testing than before actually... Which makes it take longer but will contribute to an even better release.

But people who expect something negative, will always assume it actually is something negative. :( Its not.

This topic is about SMF 2.0.14's release. It seems to have run its course by the looks of it as it's going offtopic, and 2.0.15 appears to be close to release. As such I will lock this topic now. For support questions, please visit the appropriate support board.

Thank you to everyone for your feedback and all the kind words! :)