My host (and probably most hosts) preparing to ditch 7.1, am getting slightly nervous :O)
Will anything be done to stock SMF 2.0.15 to avoid it falling behind the times, an official upgrade to 7.2+ compatibility?
(mods would need individual attention, question related to SMF only)
Thanks
SMF 2.0.15 will never support php 7.2. we dont apply patches to already existing releases.
we are working on SMF 2.0.16 which will have basic support for php 7.2.
we dont have a release date yet for 2.0.16. it will be ready when it is ready.
So .16 will be the "patched" .15 :O) Good.
But note that the most it can possibly do is support the core of SMF - not any mods, especially not bbcode mods, all of which need a rewrite.
(Well, I say that. It's theoretically possible to write a package manager package that does it, but it would be a one way only patch, with no ability to revert if it goes wrong, and if it goes wrong it takes your entire forum down. And none of the mods would be able to uninstall after because the code that they added would be entirely removed. And if you upload a new batch of files, then add mods, the mods break again. Or if the mods use hooks, it's all redundant anyway because they still don't work properly on PHP 7.2 even if the rest of the core could be patched. So, yeah, net result is that only the core can be patched.)
My host changed php 7.2 already and there is no possibility to change to any earlier version php on cPanel.
Forum was running on 1.1.21 smf, so this means that my forum is not working at all and I cannot upgrade it.
Is only possibility to wait 2.0.16? Or any suggestions what I can try?
SMF 2.0.15 will function on php 7.2, it just will fill your error log with errors.
Thank you. Ok, good to know. I´ll try upgrade then.
Quote from: Jarppi on September 08, 2019, 04:03:27 PM
My host changed php 7.2 already and there is no possibility to change to any earlier version php on cPanel.
Forum was running on 1.1.21 smf, so this means that my forum is not working at all and I cannot upgrade it.
Is only possibility to wait 2.0.16? Or any suggestions what I can try?
Hi,
My host upgraded to PHP7.2 and it broke some bits on my SMF 2.0.15.
Firstly make a back up of the file I'm suggeting you change belowWhat you could try is if you have an .htaccess file change the code inside it to say
# Use PHP5.6 as default
AddHandler application/x-httpd-ea-php56 .phpYou could also try repalcing the text 'php56' to 'php71' if you wanted to use 7.1
If you don't have .htaccess try creating one, with the code I suggested, in Notepad++ and upload it to the public html folder on your
I'm not sure if your host would have completely got rid of 5.6 if they did then it probably wont work. If it's doesn't work then just delete the new file or revert back your old .htaccess file
For my site everything is OK again now.
Any host that does this to their customer is completely irresponsible. Likely they have little experience running a damn business
Quote from: Jarppi on September 08, 2019, 04:03:27 PM
My ho changed php 7.2 already and there is no possibility to change to any earlier version php on cPanel.
Forum was running on 1.1.21 smf, so this means that my forum is not working at all and I cannot upgrade it.
Is only possibility to wait 2.0.16? Or any suggestions what I can try?
-edit- No hosting advertisements allowed outside of the hosting boards.
Quote from: Jarppi on September 08, 2019, 04:03:27 PM
My host changed php 7.2 already and there is no possibility to change to any earlier version php on cPanel.
Forum was running on 1.1.21 smf, so this means that my forum is not working at all and I cannot upgrade it.
Is only possibility to wait 2.0.16? Or any suggestions what I can try?
What was the previous version of PHP on that server?
As an update,
Another site I'm admin on had the same problem with the host updating to PHP 7.3 and when I checked cPanel it's been changed to a new version which doesn't allow the changing of PHP versions to below 7.0.
So I did my suggestion for the .htaccess file in the post above and it did work, so for those who are having issues with PHP7+ they can probably revert to 5.6 if they need to go back.
Quote from: Biology Forums on September 11, 2019, 09:24:40 PM
Any host that does this to their customer is completely irresponsible. Likely they have little experience running a damn business
In just six weeks time, PHP 7.2 becomes the oldest supported version of PHP.
Running unsupported versions of software with a long history of security issues* on a shared server - what could POSSIBLY go wrong?
* https://www.cvedetails.com/vulnerability-list/vendor_id-74/product_id-128/PHP-PHP.html has some of PHP's.
Quote from: davejo on September 29, 2019, 02:53:16 AM
As an update,
Another site I'm admin on had the same problem with the host updating to PHP 7.3 and when I checked cPanel it's been changed to a new version which doesn't allow the changing of PHP versions to below 7.0.
So I did my suggestion for the .htaccess file in the post above and it did work, so for those who are having issues with PHP7+ they can probably revert to 5.6 if they need to go back.
There has got to be a point at which most hosts will remove all PHP versions older than 7.0 (which is already EOL). 7.2 will enter the "Security fixes only" stage by the end of the year
Given that hosts are still keeping 5.6 for the time being, I wouldn't immediately assume that it's quite that bad. I also know some distros (especially the likes of CentOS) backport security fixes from newer versions of PHP...
But there is a 2.0.16 being worked on where *some* of this is remedied. I wouldn't call it total compatibility, but it will be usable in most cases without masses of errors in the log.
You can move to a better host. My host supports php 5.3 - 7.3, currently running 7.2 native. I sometimes use early versions to salvage damaged 1.1 databases, so it's a necessity for me.
My site, notthenoobs.com, is built on 2.0.15 and I signed up with Gray Web hosting. This is on php 7.3. Is that likely to be a problem?
Quote from: nidec on October 17, 2019, 05:19:24 PM
My site, notthenoobs.com, is built on 2.0.15 and I signed up with Gray Web hosting. This is on php 7.3. Is that likely to be a problem?
7.1 is the highest version 2.0.15 supports. You should be able to select 7.1 in your cPanel.
Quote from: nidec on October 17, 2019, 05:19:24 PM
My site, notthenoobs.com, is built on 2.0.15 and I signed up with Gray Web hosting. This is on php 7.3. Is that likely to be a problem?
One of the sites I'm admin on have had an updated cPanel installed by the host and changing the PHP version is not allowed. If you have problems then try what I've suggested with the .htaccess file here https://www.simplemachines.org/community/index.php?topic=569552.msg4030781#msg4030781
I should add that although I have done this and it was successful the host keeps changing the PHP version back to 7.+. I have suggested to the owner of the site that he contacts the host to tell them that the SMF software does not work on anything above 7.1 as yet I don't think he's done that.
These are the options on my hosting (see attach.)
A very good host btw, and not running any unsupported, outdated, potentially unsecure?, php versions.
Quote from: lurkalot on October 17, 2019, 06:40:31 PM
Quote from: nidec on October 17, 2019, 05:19:24 PM
My site, notthenoobs.com, is built on 2.0.15 and I signed up with Gray Web hosting. This is on php 7.3. Is that likely to be a problem?
7.1 is the highest version 2.0.15 supports. You should be able to select 7.1 in your cPanel.
There is no option to change it. I went with Gray Webhost because they were recommended on here as being experts on SMF, so Im surprised thats not available
Weird, my GWH account lets me pick 5.6 and 7.0.
Where are you looking for the option?
Quote from: a10 on October 18, 2019, 05:24:04 AM
A very good host btw, and not running any unsupported, outdated, potentially unsecure?, php versions.
All php versions on my host (5.3-7.3) are supported with security updates.
Quote from: nidec on October 18, 2019, 10:54:34 AM
Quote from: lurkalot on October 17, 2019, 06:40:31 PM
Quote from: nidec on October 17, 2019, 05:19:24 PM
My site, notthenoobs.com, is built on 2.0.15 and I signed up with Gray Web hosting. This is on php 7.3. Is that likely to be a problem?
7.1 is the highest version 2.0.15 supports. You should be able to select 7.1 in your cPanel.
There is no option to change it. I went with Gray Webhost because they were recommended on here as being experts on SMF, so Im surprised thats not available
I'm on Gray Webhost too, and only just gone to 7.1 from 5.6 in the last week or two. ;)
Maybe its because mines a new site, but im on 7.3.6
Quote from: nidec on October 18, 2019, 10:54:34 AM
There is no option to change it. I went with Gray Webhost because they were recommended on here as being experts on SMF, so Im surprised thats not available
In the hosting cPanel, search at top for PHP. Then see if you have MultiPHP Manager You can change it there.
Or if you are still stuck then send them a Support ticket, I'm sure they will sort it for you.
It's also sometimes called easyApache.
Getting close now.
Quote...will soon be updated from version 7.1 to the latest stable version, which is currently version 7.3. The reason for the update is that PHP version 7.1 will reach end of life on December 1st, 2019. When a PHP version reaches end of life, all security support is stopped, making continued usage a potential security risk.
...during the first week of November. The differences between PHP 7.1 and 7.3 are minor, so you will most likely not notice any difference.
After the automatic update, you still have the option to manually downgrade PHP to version 7.1. This gives you a chance to fix any potential issues due to outdated code before December 1st 2019, when PHP 7.1 will be removed permanently.
I hope it will support 7.3 as well. Just got a notification that my host will update to 7.3 in the first week of November. So, I guess I will be updating to 7.3 on my Acceptance Test server as soon as possible and see what runs and what not....
I'm having this exact issue. In the beginning of November my hosting will be upgraded to PHP 7.3, though I can downgrade until the end of November. From then on it's only PHP 7.3.
This isn't a PHP or hosting issue, this is a SMF issue. SMF 2.1 is not ready yet, correct? What to do?
Quote from: TheEnemy42 on October 23, 2019, 11:07:49 AM
This isn't a PHP or hosting issue, this is a SMF issue.
To be fair, it's a little of both. PHP versions have usually not been abandoned this fast in the industry.
Looking back I can see some of the older versions have been supported for longer but it's still 3 years since 7.1 was released. 7.2 was released 2 years ago, the same time SMF 2.0.15 was released. That's still quite a long time without any support.
Note I'm not neglecting the effort needed to maintain SMF but looking at it from the perspective of a forum administrator I'm for the first time forced to consider the option to migrate to a different forum software due to lack of support - and that does make me sad.
PHP moving to an annual release cycle makes it hard for volunteer platforms to keep up, in practice.
Remember that there are like 4 people on the dev team doing it in the spare time they have... it's really not a lot and there are some other priorities that need to be taken care of too.
But 2.0.16 is coming. I've seen beta builds of it with 7.2 functionality in it.
^^^ But 2.0.16 is coming
Thanks for confirming :O)
Would really hate to be forced into leaving my 10 years+ of excellent hosting because of them doing a good job in running up-to-date software on their servers !
You could get working you just have to turn off some php error logging/to suppress some errors. minor edits. I have one my servers updated to php 7.3 with smf 2.0.x running.
When they moved to 7.1 I think I was still on 2.0.13 and everything just stopped working displaying my database password in plain text to everyone who went to the site. Wasn't too happy....
Quote from: vbgamer45 on October 23, 2019, 03:07:36 PM
You could get working you just have to turn off some php error logging/to suppress some errors. minor edits. I have one my servers updated to php 7.3 with smf 2.0.x running.
Thanks for info, an option to 2.0.16.
ftm made a complete copy of my live forum on another server, and will do some late night alchemist experiments with php 7.2\3\4 and see what blows up.
Quote from: Arantor on October 23, 2019, 11:37:41 AM
But 2.0.16 is coming. I've seen beta builds of it with 7.2 functionality in it.
I'm glad to hear. Do you know when it's expected to ship? Seeing as I have 1-2 weeks before my host upgrades I'd much prefer to upgrade SMF beforehand to avoid downtime.
Quote from: Arantor on October 23, 2019, 11:37:41 AM
PHP moving to an annual release cycle makes it hard for volunteer platforms to keep up, in practice.
Remember that there are like 4 people on the dev team doing it in the spare time they have... it's really not a lot and there are some other priorities that need to be taken care of too.
Yes, as mentioned I'm not neglecting the effort needed and I'm well aware that this is volunteer work and indeed it's much appreciated. I have no real knowledge of PHP development and can understand that the changes needed are quite extensive.
But realistically, seeing as this is possibly a breaking change in PHP it might spell the doom of the SMF project if not handled, even if I'd hate to see it. Most hosts prefer to follow the recommendations of the official PHP development team and I'm guessing most forum admins won't have the knowledge needed to hack their SMF installation to make it work or ignore all the errors as vbgamer45 mentioned. I'm a developer myself but have no clue as to where to start. A guide would be much appreciated if 2.0.16 is not finished in time.
Quote from: TheEnemy42 on October 24, 2019, 06:46:42 AM
Quote from: Arantor on October 23, 2019, 11:37:41 AM
But 2.0.16 is coming. I've seen beta builds of it with 7.2 functionality in it.
I'm glad to hear. Do you know when it's expected to ship? Seeing as I have 1-2 weeks before my host upgrades I'd much prefer to upgrade SMF beforehand to avoid downtime.
it will be ready when it is ready. we never provide dates.
I find it disturbing all these responses and nobody mentions the mod that fixes things up just fine and dandy.
https://www.smfhacks.com/index.php?topic=9707.0
Though it's sad most of what needs to be fixed is stuff we've been told since PHP 5.2 to stop doing... like using create_function instead of anonymous functions.
Except that 1) it's not an official patch, 2) it only fixes the core, it doesn't fix any other bbc mods or any other mods broken by PHP7+, and 3) the replacement for create_function didn't exist until PHP 5.3 anyway.
But there's still hosts out on version 5.3 and 5.4 which is why it was not fixer sooner in the 2.0 series. It has long since been fixed in 2.1 however.
Have people tried running 2.0.15 on PHP 7.3? What issues do you run into?
Same issues that 7.2 presents, any bbc mod spews into the logs, and some badly written code breaks (but it would also under 7.1 and 7.2)
Quote from: Arantor on October 26, 2019, 11:00:49 AM
the replacement for create_function didn't exist until PHP 5.3 anyway.
5.3 came out in
2009! That's plenty of time for a replacement for create_function to have been dealt with, even with all coders being volunteers. A quick search of 2.0.15 shows 196 occurrences, many of them are repeats/duplicates, when you take that into account, there's probably about 50 unique occurrences. create_function was depreciated in 5.2 which came out in
2006! Frankly there's no excuse for that not having been dealt with a fair way before 2.0.15, even when considering that SMF is coded by volunteers
Yes, yes, we know that. We also know that in 2009 when 2.0 RC2 first came out, a lot of hosts were still very firmly using 4.3. Even now, I know of production sites still running on 5.5 that for one reason or another cannot be upgraded, so it's really not that simple.
They're also not duplicates; every single bbc definition has its own create_function instance. Also, no, it wasn't deprecated in 5.2, because it couldn't have been deprecated until its replacement came out the following version. It has been deprecated in 7.2, which is only out in 2017.
Part of the problem is that people like you demonise the SMF team - if they spend time on 2.0, they get blasted for not finishing 2.1, and if they spend time on 2.1, they get blasted for not sorting this for 2.0.
It's that kind of attitude that has led a number of people not to contribute to development, and for those few brave souls that do, they have to do it in their evenings and weekends around their day job.
Quote from: Arantor on October 27, 2019, 08:39:20 AM
Yes, yes, we know that. We also know that in 2009 when 2.0 RC2 first came out, a lot of hosts were still very firmly using 4.3. Even now, I know of production sites still running on 5.5 that for one reason or another cannot be upgraded, so it's really not that simple.
They're also not duplicates; every single bbc definition has its own create_function instance. Also, no, it wasn't deprecated in 5.2, because it couldn't have been deprecated until its replacement came out the following version. It has been deprecated in 7.2, which is only out in 2017.
WRONG! https://www.php.net/manual/en/functions.anonymous.php They've been available since 5.3, it even says on the manual page for create_function that you should be using anonymous functions
Part of the problem is that people like you demonise the SMF team - if they spend time on 2.0, they get blasted for not finishing 2.1, and if they spend time on 2.1, they get blasted for not sorting this for 2.0.
It's that kind of attitude that has led a number of people not to contribute to development, and for those few brave souls that do, they have to do it in their evenings and weekends around their day job.
The PHP function phpversion (https://www.php.net/manual/en/function.phpversion.php) has been around since PHP4! It can be used to determine which version of PHP is in use, if it returns that the version is a new enough version with an if-else block either the newer or legacy code could be run.
That's
10 years that there's been to fix that, frankly that should have been dealt with years ago, before 2.1 was even started. Version 1.0 was active at the time. Only being able to do it during evenings and weekends is no excuse when the solution has been available for about 10 years
QuoteThe PHP function phpversion (https://www.php.net/manual/en/function.phpversion.php) has been around since PHP4! It can be used to determine which version of PHP is in use, if it returns that the version is a new enough version with an if-else block either the newer or legacy code could be run.
Short of having 2 different Subs.php files (since a 5.3+ file will fail to compile on 5.2 if it uses closures), no, you actually can't. It really doesn't work like that. You have to have made the decision before even loading Subs.php and thus two different versions of the file are required. Which means double the work for all the modders, which means less modding gets done. It's also how to make a system even more fragile.
Thank you for telling me how I should have done my job, really appreciate the feedback.
P.S. You have reaffirmed every decision about why I removed my mods, means I don't have to worry about maintaining them since they'll all be terrible and incompetent, good to know.
SpacePhoenix - You think you can do better?
SMF 2.0.x is BSD licensed. GO ahead and fork it and show us how much better you would make it.
Until then -- please either knock it off or go away.
I'm also speaking as someone that has led two of the forks that have attempted the most significant amounts of changes to SMF in the last 10 years, too. I get, better than possibly anyone, how much effort it *actually* is to effect change.
Sitting on the sideline moaning about it, that's easy... getting off of one's backside to do something about it, considerably harder.
Quote from: Kindred on October 27, 2019, 10:33:22 AM
SMF 2.0.x is BSD licensed. GO ahead and fork it and show us how much better you would make it.
Why would I fork a piece of software that is in real need of a complete re-write from the group up using at the very least OOP and ideally also MVC? ::)
So why are you still using SMF (assuming you're using it because you're complaining about it) when OMG it's so terrible?
I hope that you guys will make things ready, we regulars are little lacking of support since we need knowledge to fix things on our own, but for my time here I can say that you are doing great job and it would be disaster change like this to affect on entire project. I can understand hosts moving from php5 to php 7.1, but doing more than that should mean hosting have to fix problems caused to every individual customer who request or to return money since some damage is done with forced change.
Offtopic
In last 2 days I read some post related with new bug discovered and there was word about UTF-8 on 2.1, and on 2.0 is another standard for which some text/data is lost over time. Can't find that topic, but is it possible to make it for 2.0.16? I believe that thing happened on forums to me, where I was sure to have some text written but could not find it.
UTF-8 is just a different character set, should not in any way cause anything to be lost. I've been using UTF-8 with 2.0 for years....
Quote from: Aleksi "Lex" Kilpinen on October 28, 2019, 01:00:46 AM
UTF-8 is just a different character set, should not in any way cause anything to be lost. I've been using UTF-8 with 2.0 for years....
If only that were entirely true. MySQL's UTF-8 implementation is deliberately incomplete to the point where it has two and 2.0's implementation does some very tricky stuff to repack the extended range stuff into the otherwise incomplete version.
Quote from: Arantor on October 28, 2019, 03:39:44 AM
Quote from: Aleksi "Lex" Kilpinen on October 28, 2019, 01:00:46 AM
UTF-8 is just a different character set, should not in any way cause anything to be lost. I've been using UTF-8 with 2.0 for years....
If only that were entirely true. MySQL's UTF-8 implementation is deliberately incomplete to the point where it has two and 2.0's implementation does some very tricky stuff to repack the extended range stuff into the otherwise incomplete version.
That's what utf8mb4 is for: https://medium.com/@adamhooper/in-mysql-never-use-utf8-use-utf8mb4-11761243e434
Yes, yes, I know. But SMF still supports versions of MySQL that predate mb4 support. I'm the guy who made it work anyhow by doing some magic to convert 4 byte characters into entities to fit in the 3 byte space.
Will 2.0.16 affect themes? If so, how?
Quote from: Skhilled on October 28, 2019, 06:24:12 AM
Will 2.0.16 affect themes? If so, how?
I haven't looked in a while but the login thing should be fixed once and for all (with no theme changes needed) and maybe new footer links to accommodate the new GDPR features.
Great, thanks, again. :)
Quote from: lurkalot on October 18, 2019, 12:51:35 PM
Quote from: nidec on October 18, 2019, 10:54:34 AM
Quote from: lurkalot on October 17, 2019, 06:40:31 PM
Quote from: nidec on October 17, 2019, 05:19:24 PM
My site, notthenoobs.com, is built on 2.0.15 and I signed up with Gray Web hosting. This is on php 7.3. Is that likely to be a problem?
7.1 is the highest version 2.0.15 supports. You should be able to select 7.1 in your cPanel.
There is no option to change it. I went with Gray Webhost because they were recommended on here as being experts on SMF, so Im surprised thats not available
I'm on Gray Webhost too, and only just gone to 7.1 from 5.6 in the last week or two. ;)
Found it and changed it to 5.6
Had to search Multiphp in the seach box, but it came up and was an easy swop.
When the next version 2.0.16 comes out and I upgrade, wil I have to swop this back?
Quote from: SpacePhoenix on October 27, 2019, 06:29:02 PM
Quote from: Kindred on October 27, 2019, 10:33:22 AM
SMF 2.0.x is BSD licensed. GO ahead and fork it and show us how much better you would make it.
Why would I fork a piece of software that is in real need of a complete re-write from the group up using at the very least OOP and ideally also MVC? ::)
This is also the question I should have asked myself 2 years ago. I guess when I last started, I wanted to preserve the spirit of what brought me here. But it's time to move on in that respect.
Testing with 7.3.11, "most of everything" seems to work fine.
Only real problem I could see so far, mailqueue is hit by deprecation, no php email leaves the house.
i'm glad i run a dedicated server... and can hang on to 7.1 as long as i need to.. yes, i checked- the host 'warned against it' but said they wouldn't force me to upgrade anything i didn't want to... which allows me time to await the first official release of 2.1 (which i already have styled the way i want it).
at any rate, that isn't why i'm posting.
to shoot at the authors of SMF because of evolving foundation is about..... goofy. it was and is a great platform. that's all that really needs to be said about it. if anyone was paying for it maybe there would be an opportunity to complain- but it's not. and it's better on many levels than the 'better' ones that are (premium/paid for).
Quote from: drewactual on October 30, 2019, 10:26:12 PM
if anyone was paying for it
The Charter Members are paying, every year.
Sad there seems to be very few who find it worth some money supporting smf that way.
Yes but they're not paying the developers. That money goes to infrastructure/servers etc. - no one at SM is paid to do the software.
It has been debated but every time turned into a debate about why the developers were special and that every other team also deserved recompense, in the name of equality.
Quote from: drewactual on October 30, 2019, 10:26:12 PM
i'm glad i run a dedicated server... and can hang on to 7.1 as long as i need to.. yes, i checked- the host 'warned against it' but said they wouldn't force me to upgrade anything i didn't want to... which allows me time to await the first official release of 2.1 (which i already have styled the way i want it).
I'm not on a dedicated server and I can still choose any PHP version down to 5.4. Depends on who your host is, I guess. MultiPHP makes this even easier, you can choose PHP version per domain or per subdomain ;).
So the host updated all to 7.3 (good warning in advance, option to revert to 7.1 for some weeks extra, they got good routines).
" All errors (3706) " ...in 1 hour. Really looking forward to 2.0.16 :O)
On my production site, mail works fine on 7.3, so discarding my previous (test site) mail comment (forgot to reset the php mail settings there doh).
I hate to bump this but I'd really like some suggestion on how to handle the removal of PHP 7.1 in about two weeks time.
It seems I can continue using 7.2 but from what I can understand it'll still cause some issues or a flood of error messages in the logs. My host already automatically upgraded to 7.3 and before I noticed and manually downgraded to 7.1 again I had some 7 million errorlog entries in SMF :( On the positive side it doesn't seem like the users have complained about anything yet.
Hope that 2.0.16 comes along soon.
I really want to upgrade to SMF 2.1.
But when doing that I want to do a complete overhaul of my entire website. I think at that time it would be best to clean the whole website, install SMF 2.1 and then migrate the data back. Will be some work :)
that is why we have the upgrade script. you cant just migrate data into the upgraded database due to the changes. you need to follow our upgrade process to make sure it is successful.
Hmmm... I would very much like to go to a clean vanilla forum. In the years that the current one has been running a lot of mods have been added. Some of them still work, but cannot even be controlled anymore :)
The only thing I would need from the old environment is:
-User names
-Passwords (still encrypted)
-E-mail addresses of users
-Messages
-Personal messages
-Subscriptions (so, who has subscribed to what topic)
But hey... I am not looking to hijack this topic ;)
no. that is a really bad way to deal with things....
it's not a simple "copy tables a, b and c..." because there are other tables that are interrelated.... and asome mods may make changes to the columns within a needed table.
and it reallt, really won't work, because the password hash has changed -- so, without the upgrade script, it won't get converted
If there is no problem with the current forum, than don't worry about stuff left over in the database from older mods.
Ok, I understand... there is a lot more to it :)
And the forum is running, so that part is fine. But there are definitely quite a lot of errors logged, which I think are due to all sort of old mods. Perhaps I will be fine if I just install a vanilla version of the forum and then migrate using the script and only install those mods that I really need.
Quote from: Plantje on November 13, 2019, 10:45:36 AM
Perhaps I will be fine if I just install a vanilla version of the forum and then migrate using the script and only install those mods that I really need.
First, for every mod, check that it is actually compatible with 2.1rc2!
Noooo... I am waiting until the final version of 2.1 is out. Then I want to start with a clean version. And if a mod is not compatible with 2.1....so be it 😄
I will start on my test server anyway
i'm too setting up to swap to 2.1 after the final release.... but no vanilla...
2.1 responsive is much like the responsive i built with my flagship 2.0.x... it is better in some places, not so much in others- but... it's ready out of the gate. insofar as the alterations where presentation is concerned, i decided to use includes and no real heavy lifting with the default theme.
i will be porting over the data from the 2.0 forum and then duplicating it and moving it back.
it will be interesting to see how much php7.3 improves speed and weight of the page.
the 'new' site, 2.1 if anyone is interested still has a lot of WP functions embedded on it, but it will be removed before going live. it's @ https://www.cfb51-LINE.com/forum .... the 2.0.15 site is https://www.cfb51.com ... i show this to demonstrate it's not too hard to make them look similar...
I went with sprites on 2.0 instead of separate images for the various icons, and found that 2.1 already uses sprites which i will have to change- not a big deal.
the fact that 7.1 didn't last that long is quite disappointing considering the amount of time i've put into 2.0 over the past three or so years, but it is just the nature of things. it was great whilst it lasted!!! the future of both SMF and the interwebz including whats under the hood can't really do anything but get better, and that's because it's pretty good right now and we can always fall back if needed.... of course i say this tongue in cheek- for those that take me too serious..
Quotethe fact that 7.1 didn't last that long is quite disappointing
Like every release for the last few years, it gets 2 years of mainstream fixes and a year of security fixes. 7.1 has been out since December 2016, I wouldn't suggest it didn't 'last long'. 7.4 is around the corner, for example.
i was making a funny, or attempting to... i built with 7.0 in mind and put a lot of hours in it... i 'selfishly' don't want to see it go away as if it's 'doing it' to spite me. just a joke and i dont' really believe that. i'm anxious to swap over, and as soon as my season is over, and hoping it coincides with the release of 2.1, i'm all aboard the next iteration!
NOT being funny or cute: the learning curve for 2.1 is nothing like the curve for 1.1 or 2.0 was... it's pretty intuitive after being familiar with the prior versions.
for this i thank y'all.
Frome host:
QuoteWe urge you to fix any potential issues due to outdated code before December 1st, when PHP 7.1 will be removed permanently
Tests suggests forum will somehow continue working, but would be very, very nice to see the number "16" soon :O)
Agreed. But with 3 days left that would be somewhat careless not to act upon in other ways; though the trouble is that I don't know what can be done.
Does anyone know of anything that can be done to mitigate the issues and errors that comes with running with SMF 2.0.15 on PHP 7.2?
Hello,
does anyone have an idea when 2.1 is out - with PHP 7.3 support, I guess?
I will be forced to update to PHP 7.3 soon and I'm afraid this will break my forum. 2.0.16 doesn't seem to solve this if it supports only PHP 7.2, not 7.3.
Best wishes,
Mikael
2.0.16 will be released before 2.1 (but both don't have a fixed release date yet, they're ready when they're ready), see the 2.1rc2 thread (https://www.simplemachines.org/community/index.php?topic=566669.msg4025863#msg4025863).
Why isn't the bug tracker accessible to everyone, even if it's only read only? If it were open you'd potentially have a lot more people who could work on any bugs and who could test bug fixes
The 2.1 bugtracker is public (https://www.simplemachines.org/community/index.php?topic=566669.msg4035329#msg4035329). For 2.0.x, I believe there are copyright issues.
Quote from: SpacePhoenix on November 29, 2019, 07:39:49 AM
Why isn't the bug tracker accessible to everyone, even if it's only read only? If it were open you'd potentially have a lot more people who could work on any bugs and who could test bug fixes
No, you really wouldn't. The fact that 2.1 has been open for years, linked to in the header for years and still only has a few people working on it suggests that.
The main reason that the bug tracker for 2.0 is private is mostly because people are actually really bad at reporting actual SMF bugs when 99% of the time they are mod related.
After some good testing on a forum copy, live forum now 7.3, error logging off, out of sight, out of mind.
Goodnight, wake me up when .16 is there.
Quote from: a10 on November 29, 2019, 02:16:31 PM
After some good testing on a forum copy, live forum now 7.3, error logging off, out of sight, out of mind.
How can I turn off the error logging, please? And can I control that only some errors are ignored?
Quote from: TheEnemy42 on November 30, 2019, 06:05:33 AM
Quote from: a10 on November 29, 2019, 02:16:31 PM
After some good testing on a forum copy, live forum now 7.3, error logging off, out of sight, out of mind.
How can I turn off the error logging, please? And can I control that only some errors are ignored?
Admin > Configuration > Security and Moderation > General
Untick the "Enable error logging" box and save.
Thank you! I guess I'll have to go with this solution until I find a better way.
Besides deprecated warnings, will PHP 7.3 work on SMF 2.0.15?
PHP 7.1 is officially no longer supported and will not receive any security updates. I really hope that 2.0.16 is close to being released.
It should, nothing of the migration changes should come up in core SMF; as ever mileage will vary with mods.
Quote from: MobileCS on December 01, 2019, 01:53:56 PM
Besides deprecated warnings, will PHP 7.3 work on SMF 2.0.15?
PHP 7.1 is officially no longer supported and will not receive any security updates. I really hope that 2.0.16 is close to being released.
It does. I run PHP 7.3t on one of my servers for forum hosting.
Ok, that solved the issue for forum errors ... but my error log was slammed with deprecated warnings.
Adding "~E_DEPRECATED" to my php.ini file did not solve the issue.
Did I do something wrong?
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED
There are if I remember at least two spots in the SMF code that has to be set as well. Since SMF sets the error logging as well.
Oh, the PHP code for error logging overrides the php.ini file settings? That explains why my fix didn't work.
I'm assuming load.php and error.php are the files that need attention?
Just installed the newest version of WAMP. Clean install of 2.0.15, once installed it doesn't load any CSS file. PHP 7.4 loaded
QuoteDeprecated: Array and string offset access syntax with curly braces is deprecated
errors in places
Apart from that it seems to work ok
Is there a beta version available of 2.0.16?
There is no public version of 2.0.16. It is also quite a substantial update as it doesn't just cover that but also some GDPR functionality.
Also, I don't know if 2.0.16 even supports 7 4
Quote from: Kindred on December 03, 2019, 10:36:16 PM
Also, I don't know if 2.0.16 even supports 7 4
Found this via Google:
https://kinsta.com/blog/php-7-4/
Don't know if that covers all the changes, does it looks like any of the 2.0.16 code would fall foul of the changes?
Hilariously I think 7.4 will bring warnings in the log. Needs testing for sure.
Wonderful ... that means even more delays.
As opposed to worrying about 7.2 now and 7.4 in a future release, of course. And of course the hard work of volunteers is appreciated.
Of course! I do appreciate everything they have done.
It's just frustrating at times being held back from upgrading PHP due one piece of software. Now I'm stuck on PHP 7.1 - and it's no longer supported.
Have used 7.3 for some weeks, not seen any problems, and nothing reported by members. Am probably lucky because of using few modifications, which were all compatible.
So here it seems to only be a matter of not having to disable error logging :O)
But, in the wake of this php situation, a lingering feeling of unsecurity have arisen. Times are changing. For SMF, a matter of organisation, finance, goals, philosophy? What kind of contribution could be helpful from us simple users and ignorant peasants (ref. Monty Python))? Renumeration of a dedicated coding team (crowdfunding, actively seeking donations \ more charter members)?
Anyway, am hoping this great software (and great people) will have a great future.
Every bit of help is of course appreciated, but personally I think testing, bug hunting, bug fixing, active participation, translating - those would be ways to help with something concrete. If only we had more people interested in that side of things. The development is mostly public, anyone can follow and take part on Github. Other ways to help the project can be found behind the link in my signature :)
Quote from: Aleksi "Lex" Kilpinen on December 07, 2019, 01:49:41 AM
The development is mostly public, anyone can follow and take part on Github.
SMF 2.0 is not public at this time on github.
Well, yes wasn't thinking 2.0 specifically. Was speaking of the project as a whole.
I might be from help for testing. In few days I'm finishing my course and final work for QA software tester, so I hope that we can help in both directions. I need to learn a lot about testing and need tutors for sure, for manual testing and for Java/Selenium/TestNG. Where could I find better people to learn from than here, even if Java is maybe not your thing, but you all have wide knowledge. I made post here month ago https://www.simplemachines.org/community/index.php?topic=570364.0 and Suki replied and was in touch with me before I had to go to 100% focus on lectures because it was fast and very hard course to finish where I literally had hard homework 2 times each week and all my time dedicated for that. About manual testing, we mostly went through only theoretically, did some test cases for some sites in text document and in Jira, but still have to learn. I guess testing on which I can work can be Exploratory, Smoke, Sanity, Regression (without testing code), Cross-browser, Equivalence partitioning, Boundary Value Analysis, Load and Usability testing.
Based on cases, I can test some functionalities through Java/Selenium/TestNG, but since my first touch with Java was about 2 months ago, I'm still very newbie and have to go again with basics to understand things that I didn't since course was fast.
About all what we was working on course:
SQL & PostgreSQL (not sure what exactly is SQL Server Manager Studio and Toad for SQL server, but its in course description, getting tables), Java & Eclipse (Selenium, Selenium Webdriver, TestNG, POM), Apache POI for Word/Excel , PostMan, HTML and CSS. Also catching CSS Selectors or not sure how is called for TestNG tests, like this https://www.w3schools.com/jsref/dom_obj_all.asp
Have to learn after course Jenkins since its used with Jira, so will see where all that will go.
So, I can work on simple tasks on beginning and with time on some harder, but will definitely need tasks since I don't know on what details is your focus. I am community manager on SMF forums for years, like to investigate mods and so far I learned a lot about what things are good for forum and behavior of SMF is most of time known to me, not hard to notice if something is wrong, but we have different point of view on some things related with functionalities.
Hi, I'm new to the this forum so I'd like to say thank-you to the SMF team for bringing us this great software.
I'm running SMF 2.0.15 (with no mods) on PHP 7.1, but in mid-January my ISP is removing PHP 7.1 support.
I've read this thread and understand that my options are either to upgrade to SMF 2.1 RC2 or keep going with SMF 2.0.15 but to turn error logging off.
I'm going to continue with SMF 2.0.15 and switch to PHP 7.2 but, before I do that, I'd just like confirm that the only issue is with error logging. Also, I know that there is no firm date for the release of SMF 2.0.16, but is there a rough idea such as within the next 3 months or so?
Thanks in advance.
we don't provide dates, or rough estimates. it will be released when it is ready to be released and not a moment sooner.
due to the holidays it has slowed things down a bit, we are still working toward a release as soon as possible.
Quote from: Illori on December 09, 2019, 11:54:00 AM
we don't provide dates, or rough estimates. it will be released when it is ready to be released and not a moment sooner.
due to the holidays it has slowed things down a bit, we are still working toward a release as soon as possible.
Fair enough. Then I'd just like confirm that the only issue with PHP 7.2 and SMF 2.0.15 is with error logging and that turning this off is all I need to do. (I have no mods).
Yes it is, php error logging. You can edit SMF directly to disable in two spots to ignore those errors.
Didn't you post a mod that fixes 2.0.15 in php 7.2? Can't find it. >:(
there appear to be other issues caused by that 7.2 compat mod...
Quote from: vbgamer45 on December 09, 2019, 12:13:01 PM
Yes it is, php error logging. You can edit SMF directly to disable in two spots to ignore those errors.
Do you have more details on what to edit?
You need to modify the index.php file and the Sources/Errors.php file. However, that solution did not work for me.
The instructions are here : https://www.simplemachines.org/community/index.php?topic=506431.20
I had to edit my Apache httpd.conf file and set "LogLevel" to "warn" and disable the forum error logs (Admin » Configuration » Security and Moderation » General).
I'm running PHP 7.3 without issues now.
With my ISP I can't access the httpd.conf file so this is not an option for me.
I suppose my question now is this - if I set it to use PHP 7.2 and disable error logging are there any gotchas I need to be aware of? For example are errors actually being written to the DB and need to be cleaned out periodically?
No "gotchas " that I am aware of. If you disable forum error logging, no errors are written to the database.
However, your Apache error logs will still get hammered with depreciated warnings - unless you follow my instructions above - or disable Apache error logging completely.
Quote from: MobileCS on December 09, 2019, 04:14:44 PM
No "gotchas " that I am aware of. If you disable forum error logging, no errors are written to the database.
However, your Apache error logs will still get hammered with depreciated warnings - unless you follow my instructions above - or disable Apache error logging completely.
Right, I see. I'm not using a hosted server. My service provider doesn't provide access to Apache or its configuration so I guess it's not an issue.
I think you'll be just fine then.
I looked up Apache "LogLevel" and it actually defaults to "warn" (and that's what you want). I guess I manually adjusted my option a long time ago and forgot about it.
Quote from: Pogo Stick on December 09, 2019, 11:44:54 AM
I'm running SMF 2.0.15 (with no mods) on PHP 7.1, but in mid-January my ISP is removing PHP 7.1 support.
Why are they doing that?
I'm running my 2.0.15 forum on 5.6 and my ISP will allow me to set it to any version of PHP I want 5.6, 7.0, 7.1, 7.2 etc.
My ISP doesn't support any PHP version below 7.2 since Dec. 1. I really hope 2.0.16 is coming soon. I'm not having any trouble so far (using 7.2 atm) but the error logs get bigger and bigger after each login.
Quote from: landyvlad on December 18, 2019, 12:08:15 AM
my ISP will allow me to set it to any version of PHP I want 5.6, 7.0, 7.1, 7.2 etc.
Hosters chosing to only offer current\ supported \ secure \ updated software are doing the right thing 100% imo, f.ex. in context of the ongoing extreme amounts of online criminal activity. Am hoping SMF will keep up with the changing times.
Chances are that for hosts, what versions they support is going to be down to costs. if it ends up costing them too much to deal with older versions of PHP then chances are they'll axe them
Am looking upon the old php's like win95, xt, vista, 7, still working fine for many tasks, but definitely nothing one would chose to base one's future upon.
php lifespan
https://www.php.net/supported-versions.php
Quote from: fungolfer on December 18, 2019, 02:51:39 AM
My ISP doesn't support any PHP version below 7.2 since Dec. 1. I really hope 2.0.16 is coming soon. I'm not having any trouble so far (using 7.2 atm) but the error logs get bigger and bigger after each login.
You can turn off smf error logging for now under settings. Just rememer to reenable it.
Yeah I know. :)
Did that before and will do that again now. It was just a reply to Landyvlad so he can see that many ISP don't support older versions of PHP anymore.
Cheers :)
For me (and I don't mean my SMF stuff) this is very important:
Quote from: a10 on December 18, 2019, 02:48:07 PM
Am looking upon the old php's like win95, xt, vista, 7, still working fine for many tasks, but definitely nothing one would chose to base one's future upon.
Yes indeed.
My (side) business website was built on a platform (PHP_Directory) that is no longer maintained by the author, and is only compatible up to PHP 5.6. Any upgrade to 7.x will stop it from working, something that I cannot have happen.
So I am now nearly finished the process of having the site redone on a much more extensively used platform, which caters for PHP upgrades indefinitely. (There were also other reasons for the change, but the PHP issue certainly was the most critical)
Quote from: efk on December 07, 2019, 06:45:40 PM
I might be from help for testing.
I also have plans for (automated) testing and am currently experimenting with this a bit. Sadly, my setup is only on my home PC, because I don't have a VPS big enough to handle the requirements.
Feel free to throw me a PM though.
To those who were worried about php 7.1 going away: SMF 2.0.16 Released (https://www.simplemachines.org/community/index.php?topic=570986.0;topicseen).
Months passing by, was beginning to doubt, was it time to, sadly, look into a new forum platform, but hey, sudden surprise and relief! The best available software imo has been revived. Great job.
Seeing the amount of improvements, changes and work, am understanding why it took, and needed, time.
Now, can only imagine the hours and long nights gone into this, they deserve all the support they can get > evaluate a charter membership, feels good at the giving end, does good at the receiving end :O)
I'm running 2.0.17 and when I switch from php 5.6 to 7+ I loose functionality. ie, when I try to access the security and moderation pages, I get a white, "This page isn't working" page.
Any ideas why?
Any mods?
Lots. Do you think that could be causing the problem?
Since SMF 2.0.17 supports PHP7.2+, and many mods don't, that's very likely.
Off course that is possible: the SMF code may be updated to support php 7, but every mod adds code: that code is not updated by SMF, so a simple mod with non-compliant code can stop your forum from functioning on a PHP version that SMF supports but the mod code does not...
So starting with the most likely ones first, I need to uninstall them one at a time and try 7+.
Thanks for your reply
also next time you would be best to open your own topic for your issue.