Dear Users,
Simple Machines is proud to announce the release of the 3rd Beta of SMF 2.1. This version contains many improvements over Beta 2 and also fixes many bugs that were discovered following its release.
Among the notable improvements:
- Added reCAPTCHA as core feature to keep spammers away.
- Upgrade.php code clean-up. Now the upgrade process should be more consistent.
- RSS general improvements.
- Added support for jQuery 3.x.
- Modified Curve2 to improve the responsiveness of the design.
- General bug fixes, code improvements, and clean-up.
- Default codification will now be UTF-8.
For full details of what has changed, please see our GitHub repo (https://github.com/SimpleMachines/SMF2.1).
The general installation/upgrade procedure of this Beta release remains the same, however,
once you upgrade from an older version to 2.1 you cannot go back, so please take careful consideration before upgrading any live site. Have a look at Installing and Upgrading SMF (https://wiki.simplemachines.org/smf/Category:Installing_and_Upgrading) in the Online Manual to find out more. You cannot upgrade to 2.1 Beta 3 via the package manager; instead you will need to carry out the Large Upgrade process. SMF 2.1 can be obtained from the download section (https://download.simplemachines.org/).
Please note that because this is a beta release, translations and language strings other than English have not been finalized and may not yet be complete.
Finally, as always, this topic is not for support. Discussion and support for 2.1 can be found in the 2.1 support board (https://www.simplemachines.org/community/index.php?board=254.0).
Finally, thanks to all of the team and development contributors (https://github.com/SimpleMachines/SMF2.1/graphs/contributors) who have brought us one step closer to a release candidate. On behalf of the project, we appreciate the time, energy and contributions you have made.
Thank you for using SMF
Kind regards,
Simple Machines Forum Team
Good to see 2.1 moving forward. I await when it becomes a stable and recommended for live sites.
Very nice work, thank you so much to everybody contributing and making this release possible! :)
Congrats team!
Yeah, baby!
Been a long time coming, glad to see the progress.
Nice! :)
Beautiful.
Well done, team, SMF rocks! I hope the next beta/RC release will not take a further 2 years :)
Using 2.1 in live site for 2 years and evertything works just fine.
Great work!
WOOHOO!!!
I have to say that I'm looking forward to 2.1 more than any other software upgrade in recent years.
Party on, dudes.
8)
Good Job!
Thank you all, great work!
This rate next release be 2019 ...
Good to see an improved proxy.php in there ;)
Quote from: Shambles on June 01, 2017, 10:45:13 AM
Good to see an improved proxy.php in there ;)
Will be properly fixed too in the next release.
The downloadable Large upgrade zip file seems to lack upgrade-helper.php, however, after manually putting it in the right place, things went smoothly. Mad props to the dev team!
+1 internets to you 8)
We've fixed that. The upgrade packages now include that file.
The full install ZIP package is missing the file: Settings_bak.php
I also spotted some issues this morning testing it you can read about posted here:
Link: https://theadminzone.com/threads/smf-2-1-beta-3-released.144396/
QuoteI tested it today and think I spotted two issues. One, they didn't appear to include the "Settings_bak.php" file in the package (it's missing) but needed. Also, when I enabled the Calender and tried to visit it on the front-end. I get a blank page and later compared URL used leading to it with SMF 2.0 installed (stable version). Both use exact same URL link leading to calendar and works fine with stable version - not with the Beta 3 of 2.1 though it didn't. I tested both versions on purpose to rule out the page not being blocked by Mod Sec - but both versions used same URL link leading to Calendar. So not sure why it shows for 2.0 version and not Beta 3 of 2.1 on front-end?
Also tested it running under both PHP 7.0 and 7.1, not sure about this one - but both was giving error logs from cache directory (when cache was enabled) to indicate something used in a PHP file might now be depreciated. Soon as I switched to PHP 5.6 the error logs stopped, so it seems linked with using PHP 7+ unless I'm missing a php module that needs be activated causing it
Thank you for testing... it is a beta, after all...
However, I will say, reporting issues on another site is useless. Here or github are the only places that reports should be made.
Also, that report is nonsense. Settings_bak.php is not supposed to be included, it's a backup of the main Settings.php file made when changes are made to the file. Why would it be included when it can *always* be regenerated by the software itself whenever it is needed?
Quote from: Arantor on June 02, 2017, 04:45:34 AM
Also, that report is nonsense. Settings_bak.php is not supposed to be included, it's a backup of the main Settings.php file made when changes are made to the file. Why would it be included when it can *always* be regenerated by the software itself whenever it is needed?
So why is one included with SMF 2.0 download package then? You can always download both 2.0.14 and 2.1 Beta 3 and compare it to see for yourself. ;D
And when you say one gets generated auto on server after making changes to settings. Not so sure about that, one didn't get auto created on mine after saving some server settings. I still kept seeing the warning text saying Settings_bak.php permissions was wrong - then when looking on host saw none was present.
*shrug* That's what's _supposed_ to happen, at least. That's what the _bak part indicates, it's a backup.
Thanks all. Just giving this new beta a try locally. Noticed this in the admin center.
Support Information
Version Information:
Forum version: SMF 2.1 Beta 3
Current SMF version: SMF 2.1 Beta 2
(more detailed)
Can't wait!
Keep up the good work guys.
Thanks.
Quote from: lurkalot on June 02, 2017, 03:21:07 PM
Thanks all. Just giving this new beta a try locally. Noticed this in the admin center.
Run the Fetch Simple Machines Files scheduled task and it should update.
Great work :)
Awesome! Cannot wait until the final release, 2.1 looks to be great just like any other SMF version! I'm going to test beta 3 on a local server tomorrow and give back some feedback about it. ^^
Off topic and non-English posts removed. Please only use English in English language boards and stay on topic. Thank you.
Well done to all involved! ;)
at last , we see some progress here :D
*waitingpatientlyforfinal
Very Nice- Congratulations
Cannot wait for the official release!
Great work everybody :).
Good job
Applause... well done everyone involved.
Good job sir. Great work.
cool beans, upgrade to my beta board worked without a hitch.
keep on keeping on!
Looking forward to the progress.
Yeayyy!!!!
Well done team proud of you>.....Thanks for the best product.
Unfotunately it failed for me. I followed the proposed large upgrade procedure (exact like I done the beta's before):
Notice: Undefined index: db_mb4 in /www/htdocs/xxxxx/forum_smf/Sources/Load.php on line 89
Any ideas? It's kinda small Testforum and sure I have backups but like to know how to avoid this.
Thanks for your time!
cheers!
Quote from: Serena Butler on July 06, 2017, 08:48:01 AM
Unfotunately it failed for me. I followed the proposed large upgrade procedure (exact like I done the beta's before):
Notice: Undefined index: db_mb4 in /www/htdocs/xxxxx/forum_smf/Sources/Load.php on line 89
Any ideas? It's kinda small Testforum and sure I have backups but like to know how to avoid this.
Thanks for your time!
cheers!
Selena please do your support requests at the appropriate board: https://www.simplemachines.org/community/index.php?board=254.0
Yes wait.....thank you
Subs-db-mysql.php file has a utf8 problem on db connection created in ssi.php
Row 384 Subs-db-mysql.php
$connection->set_charset("utf8");
https://github.com/SimpleMachines/SMF2.1/issues/4205
Define "problem".
Quote from: Colin on May 31, 2017, 09:21:59 PMFinally, as always, this topic is not for support.
Edited to remove quoted spam post, which had been deleted - Iris.
The beta3 is quite usable as it is, and beta4 is startet upon- on Github at least.
I am developing a new SMF theme for 2.1 beta3/beta4 and see no problem starting to use this version. No need to wait until RC versions - the more that use betas the quicker any issues can be dealt with and the sooner we can get to that stable RC version. I remember using 2.0 betas long before any 2.0 stable versions and there were quite a few changes in the default theme back then, from one beta to another.
It is perfectly fine to use the Beta version in a sandboxed personal environment, but we do discourage running any Beta version in a production environment. We certainly appreciate you testing SMF 2.1 and ultimately how you use it even in the beta stage is at your discretion.
After struggling with SMF V2.0.14, I installed this BETA version and still found the same bug...
I log in as admin and when I try to log out it gives an error... also if you log in with registered members they log into each others accounts. I tried to downgrade to previous version but seems like you can't... Been using SMF on all my previous websites and it worked great! Hope you guys will fix this soon... And also... can't install any themes on BETA...
Please don't use this thread for support. Start a new topic in the right board, and you'll receive support there.
I have to say that I'm looking forward to 2.1 more than any other software upgrade in recent years. glad to see the progress.
Link to website removed. Please avoid putting links to your website in your replies, otherwise you will be warned for spamming - Iris.
how can i fix this error: /home/club206/domains/club-206.ro/public_html/Sources/Subs.php
==>3311: $path = $modSettings['attachmentUploadDir'][$modSettings['currentAttachmentUploadDir']];
3312:
Thanks!
le. i have beta 2 from the begining .. and i cannot pas to a stable smf :( is a live forum...well almoust dead because of fb:)
Quote from: Colin on May 31, 2017, 09:21:59 PM
Finally, as always, this topic is not for support. Discussion and support for 2.1 can be found in the 2.1 support board (https://www.simplemachines.org/community/index.php?board=254.0).
Congratulations
How is it going with final release of 2.1? ::)
It'll be ready when it's ready. We don't give ETAs on release dates, besides, it still needs to go through the RC phase first.
The offtopic discussion has been merged with the existing topic in Chit Chat. Thanks.
It's a bit difficult to setup, but it works smoothly.
This SMF 2.1 Beta 3 is not working properly i used this one 1 week after that i uninstalled
Quote from: Astrorushi on October 23, 2017, 08:20:34 AM
This SMF 2.1 Beta 3 is not working properly i used this one 1 week after that i uninstalled
Well, that's why it is called a beta. It would be helpful if you could detail what "wasn't working" in the bug reports or support section so it can be fixed.
Quote from: Astrorushi on October 23, 2017, 08:20:34 AM
This SMF 2.1 Beta 3 is not working properly i used this one 1 week after that i uninstalled
Thats pretty vague though, hopefully you were not looking for some magic out of SMF .. :)
Still sad to know SMF didn't work out for you.
Congrats devs!
Can't wait for the RC/Final when it's ready!
How come it's called SMF 2.1 instead of SMF 3.0, if it's going to be so different from 2.0... ?
Because the plan was to release a small upgrade while 3.0 was being worked on. Then people added more and more and more, but I think calling it 3.0 would be a mistake.
How far away is 2.1 official release? ::)
At least another year, possibly longer.
Well done, team, SMF rocks!
Its great news for SMF users
Quote from: Arantor on November 22, 2017, 02:37:34 PM
At least another year, possibly longer.
So are you saying that updating mods for this version can be a frivolous endeavor wrapped in an enigma of frustration?
Hopefully not. We are getting there, but yes mods shouldn't be updated until a release candidate.
Thank you. :) Looking forward to the release candidate.
Quote from: butchs on December 31, 2017, 09:40:00 PM
Quote from: Arantor on November 22, 2017, 02:37:34 PM
At least another year, possibly longer.
So are you saying that updating mods for this version can be a frivolous endeavor wrapped in an enigma of frustration?
Not entirely. A lot of the mod related stuff in 2.1 was added because I updated my mods to work with 2.1. Whenever there was a feature one mod needed I added it, whenever a mod borked something in SMF I fixed it.
So if you are in a helping mood, you could update a mod and help us find errors, merely testing the code via using the mod related features would help us a lot.
Quote from: Arantor on November 22, 2017, 02:37:34 PM
At least another year, possibly longer.
Well then, I have no more patience. I'm waiting for so many years to get a modern smf (for example user mentions) and there are so many other things that are available in other forums. I will convert to another system now.
Even though you can have mentions as an add-on today, of course...
He thinks that by telling us he's going to switch, we will suddenly and miraculously discover that 2.1 is ready for release just to make him stay....
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
or not....
Quote from: Kindred on January 18, 2018, 02:38:54 PM
He thinks that by telling us he's going to switch, we will suddenly and miraculously discover that 2.1 is ready for release just to make him stay....
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
or not....
I've been waiting for world peace, since I was born still waiting. :-P
I like stability........... not instability. A hastened release would no doubt be less desirable, and then that what people
that wanted it now would complain about. I work months before I even open up websites using this software,
would stand to reason real significant releases to update would take years. I am not a developer but had been in the past
and I always hated version updates that were fixes and people used full upgrade status not update status as they should
is pet peeve of mine. I was around when the first SMF betas were being tested and rightly so there were so many fixes, and even though one
could install it; it took a long time for solid release to happen. This is the want it now generation, having no idea that quality is worth the time.
My two cents.
He is a she and no, she is not.
Moving to another system is entirely up to you ... in the meantime, back on topic please ... :)
2.1 release schedule discussion moved to Chit Chat: https://www.simplemachines.org/community/index.php?topic=558433.0
Anybody running a live site anywhere to take a look at it in action?
Quote from: njtweb on April 27, 2018, 09:15:38 AM
Anybody running a live site anywhere to take a look at it in action?
Testing @ test2.fjr-club.nl
But it is a full copy so should give an idea...
https://www.whatsurbeef.net (smf 2.1 beta 4)
Quote from: Bigguy on April 27, 2018, 02:50:50 PM
https://www.whatsurbeef.net (smf 2.1 beta 4)
Interesting. Thank you
I need to update it again. Last time it was updated was about 3 weeks ago or so I think.
Quote from: Bigguy on April 28, 2018, 09:37:21 AM
I need to update it again. Last time it was updated was about 3 weeks ago or so I think.
How often do you update ? I'm thinking of migrating to 2.1 (yes I know not recommended) but it's a small forum and I think the benefits make it worth while. On the plus side will help with the testing / fault finding ;D
I update when I think there has been a lot progress on GH.
When you use the nightly download: https://www.simplemachines.org/community/index.php?topic=558451.0
you got a file with a url in there,
where you see how mutch commits/changes are behinde and
so you can "scan" if some changes could break (mostly when upgrade/install file get touches) your setup.
Thanks Guys.. going to build a test forum with 2.1 so I can get more familiar with it and then decide if to make it live.
Testing with it is a good thing. Taking it live is a different story. To keep it up to date there is a lot of updating to do. Not to many mods or themes are out for it yet either.
You outdid yourselves with this version guys. Keep up the great work.
I have one question though, someone said that Smf 2.1. has been in development for 6 years and it has not reached the stable version yet. What is with the delay? 6 years is quite a long time to be spent on one version imho.
Quote from: kevinsystorm89
... in development for 6 years and it has not reached the stable version yet. What is with the delay? 6 years is quite a long time to be spent on one version imho.
Answers can be found in the 2.1 Discussion board
https://www.simplemachines.org/community/index.php?board=254.0
Do you want a good, solid, secure piece of software or do you want something fast? You cant have both.
We are all volunteers, including the developers. They work when they have the time to do so and the software will be released when it's ready, not by any arbitrary timeline.
As Kindred said. And as much as we'd love to see it released soon, we have to go with the pace everyone has time to work with. Because of this, any help is always appreciated, be it with small fixes, to reporting bugs, translations, etc :)
Here my german 2.1 Beta4 page (https://www.stephan-frank.de). With custom page and own themes.
2.1 is on a very good way and the developers are doing a very good job :)
Quote from: wintstar on May 26, 2018, 04:50:33 AM
Here my german 2.1 Beta4 page (https://www.stephan-frank.de). With custom page and own themes.
2.1 is on a very good way and the developers are doing a very good job :)
How the heck did you get 2.1 Beta 4? As far as I can see there's only up to 2.1 Beta 3 on the download site.
Unless I'm missing something major.
Github has 2.1 beta 4
Quote from: Torngate on June 07, 2018, 10:31:36 PM
How the heck did you get 2.1 Beta 4? As far as I can see there's only up to 2.1 Beta 3 on the download site.
Unless I'm missing something major.
Since the release of Beta 3, the version on GitHub has been marked as Beta 4. You can get access to it at https://github.com/SimpleMachines/SMF2.1 (https://github.com/SimpleMachines/SMF2.1).
It should not be used on a live site though. With that said, you should not be running beta 3 either, as it is out-dated.
(https://s15.postimg.cc/okemqtlcr/do-not-eat2020.jpg) (https://postimages.org/)
:D
Quote from: wintstar on May 26, 2018, 04:50:33 AM
Here my german 2.1 Beta4 page (https://www.stephan-frank.de). With custom page and own themes.
2.1 is on a very good way and the developers are doing a very good job :)
That looks good mate.
A question - the background image with transparency etc. Is that a feature of 2.1 (or something also available in 2.0 that I've missed).
What have you changed in the theme itself? It doesn't look all that different to my 2.1beta3 as far as I can tell from memory :)
No it is not a feature. I did the same on my site but a little different. Most of it is just css edits with a bit of playin around in a template file or two.
I wonder if that could be done with a mod?
Hint: write a mod to do it please ! :)
Possibly... but for the default theme only, the mod probably wouldn't work on other themes.
That's cool I only plan on using Curve2 anyway.
Yeah, Curve2 is a great theme ;). I like it a lot ;).
Quote from: landyvlad on June 24, 2018, 10:18:08 PM
Quote from: wintstar on May 26, 2018, 04:50:33 AM
Here my german 2.1 Beta4 page (https://www.stephan-frank.de). With custom page and own themes.
2.1 is on a very good way and the developers are doing a very good job :)
That looks good mate.
A question - the background image with transparency etc. Is that a feature of 2.1 (or something also available in 2.0 that I've missed).
What have you changed in the theme itself? It doesn't look all that different to my 2.1beta3 as far as I can tell from memory :)
I only copied the default theme, pasted a background image and customized the css. The first and reference page is not a mod. I added it to the system. I don't like the portal system. Too much for me. Download and contact page are Mods from 2.0. These I adapted to the GDPR. Not a big action.
Will this version be fully compatible to PHP 7?
Yes, although the current version (2.0.15) is also ready to go with PHP 7. It's just plugins that aren't.
Quote from: GigaWatt on June 28, 2018, 08:27:09 AM
Yeah, Curve2 is a great theme ;). I like it a lot ;).
I totally agree !
This is beta4 release?
https://github.com/SimpleMachines/SMF2.1
There is no official beta 4 release yet - but the code literally gets updated nearly every day so a 'beta 4 release' could be anything from a few months ago until today.
Beta 4 mu or rc1 will occur which will be released ????
At the moment, beta 4 is a working title. Time will tell if it will be an rc or a beta.
I largely suspect the next release will actually be called RC1. Right now the code calls itself beta 4, however given how close the list of 'RC1 items' is, it's quite possible that beta 4 will be skipped and go straight to RC 1.
Quote from: Arantor on July 23, 2018, 02:13:12 PM
I largely suspect the next release will actually be called RC1. Right now the code calls itself beta 4, however given how close the list of 'RC1 items' is, it's quite possible that beta 4 will be skipped and go straight to RC 1.
hope come rc version
But why, though? What does it being called 'RC1' get you that it being called 'beta 4' doesn't? It's just a version number - until final happens, it doesn't *really* mean anything.
If anything, a repeat of 2.0 would be bad - 2.0 RC1 wasn't actually that great.
Quote from: Arantor on July 23, 2018, 02:26:35 PM
But why, though? What does it being called 'RC1' get you that it being called 'beta 4' doesn't? It's just a version number - until final happens, it doesn't *really* mean anything.
If anything, a repeat of 2.0 would be bad - 2.0 RC1 wasn't actually that great.
I do not believe in 4 years now rc1 e
So what? If the next release were called beta 4, or it were called RC1, it's still an in-development project, simple as that.
Is my understanding correct that the real "difference" is -
beta - lots of changes, regularly. Strongly recommended NOT to be used in production.
RC - theoretically stable for production use, but still in a work in progress.
Final - good to go, install away and enjoy !
RC basically means the product should be ready to use, and the devs believe it does not have any major issues anymore.
Ideally, RC and final would be nearly identical.
All I'll say is look at what happened with 2.0.
Quote from: landyvlad on July 24, 2018, 08:32:18 PM
RC - theoretically stable for production use, but still in a work in progress.
RC is short for Release Candidate. It means "we hope the product is ready for a Final releases, but we're not really sure yet, there might still be a few small bugs, so basically, it's more or less safe to use, but with caution"... also, it's still not advisable to use a RC on anything that you've invested in.
I say again: look at 2.0 ;)
Specifically compare 2.0 RC1 to 2.0.0, or even 2.0 RC1 to 2.0 RC2.
Yes, well. I did say ideally. 2.0 RC was not an ideal case really.
Hopefully the lessons from 2.0 will mean we won't see/required RC1, RC2, RC3 etc
I know everyone is looking forward to 2.1 Final - hopefully that won't be TOO far off, but only time will tell.
Quote from: Arantor on July 25, 2018, 02:40:20 AM
All I'll say is look at what happened with 2.0.
A huge management mistake ?
No, the fact that Curve wasn't ready for RC1, came out in RC2, overhauled significantly in RC3. Or the hasty introduction of protected groups in RC4. Or the release of RC5 to reassure some of the... political agitants that SMF hadn't backed itself into a corner.
I know only one thing, that everyone is eagerly awaiting the official stable version. ::)
Please make it faster... :-\
I am also super excited for SMF 2.1 to come out, but remember... Good things take time. :)
Is everybody happily wasting time fighting about words again?
I remember I posted a thread named "congratulations SMF on the 7th birthday of SMF 2.0 Gold" and it was deleted right away. What I wanted to draw the attention to was this:
Is it not possible for some here to stick to the subject and/or the work?
FACT is: 2.0 GOLD is 7 years old and 2.1 is long overdue
FACT is: the team has changed and learned from its mismanagement
FACT is: suggestions are worthless because everything is swept off the table with "it's feature-locked"
I am looking forward to seeing a release finally coming, so all these nervecutting word-wars about nothing can
finally take their end and features and improvements can be discussed again.
Thumbs up, team!
QuoteFACT is: 2.0 GOLD is 7 years old and 2.1 is long overdue
Correct. It was never meant to be a big release was already overdue 5 years ago when I tried to re-rail it, though I consciously added new features to it then because a release that no-one cared about because it had nothing compelling in it was worse than no release at all. But even I never expected it to take another 5 years.
QuoteFACT is: the team has changed and learned from its mismanagement
You say this with such certainty.
QuoteFACT is: suggestions are worthless because everything is swept off the table with "it's feature-locked"
Most suggestions are not worthless because of feature lock. Most suggestions aren't worth much because they're not really suitable for a generic piece of software - many of them would be very suitable if building a gaming forum or a roleplay forum or some other specific kind of forum, but not a general purpose forum.
Quoteso all these nervecutting word-wars about nothing can finally take their end
They're not about nothing. They're just about things you don't care about - that doesn't mean others don't care.
"Plus ça change, plus c'est la même chose" -- Jean-Baptiste Alphonse Karr
This is more directed to the "Jr. Member" that thinks they know everything. You don't.
"This has been a rare sighting of the Emergency Bear Activation program. Had this been a test, your chances of survival would be greatly increased."
// Back to the shadows...
Hey Douglas, long time no see.
SMF is still one of my favorite forum systems, sadly reddit is attacking the personal community structure as new users of the internet don't understand anything outside of it.
Hi Doug! :)
NICE!! ;)
Alright, just upgraded my dev-site to 2.1. Let's see what's under the hood shall we? :P
you used the github version, right?
The download version of beta 3 is WAY out of date at this point.
Quote from: Kindred on August 16, 2018, 09:31:10 AM
you used the github version, right?
The download version of beta 3 is WAY out of date at this point.
Oh i didnt see you post... ol' boy just point it out your post ;) thank you.
Question from a SMF newbie...
Safe to assume that 'eventually', 2.1 will be available via package manager?
I'm on 2.0.15 but like I said... newbie with this particular forum software. Not sure if I'm ready to tackle a manual install.
Thanks in advance.
no.
2.1 will be a major release... this means you must use the upgrade archive/process, not the patch process.
You will never be able to upgrade from a 2.0.x release to a 2.1.x release by using the package manager
When will we be expecting the full release
Quote from: Richard K on October 03, 2018, 12:38:59 AM
When will we be expecting the full release
When it's done, same as ever.
Will this 'new' version have a mobile friendly theme as default?
Yes, it comes with a responsive theme as the default theme.
I know we can't ask on time frames but how is this going because I've just noticed beta 3 is from 2017
If you want, you can check on Github. Work is ongoing, and progress is being made. https://github.com/SimpleMachines
Quote from: Arantor on October 03, 2018, 03:04:45 AM
Quote from: Richard K on October 03, 2018, 12:38:59 AM
When will we be expecting the full release
When it's done, same as ever.
Feature request: Auto-responder to save Arantor the trouble every time ;)
Then it needs a secondary feature, to track the estimated date and bump it by a week every time someone asks, or if they complain about it taking too long.
Quote from: Arantor on October 19, 2018, 08:56:37 AM
Then it needs a secondary feature, to track the estimated date and bump it by a week every time someone asks, or if they complain about it taking too long.
;D
I only hope that when SMF 2.1 be released, it will not be much outdated or big step backwards compared to other forum scripts :-X SMF is a amazing and solid software but needs a little speed up in developing ;)
If I were to point out that XenForo 2.1 is shipping native desktop/mobile push notifications (except iPhone/iPad) without needing an app, and that when XF first started out, SMF 2.0 was still trying to make Curve 1... I'll let you be the judge of 'compared to other forum scripts'.
meanwhile, *rubs out previous release date, adds another month*
Quote from: Nolt on October 20, 2018, 03:56:57 PM
I only hope that when SMF 2.1 be released, it will not be much outdated or big step backwards compared to other forum scripts :-X SMF is a amazing and solid software but needs a little speed up in developing ;)
I've been thinking the very same thing and I still remember the team saying this release wouldn't take as long as the last, I forget how many years ago that was now
tbh its already behind others
2.0 released in 2011.
*rubs out the 2.1 release date in the secret board, adds another week to the date*
Quote from: movierchives on October 21, 2018, 01:54:24 PM
Quote from: Nolt on October 20, 2018, 03:56:57 PM
I only hope that when SMF 2.1 be released, it will not be much outdated or big step backwards compared to other forum scripts :-X SMF is a amazing and solid software but needs a little speed up in developing ;)
I've been thinking the very same thing and I still remember the team saying this release wouldn't take as long as the last, I forget how many years ago that was now
We don't have enough developers to move it along faster, plain and simple. Maybe the situation was different back then (I wasn't around for that)
Maybe if more people tried to help instead of just complaining it would be already finished. Remember this is an open source project and no one is paid to work on it.
Personally as a viewer of GH on a daily basis, I think the progress has been going very good recently.
Anyone who wants to help speed us along is more than welcome to help out (https://github.com/SimpleMachines/SMF2.1/issues).
They should also check this link. It looks real good I think:
https://github.com/SimpleMachines/SMF2.1/milestones
Quote from: Bigguy on October 21, 2018, 04:23:58 PM
They should also check this link. It looks real good I think:
https://github.com/SimpleMachines/SMF2.1/milestones
Yes been following. Very tempted like you @Bigguy make my site live with this beta version and help with the bug identification / issues.
Any help from all would be great. ;)
Quote from: Gwenwyfar on October 21, 2018, 03:36:11 PM
We don't have enough developers to move it along faster, plain and simple. Maybe the situation was different back then (I wasn't around for that)
Maybe if more people tried to help instead of just complaining it would be already finished. Remember this is an open source project and no one is paid to work on it.
I totally agree with you and I regret we lack of more devs to help :'(
I think that users who visit this site are just concern that nothing is going on with 2.1 progress. People just like reading news rather than visiting GIT and check milestone or bug tracker. In past we had more SMF 2.0 WIP released than now.
Mine point is that maybe would be better to post a news from time to time about the progress (even when no new beta/rc are released) rather than nothing.
Quote from: Bigguy on October 21, 2018, 03:48:27 PM
Personally as a viewer of GH on a daily basis, I think the progress has been going very good recently.
That's true, fingers crossed to keep with this work.
Need a bigger hammer :P
Lol
A saying in Germany says:
Good things take time :)
2.1 is on the right track.
Quote from: Bigguy on October 21, 2018, 04:23:58 PM
They should also check this link. It looks real good I think:
https://github.com/SimpleMachines/SMF2.1/milestones
I don't get that, RC1 93% complete and RC2 32% complete
So two release candidates are being worked on at the same time? :o
No, just some issues and stuff are tagged for RC1 while some others are tagged for RC2. RC1 tagged issues must be solved for RC1 release, and RC2 ones dont.
Quote from: Nolt on October 21, 2018, 07:05:47 PM
I think that users who visit this site are just concern that nothing is going on with 2.1 progress. People just like reading news rather than visiting GIT and check milestone or bug tracker. In past we had more SMF 2.0 WIP released than now.
Mine point is that maybe would be better to post a news from time to time about the progress (even when no new beta/rc are released) rather than nothing.
Maybe. Though if that is done it would likely go into dev blog rather than this news section.
Quote from: movierchives on October 23, 2018, 10:46:06 AM
Quote from: Bigguy on October 21, 2018, 04:23:58 PM
They should also check this link. It looks real good I think:
https://github.com/SimpleMachines/SMF2.1/milestones
I don't get that, RC1 93% complete and RC2 32% complete
So two release candidates are being worked on at the same time? :o
technically, yes.... dozens of versions may be worked on "at the same time"
Issues get tagged to a version for release. Those issues MAY get addressed before the release even officially starts work.... or an issue that was addressed for RC1 may have been bumped out to RC2 - and so forth.
Realistically, don't worry about anything except the next release - and even then, the stats are more fluid than fixed, given that issues can be pushed out ot brought in, depending on severity, etc.
Fluid is right. I have seen RC1 go from 95% complete to 83% complete in the blink of an eye. All who work on it are working hard to get it out. One fix might cause two bugs and they have to be fixed and so on. It's frustrating sometimes, lol.
Quote from: Bigguy on October 23, 2018, 06:04:08 PM
It's frustrating sometimes, lol.
Coding usually is :P... considering it's consisted of 5% of the time actually coding, 95% fixing bugs, LOL :D.
and code just gets more annoying when you know several languages. Can't mix PHP and C#, for example.
(https://i.postimg.cc/wvhbf0XF/Untitled-1.png)
That's a very nice pic. Gotta love it. :)
For better or worse, in Github, random contributors submit whatever they want to, whenever they want to. Most get bent out of shape when their prs aren't mmediately tested and merged by the devs.
Which uses up dev time. A lot of it. (And who really wants to spend days and weeks testing someone else's stuff?)
But they don't want to discourage good contributions.
So...
You prioritize. It's a basic, minimalist, workable, self defense mechanism.
And submissions come in all over the map.
I welcome the recent focus on specifying RCs. It sets priorities and expectations. RC2 is a polite way of saying well look at your contribution. Later.
It's a good thing.
Quote from: Bigguy on October 21, 2018, 04:23:58 PM
They should also check this link. It looks real good I think:
https://github.com/SimpleMachines/SMF2.1/milestones
^^^^ This really gives hope! ^^^^ You made my day!
Just in the very first topic on git hub that I open
(https://github.com/SimpleMachines/SMF2.1/issues/4930)
I read this:
quote:
"team should inform community better"
That hits the nail on the head.
Different people, different opinions.
Not sure that was the intention of the comment, but either way, I agree. The problem is we just don't have anyone focused on this because everyone is busy doing other things.
Loving seeing the progress y'all are making. Wish I had the programming aptitude to help out, but alas 'tis not to be.
Keep up the good work!
There are still outdated 2.1 Beta 3 (https://download.simplemachines.org/) available for download, although they are outdated. Also the language packs for it. The current beta archives of Github should be offered, so that you can also test at the current state. Very often there were error messages. It turned out then sometime that it was an outdated Beta3 archive. This should also be changed. The few know that on Github already Beta4 is active. Also applies to the outdated language packs that are still recommended => https://www.simplemachines.org/community/index.php?topic=562247.0 (https://www.simplemachines.org/community/index.php?topic=562247.0)
can't it be a little speedy rc version rc can be completed this year ?
+1 month
we will wait and see the end of +1 month :o
No, every time someone asks if it can be done quicker, we add another month to how long it's already going to take.
Just in the last week alone, the next release date has extended by over three months.
Quote from: wintstar on October 29, 2018, 04:18:06 AM
There are still outdated 2.1 Beta 3 (https://download.simplemachines.org/) available for download, although they are outdated. Also the language packs for it. The current beta archives of Github should be offered, so that you can also test at the current state. Very often there were error messages. It turned out then sometime that it was an outdated Beta3 archive. This should also be changed. The few know that on Github already Beta4 is active. Also applies to the outdated language packs that are still recommended => https://www.simplemachines.org/community/index.php?topic=562247.0 (https://www.simplemachines.org/community/index.php?topic=562247.0)
but beta 3 is an official release, beta 4 is just something the files on github are called for some reason.
Quote from: Arantor on October 29, 2018, 03:47:17 PM
No, every time someone asks if it can be done quicker, we add another month to how long it's already going to take.
Just in the last week alone, the next release date has extended by over three months.
So, a Duke Nukem Forever type release schedule? lol
No, not a DNF schedule, just one that is realistic. Every complaint makes it take longer.
but beta 3 is an official release, beta 4 is just something the files on github are called for some reason.
It is not logical to offer Beta3 here for testing and to be much further on Github. Some report bugs from Beta 3 that are already fixed on Github.
That's no way to get testers, no way to get ahead. On Github is working on Beta4, so why not officially release it?
Beta 4 is still being worked on. It is not ready to be released.
Quote from: wintstar on October 29, 2018, 04:43:30 PMIt is not logical to offer Beta3 here for testing and to be much further on Github. Some report bugs from Beta 3 that are already fixed on Github.
That's no way to get testers, no way to get ahead. On Github is working on Beta4, so why not officially release it?
Presumably because they're not yet happy that it's ready to be called Beta 4. It's easy to test if you want to test it. Just download the latest build from GitHub and install it wherever you like.
I strongly suspect that beta 4 is simply a holding name and that the next release will be RC1 once all the remaining bugs that are important enough to not wait are fixed...
That makes sense. ;) In which case they'd definitely want to be sure it's ready to be called an RC.
(Says he, with dire memories of the 2.0 RC cycle)
Dire memories indeed.
Also calmer releasing an official version on the website is not a simple as pushing a button.
I think smf should be a paid software and seo should come smf ink structure change must be sitemap
Quote from: Replikacep on October 30, 2018, 01:16:28 AM
I think smf should be a paid software and seo should come smf ink structure change must be sitemap
The first thing is never going to happen, the second is also never going to happen, the third is unlikely but possible, I guess.
SMF will never be paid. period.
Simple Machines is already an incorporated corporation. We're not going to change our corporate structure (and even if we did, it would have no effect on SMF, the software....)
Sitemaps are available in several different formats as mods.
On that note, here's a little write-up that's existed since the dawn of SMF: Why free is better
https://www.simplemachines.org/about/whyfree.php
Besides if it went paid, I suspect the person suggesting it would then complain about how expensive it is and demand it be free again.
Quote from: Arantor on October 30, 2018, 04:28:33 PM
Besides if it went paid, I suspect the person suggesting it would then complain about how expensive it is and demand it be free again.
No they just use nulled version.
And then be denied support and complain about it.
Quote from: Replikacep on October 30, 2018, 01:16:28 AM
I think smf should be a paid software
If your willing to pay why not do the next best thing and become a charter member, you will be funding SMF and feel like you are buying a license ...
Quote from: Arantor on October 29, 2018, 03:47:17 PM
No, every time someone asks if it can be done quicker, we add another month to how long it's already going to take.
Just in the last week alone, the next release date has extended by over three months.
I believe this. This explains how we're half a decade into beta.
I'd be using it right now and fat and happy if the pretty URLs could be ported.
Triple posts deleted/merged - Iris.
Quote from: cpf on November 04, 2018, 11:50:39 PM
Quote from: Arantor on October 29, 2018, 03:47:17 PM
No, every time someone asks if it can be done quicker, we add another month to how long it's already going to take.
Just in the last week alone, the next release date has extended by over three months.
I believe this. This explains how we're half a decade into beta.
Sadly, it was a joke. The real reasons amount to three complete replacements of dev team in that time, no one having a concrete vision of what 2.1 should actually contain (and therefore no way to know when "done") and everyone just doing it in their spare time.
is there any new news or estimated time for stable version?
* another week added to the estimate.
Maybe a solution to the constant questions might be a stickied thread titled, "
When is 2.1 going to be released?"
with
- A brief explanation re why no dates set.
- An explanation of what RC1, RC2 and Final means; and
- A periodically updated copy of the github progress as per:
(https://i.postimg.cc/wvhbf0XF/Untitled-1.png)
(OK well not a solution but it might be easier just to point people to that thread rather than explain over and over... and over.. again)
1. We already explained that *a lot* of times.
2. https://en.m.wikipedia.org/wiki/Software_release_life_cycle
3. I wrote the last dev updates from Dev's Blog (with help of some members of the team, of course). Because apart from the developers not a lot of people among the team has development knowledge or perhaps, time to write a new article (my case, right know), it's kinda difficult to get one of those periodically. Furthermore, if you're wondering why devs doesn't write them, it's because we prefer them to focus on real development rather than writing new blog posts.
No one reads stickies. Once it gets enough comments, it just becomes a ball of people asking the questions answered by the first post because reading the first post is effort.
The mobile version of Wikipedia is kinda nice on a desktop PC, ironically enough.
Quote from: landyvlad on November 13, 2018, 04:57:48 AM
Maybe a solution to the constant questions might be a stickied thread titled, "When is 2.1 going to be released?"
with
- A brief explanation re why no dates set.
- An explanation of what RC1, RC2 and Final means; and
- A periodically updated copy of the github progress as per:
(https://i.postimg.cc/wvhbf0XF/Untitled-1.png)
(OK well not a solution but it might be easier just to point people to that thread rather than explain over and over... and over.. again)
and today that's showing no issues open for RC1... is it finally happening?
Quick add some issues to the RC1 list before users get their hopes up :D :D
There's a process and a good bit of work involved in putting together a release from the code on GitHub, so patience is still required. Progress is advancing, as you can see, but as always, the official release date is "when it's ready." ;)
And don't forget, every time someone asks, add another week ;D
Yeah, we have already a.. uhm.. 37 week delay? More or less?
if they keep asking, the actual release date will catch up to the original plan + delay. :)
I keep having doubts about how we will use the delay. Maybe have a team vacation ::)
Quote from: Gwenwyfar on November 14, 2018, 04:00:35 PM
I keep having doubts about how we will use the delay. Maybe have a team vacation ::)
Paid?
Is there payment in candy? I'd accept that.
Or we could do a Cuban move and pay everyone in rum.
Quote from: Gwenwyfar on November 14, 2018, 07:14:48 PM
Or we could do a Cuban move and pay everyone in rum.
If you reward all the devs post RC1 release with rum, then RC2 is gonna be funky !!!
I wanna be paid in oatmeal raisin cookies. :D
Really looking forward to a stable version. Sometimes there is a need to put up a new forum up and 2.1 sounds better than 2.0.
I must say, the only reason I'm no longer in team because they refused to pay me in catnip. So catnip brings you this kitty back just saying ::)
lol
Step by Step my teacher used to say because if everything is hurried, the faults sprout up in heaps. *eating cookie*
Quote from: Antes on November 15, 2018, 07:11:47 AM
I must say, the only reason I'm no longer in team...
Ohoh, dev-members dropping out again? That can well bring another year.
And because I said it, two !
Quote from: SMiFFER on November 18, 2018, 02:33:27 AM
Quote from: Antes on November 15, 2018, 07:11:47 AM
I must say, the only reason I'm no longer in team...
Ohoh, dev-members dropping out again? That can well bring another year.
And because I said it, two !
Don't nit pick the joke... that's not nice.
/me has rejoined in the past month...
Quote from: Antes on November 18, 2018, 07:21:04 AM
Quote from: SMiFFER on November 18, 2018, 02:33:27 AM
Quote from: Antes on November 15, 2018, 07:11:47 AM
I must say, the only reason I'm no longer in team...
Ohoh, dev-members dropping out again? That can well bring another year.
And because I said it, two !
Don't nit pick the joke... that's not nice.
What about nip-picking it? ;D
But in all seriousness, I appreciate the hard work you guys have done and continue to do. I'm really excited for the next release. PHP 7.2.x has forced me to use it in a live manner in at least one location, (yes, I know. You're not supposed to do that), but it has been unbelievably stable so far. The only issue I've run into was from the lack of updates to one of my favorite mods because the mod developer has been too busy working on SMF itself! :P
All in all, I know the community doesn't always show it much, but we do love you guys for what you do for us. Please keep it up!
When will the next release be? (multiplied by 52).
I think it's wrong people saying development is slow. It just looks that way as others are moving so much faster - all relative.
How about SMF 2.1 Beta 3.1
QuoteHow about SMF 2.1 Beta 3.1
That's actually not a proper naming scheme.
See semantic versioning § 9 https://semver.org/#spec-item-9
No beta 3.1 allowed
Beta 3 comes after beta 2.
It was kind of tongue in cheek.
I have now moved away from SMF but after looking around I found that other forums are also suffering or on the verge of closing down. As Arantor said, SMF is a mature package, and forums are not the most popular choice they once were. Some of the new company targeted forum/message apps are making money though.
After using my 'new' forum I do miss some functionality I had with SMF. That's often the case - some things are better, some worse.
I hope SMF picks up a bit as it served me well for 10 years.
Then again we have n the past had 2.0 RC 1-1 and 2.0 RC 1.2, both bad decisions that have haunted ever since.
shush! Those shall never be mentioned in the light of day again! :P
lol
Right as you decided to just delete with no explanation after I was abused I've decided to focus on different forum software, good look with 2.1.0 when it comes out in the next 10yrs
Quote from: movierchives on December 14, 2018, 12:33:55 PM
Right as you decided to just delete with no explanation after I was abused I've decided to focus on different forum software, good look with 2.1.0 when it comes out in the next 10yrs
ummmm.... I didn't do it.
However, the conversation/argument wasn't deleted, just split from this thread (since it was offtopic to the 2.1 beta release) and moved
Quote from: movierchives on December 14, 2018, 12:33:55 PM
Right as you decided to just delete with no explanation after I was abused I've decided to focus on different forum software, good look with 2.1.0 when it comes out in the next 10yrs
It was just moved by a team member
https://www.simplemachines.org/community/index.php?topic=563991.msg3999035#msg3999035
Quote from: OCJ on December 10, 2018, 05:17:43 PM
How about SMF 2.1 Beta 3.1
SMF 2.1 Beta 2 Episode 2 Part 2...
It's close. Of course this could change in a minute or two as well, lol. For now though the milestones look good:
https://github.com/SimpleMachines/SMF2.1/milestones
SMF 2.1 has not made it to RC level yet. I just wanted to throw this in there. Like I said above the status of 2.1 could change at any time and until 2.1 is marked as RC it is still beta.
Quote from: Bigguy on December 17, 2018, 08:00:12 PM
It's close. Of course this could change in a minute or two as well, lol. For now though the milestones look good:
https://github.com/SimpleMachines/SMF2.1/milestones
Yup, they look good. :) Nice to see that.
Coolio! Nice Christmas present maybe.
Quote from: landyvlad on December 21, 2018, 12:33:40 AM
Coolio! Nice Christmas present maybe.
/me points at signature.
Quote from: Sesquipedalian on December 21, 2018, 04:02:12 PM
Quote from: landyvlad on December 21, 2018, 12:33:40 AM
Coolio! Nice Christmas present maybe.
/me points at signature.
Conspiracy confirmed!
In all seriousness though, I noticed that the issues list for RC1 is completed. Is there a final to-do list publicized anywhere of what is left still before that version is released, or is that all in-house? Just asking simply out of curiosity.
Checking that the list of things to be done for that version is actually completed and there are as few bugs as possible. Changing the version in the files and maybe a few more checks here and there. I would guess. This is just what I think but who knows what the Devs will do before releasing.
Quote from: Bigguy on December 21, 2018, 10:10:02 PM
Checking that the list of things to be done for that version is actually completed and there are as few bugs as possible. Changing the version in the files and maybe a few more checks here and there. I would guess. This is just what I think but who knows what the Devs will do before releasing.
I figured that was probably the case too. The curiosity is getting to me, though!
When a version is (close to) being ready for release, there's several things we do in a release process.
Over the years the policy has changed to be a bit more rigorous as we had a couple of releases that had mistakes.
Admittedly, sometimes sloppy mistakes that could have been prevented by taking more time testing the packages - which we acknowledged and promised to do better.
In general when a release is imminent: all kinds of tests start happening. A few examples are checking if the packages build OK on the server, checking if language packs are generated (properly) and of course packages are created for internal use with what we think will become the release. This package is distributed to the team and a couple of member groups so that the installation, upgrade and patches (if applicable) can be tested for errors; both during install as issues that come up (shortly after) installing it. If errors occur that are actually caused by our code, they are fixed and an updated package is created to test it again. If there are no issues, we proceed. So when we're happy: fireworks start, hymns are sung, the servers shake in terror and beg the sysadmins to save them for what is about to come - and the release is actually made to the public. :) There's a lot more stuff/testing that is being done (by various teams, not just devs!), but this is one of the most fundamental examples about what's going on behind the scenes during a planned release of a new version. :)
This way we try to ensure, even for beta/RC releases, there are no (significant) issues with installing/upgrading.
So there's quite a lot happening in the background for each release and there's a good amount of testing taking place. :)
Nice to hear what is actually going on. Very cool and sounds like a lot of work.
/me tip toes away as not to disturb anyone working.....please no shouting here right now, people are concentrating, lol.
Quote from: CoreISP on December 22, 2018, 09:49:08 AM
When a version is (close to) being ready for release, there's several things we do in a release process.
Over the years the policy has changed to be a bit more rigorous as we had a couple of releases that had mistakes.
Admittedly, sometimes sloppy mistakes that could have been prevented by taking more time testing the packages - which we acknowledged and promised to do better.
In general when a release is imminent: all kinds of tests start happening. A few examples are checking if the packages build OK on the server, checking if language packs are generated (properly) and of course packages are created for internal use with what we think will become the release. This package is distributed to the team and a couple of member groups so that the installation, upgrade and patches (if applicable) can be tested for errors; both during install as issues that come up (shortly after) installing it. If errors occur that are actually caused by our code, they are fixed and an updated package is created to test it again. If there are no issues, we proceed. So when we're happy: fireworks start, hymns are sung, the servers shake in terror and beg the sysadmins to save them for what is about to come - and the release is actually made to the public. :) There's a lot more stuff/testing that is being done (by various teams, not just devs!), but this is one of the most fundamental examples about what's going on behind the scenes during a planned release of a new version. :)
This way we try to ensure, even for beta/RC releases, there are no (significant) issues with installing/upgrading.
So there's quite a lot happening in the background for each release and there's a good amount of testing taking place. :)
I appreciate the informative response. That was exactly what I was looking for! ;D
Just to be clear, folks, CoreISP's post merely describes in general the processes involved in creating a release. For anyone trying to read between the lines, the anticipated release date of RC1 in particular remains what it has always been: when it's ready. ;)
Quote from: Sesquipedalian on December 23, 2018, 02:28:16 AM
Just to be clear, folks, CoreISP's post merely describes in general the processes involved in creating a release. For anyone trying to read between the lines, the anticipated release date of RC1 in particular remains what it has always been: when it's ready. ;)
rc 1 seems to be ready at the beginning of the year
Thanks to everyone who works, a very solid infrastructure has emerged.
(https://i.hizliresim.com/7aXmdN.jpg)
That's not what that says. The part of that paragraph that says it'll be ready is this:
Quotethe anticipated release date of RC1 in particular remains what it has always been: when it's ready. ;)
Quote from: Sesquipedalian on December 23, 2018, 02:28:16 AM
Just to be clear, folks, CoreISP's post merely describes in general the processes involved in creating a release. For anyone trying to read between the lines, the anticipated release date of RC1 in particular remains what it has always been: when it's ready. ;)
Completely understandable. I was just curious on what was left in terms of the general work. Now that all of the issues for RC1 have been "resolved", there's nothing left in public view to see how things are progressing for that particular version. I guess you could consider it as my curiosity and impatience getting the best of me. :)
Since it was marked RC1 about 20 more bugs were found. It will not be out I would think until they are resolved.
Quote from: Bigguy on December 24, 2018, 03:29:33 PM
Since it was marked RC1 about 20 more bugs were found. It will not be out I would think until they are resolved.
Where are you getting that information from?
https://github.com/SimpleMachines/SMF2.1/milestone/6
Please avoid sharing that kind of information. A couple of days ago we released what could be the final RC1 build to the beta testers group. Most of the latest bugs on GitHub are related to that build sent to the testers.
Now it's up to the development team to merge now (or not) some of the solutions for those bugs. We don't want to merge them all, but it might be worth to merge some of them for release consistency. Those aren't a release stopper anyway.
Sorry about that. What he said.
What's to share, though? The code is on Github, one could easily take the point of "the version numbers were changed to RC1" as that point in time and note bugs having been created after that...
Sure, while that's true and available for anyone, Bigguy said that it won't be out until they're resolved, he thinks. That can just be misleading for other users and not entirely true.
Quote from: Bigguy on December 24, 2018, 07:32:55 PM
Sorry about that. What he said.
No problem :)
Mind you it also exposes some interesting decisions, like the choice to rewrite how board access works this close to an RC, it was stable and mature and now needs to be totally retested.
It's normal to have different opinions and proposals while developing open source software. Developers are open to discuss that kind of things, and it's their choice to do one thing or another.
Sure, but doing it this late into the project seems like a bad idea especially as it has caused at least one major bug that should not go out in an official release.
Sesquipedalian wants to change the pace of the releases once we release RC1 so, we can't really tell what is he going to do. It's up to him. We can't keep doing the same things that haven't been working for years.
Agreed, but again: changing a major system (especially a security related one!) just before a release is a bad idea, especially when it's clear not enough testing was done.
If only there were a way to write tests for things so that you could check it didn't break when doing refactoring.
Note: I'm not criticising what was done. I'm criticising the fact it was done this close to RC. The whole point of an RC is to have "what we think is a stable product" not "something that is really another beta under a different name". Ironically, see 2.0 RC1 for exactly the same thing.
Which change was that?
I'm sure Sesquipedalian knows what's best to do. Anyway, if you have further thoughts I gently invite you to post them on GitHub so they can be reviewed properly. We appreciate that ;)
The rewrite to board access, cause of https://github.com/SimpleMachines/SMF2.1/issues/5265 and related issues. You know, that thing that SMF has had forever albeit in an ugly form, but was *stable*.
Did it need a rewrite? Sure. Doing it in the weeks before the first release that "isn't beta"? Not a good idea.
Would I post them on GitHub? No, because the damage has already been done by not saying no to such contributions *at this time*. I don't have time to review every commit and warn about ones that are a bad idea because need more testing, because just before an RC is the wrong time to be doing it.
The fact I even have to explain this notion indicates to me that there is no point trying to fix anything.
I must have missed that, I don't know which PR is it. I'll forward it to our RC1 discussions though so the devs don't miss it :)
Seems the bulk of it was done in 4727, further back than I thought, but still... something like that needed some serious testing and planning.
Well i'm suprised that you notice on the one hand that this was a deep change,
on the other hand you got problem because >one< issue raised up out of this.
And this one issue got fixed months ago,
so everything is fine with this change.
Other than the bug that's open on GitHub right now, you mean?
Quote from: Arantor on December 25, 2018, 10:09:22 AM
Other than the bug that's open on GitHub right now, you mean?
It appears that they closed it not long after you brought it up. Hopefully it is resolved now, although I have no idea. I didn't look heavily into it, but I updated my forum to the latest repo files a few days ago and didn't encounter this issue myself.
As for the discussion at hand, the files were originally being referenced as Beta 4. If changing a major system is necessary and it affects versioning that bad, I don't understand why they wouldn't just rename RC1 to Beta 4 again, change RC2 and Final to RC1 and RC2 respectively, and add another Final. That seems like it would fix it. (It seems odd to me anyway that Final would be a version which contains open bugs that need fixing). That's just me, though. I'm sure there is a reason for everything being done, and I'm definitely not trying to criticize it. I appreciate all the hard work you guys are doing greatly.
On a side note, no one has been asking when it will be released lately. Guess that means no more extra delays? ;D
Note that the changes in question were only merged in today to fix the issue I pointed out, but this kind of thing sits badly with me - if you're going to revamp a key system, one that is inherently security related, it needs as much testing as you can throw at it, and the issue raised makes it seem like the major change had little or no testing, which is bad for everyone.
Also, 2.0 had a lot of known bugs in it when it was released and plenty of which have never been fixed since.
Mind you, I'm a bit salty because I was always taught that an RC is 'something you believe to be final' and I'd love to avoid having 5 RCs again.
Quote from: Arantor on December 25, 2018, 07:32:06 PM
Note that the changes in question were only merged in today to fix the issue I pointed out, but this kind of thing sits badly with me - if you're going to revamp a key system, one that is inherently security related, it needs as much testing as you can throw at it, and the issue raised makes it seem like the major change had little or no testing, which is bad for everyone.
Yikes. Hopefully that is the last we see of that bug then, (or any related ones).
Quote from: Arantor on December 25, 2018, 07:32:06 PM
Also, 2.0 had a lot of known bugs in it when it was released and plenty of which have never been fixed since.
I believe that lol. I've come across some weird stuff over the years with 2.0, such as having too many membergroups attached to a board permission causing it to break the database and not want to properly save things.
Quote from: Arantor on December 25, 2018, 07:32:06 PM
Mind you, I'm a bit salty because I was always taught that an RC is 'something you believe to be final' and I'd love to avoid having 5 RCs again.
Makes sense. RC does stand for Release Candidate I believe, so I can see where you are coming from.
QuoteMind you, I'm a bit salty because I was always taught that an RC is 'something you believe to be final' and I'd love to avoid having 5 RCs again.
It is more like a "RC means no more large changes and few or no major bugs" as I understand it. Maybe the name is wrong for that end, but a line has to be drawn somewhere and that line is RC. I may not agree with all the details of the process, but it makes sense.
QuoteAlso, 2.0 had a lot of known bugs in it when it was released and plenty of which have never been fixed since.
Now, this is something I'm more bothered about... I'd expect a software's patches to
fix things, and it still completely stumps me that we won't even fix some small bugs or even do small language edits. For whatever was supposed to be the "reason". Hopefully something that will change.
I've seen up to 15 RCs on some products. Not that I'm pro that, it's just that it has been seen before... though on PC software.
So have I, just the very term "release candidate" implies "could be a viable release" to me...
Still, we found some things, some of them were already in progress, some of them are being tackled. You all know I'm sour, bitter, jaded etc, but I'm really impressed with what has happened only since last night. So much positive energy right now, so I'll try to be more positive too.
Maybe it would match that if it were alpha/beta/RC?
:)
Quote from: Arantor on December 26, 2018, 04:39:50 AM
You all know I'm sour, bitter, jaded etc, but I'm really impressed with what has happened only since last night. So much positive energy right now, so I'll try to be more positive too.
That's the spirit! ;D
One thing about SMF that stands out on support forums - they talk a lot more about doing something than actually doing it. Wonder how many MB of Dev chit chat there are about 2.1 releases - if only it was code. Makes you wonder how much chit chat each line of software code represents.
Chit chat takes far less effort to write than code. I can make hundreds of posts a day, but hundreds of lines of code? Less likely.
I will note that most of the developers don't contribute to the "talk about it" because they are out there doing it... so, your comment is just incorrect in its entirety
I also think people don't understand what's actually involved with programming, they think it's as easy as just typing. Fun fact, I spent 8 hours at work programming, I fixed two bugs and changed something at a client's request, these things totalled 28 lines of code. Just over 4 lines of code per hour and yet I'm consistently considered one of the most productive people.
It really isn't easy to actually do this programming thing. I suggest those complaining about it give it a go sometime.
Exactly, it depends sometimes on a lot of factors, time, thinking of the issue, for me personally I am always pushed in many directions or people needing me to do something.
Quote from: OCJ on December 28, 2018, 01:12:19 PM
One thing about SMF that stands out on support forums - they talk a lot more about doing something than actually doing it. Wonder how many MB of Dev chit chat there are about 2.1 releases - if only it was code. Makes you wonder how much chit chat each line of software code represents.
Posts by Sesquipedalian on simplemachines.org:
447
Contributions by Sesquipedalian to SMF 2.1:
738 commits
35,683 lines of code changes:
20,735 additions
14,948 deletions
Please feel free to reconsider your claim, OCJ. ;)
I assumed it was a dig at me, so...
It was probably toward anyone and everyone associated with SMF because he's impatient waiting for that next release of pure awesomeness.
Quote from: Arantor on December 29, 2018, 05:26:52 AM
I assumed it was a dig at me, so...
Maybe that's what everyone thought. I thought of replying too but... There's better things to do. Like resting and having fun so you'll be able to write code better without stressing youself, or discussing doing things for when you have the time to do it ;D
Quote from: Arantor on December 29, 2018, 05:26:52 AM
I assumed it was a dig at me, so...
If so, that'd be even sillier. You've posted so often here over the years because you've spent so much time helping people. To complain about that would seem... rather odd.
Quote from: SugarD-x on December 29, 2018, 05:33:22 AM
It was probably toward anyone and everyone associated with SMF because he's impatient waiting for that next release of pure awesomeness.
That sounds about right to me. Also, :D
Yep.
And I just noticed my comment was rather ambiguous. If it's for everyone, then each one of us is personally included, though some do post here more often, so...
To miss the fact some hardly even post here at all is also silly.
Quote from: Arantor on December 28, 2018, 07:47:02 PMI also think people don't understand what's actually involved with programming, they think it's as easy as just typing.
Time is relative online so many feel your time is theirs and what you dedicate your time to is the same as things they would. Coding things for 'free' usually is a work of love- people do not know the cost or time involved in these ventures. In other words, you are not human- you are not entitled to life, free time or pursuing your own needs and wants. You are just there for them, and them only. That is the modern interpretation of a username- the person that posts updates that meets your needs when you want it.
With all that said... let's hope that 2019 sees some good surprises for SMF 2.1 with a stable public release. ;)
For people that want to learn some coding try here: https://www.codecademy.com/
It is a very difficult job coding..
Quote from: Sesquipedalian on December 29, 2018, 05:25:45 AM
Quote from: OCJ on December 28, 2018, 01:12:19 PM
One thing about SMF that stands out on support forums - they talk a lot more about doing something than actually doing it. Wonder how many MB of Dev chit chat there are about 2.1 releases - if only it was code. Makes you wonder how much chit chat each line of software code represents.
Posts by Sesquipedalian on simplemachines.org:
447
Contributions by Sesquipedalian to SMF 2.1:
738 commits
35,683 lines of code changes:
20,735 additions
14,948 deletions
Please feel free to reconsider your claim, OCJ. ;)
ROFLMAO OCJ = pwned.
I think OCJ was the one being rude, making such comments on the development team, apparently based on false assumptions made on the forum alone.
For anyone who has spent a little time here, it should be fairly apparent that actual development work is not really visible here, and one can't make assumptions like that on what they see here. Even github can't really show how much time and effort has gone in to each commit...
Hi,
I'm looking to resolve the mobile friendliness of my site. I'm running 2.0.15 with the responsive curve mod. Will this version do away with the need of a mod, and be responsive anyway? So is it worth me sitting back and waiting for the upgrade?
And how about other mods, will they be compatible with this version? And if not, are they automatically discarded on upgrade?
Thanks in advance
Pete
Yes 2.1 is responsive, some mods will work with few or no changes, but all mods should be uninstalled on upgrade.
The package manager will frequently try to let you install things that aren't marked for 2.1 on the off chance they might work.
8 months and not release as yet?!
14 months since ANY update!!!
....... SMF is starting to look VERY dated these days and an 'elephant-in-the-room' of missing features.... :'(
I don't know code, I don't know the difficulties... I'm just a consumer of SMF ...... for over 12 years! :-[ :'( :'(
14 months since an update.....Me thinks you have not been to GH lately.
https://github.com/SimpleMachines/SMF2.1/milestones
Two and a half lines of chitchat produced a whole page of replies. Some people here are very highly strung - wasn't at all like some people made it out to be. Of course I appreciate the difference between writing chitchat and code, and the hard work people put in - just doesn't seem so productive as a group here (but that's another story better left burried). Anyway, it was meant to be posted in another board, 'Old News and No Updates'.
Quote from: ModelBoatMayhem on January 10, 2019, 07:17:40 PM
8 months and not release as yet?!
14 months since ANY update!!!
Yes, it's been long - but personally I'm pretty happy with my 2.0 still, I'm in no rush to get to an unfinished 2.1.
Quote from: ModelBoatMayhem on January 10, 2019, 07:17:40 PM
....... SMF is starting to look VERY dated these days and an 'elephant-in-the-room' of missing features.... :'(
I don't know code, I don't know the difficulties... I'm just a consumer of SMF ...... for over 12 years! :-[ :'( :'(
Yeah, I've been with SMF since 2005, so 14 years or so, and have never heard my users complain of those "missing features" that are available on other platforms - Actually, looking at the feature list of phpBB for example, I can't say what those are...
Quote from: OCJ on January 10, 2019, 09:27:07 PM
Of course I appreciate the difference between writing chitchat and code, and the hard work people put in - just doesn't seem so productive as a group here (but that's another story better left burried). Anyway, it was meant to be posted in another board, 'Old News and No Updates'.
Well, for one, yet again, you're just plain wrong in pretty much everything you said...
SMF is quite productive. If you think otherwise, then you're not actually paying attention.
... and your statement did not indicate any appreciation of the difference, since you directly related the two and indicated that you believed the chit chat was indicative of lack of coding progress.
As for "old news and no updates" - once again, you don't seem to be paying attention, since - while it may not be the updates that you WANT - there have been frequent updates both in code and notes.
So other words, a blowhard complaining that the free time of volunteers is not being spent fast enough so he doesn't have to.
Quote from: Aleksi "Lex" Kilpinen on January 11, 2019, 04:04:06 PM
You might just be on to something there, perhaps this topic should be split already.
Oh, and I appreciate the effort, I do - but that sounded strange, tervetuloa is a greeting like welcome in english, but what you probably meant would translate to "Ole hyvä" -> Be good. :P
Nope just saying welcome in Finnish "Peculiar Finn" I chat with Bryan (runic) to much..besides my second family are all Finnish
Quote from: Oldcrow on January 11, 2019, 04:07:23 PM
Quote from: Aleksi "Lex" Kilpinen on January 11, 2019, 04:04:06 PM
You might just be on to something there, perhaps this topic should be split already.
Oh, and I appreciate the effort, I do - but that sounded strange, tervetuloa is a greeting like welcome in english, but what you probably meant would translate to "Ole hyvä" -> Be good. :P
Nope just saying welcome in Finnish "Peculiar Finn" I chat with Bryan (runic) to much..besides my second family are all Finnish
Cool, well - I've been around a couple of years longer than you, so didn't immediately think you were welcoming me :P
Anyhow, remind Bryan to explain you how some words in finnish have a dozen of different usages :P And the other way around.
Quote from: Aleksi "Lex" Kilpinen on January 11, 2019, 04:12:30 PM
Quote from: Oldcrow on January 11, 2019, 04:07:23 PM
Quote from: Aleksi "Lex" Kilpinen on January 11, 2019, 04:04:06 PM
You might just be on to something there, perhaps this topic should be split already.
Oh, and I appreciate the effort, I do - but that sounded strange, tervetuloa is a greeting like welcome in english, but what you probably meant would translate to "Ole hyvä" -> Be good. :P
Nope just saying welcome in Finnish "Peculiar Finn" I chat with Bryan (runic) to much..besides my second family are all Finnish
Cool, well - I've been around a couple of years longer than you, so didn't immediately think you were welcoming me :P
Anyhow, remind Bryan to explain you how some words in finnish have a dozen of different usages :P And the other way around.
Amazing.. none of my family speaks the language, but they do belong to 2 Finnish organizations in Michigan
I actually have family in the states I understand, no idea where - don't know them.
But, I already split this topic once - let's continue on topic :)
https://github.com/SimpleMachines/SMF2.1/milestones
In case anyone is questioning the progress.
As for the actual topic at hand, I'm very excited for RC1. I've been manually updating to the "Beta 4" files in the mean time, so it will be nice to get my forum back onto a proper release schedule. I'm just hoping there aren't any conflicts between the GitHub files and RC1 since the live GitHub stuff may contain things in newer releases, (such as RC2 and Final).
SMF does look outdated and of course board admins want to give their users the best experience possible for the price (free :-P).
I do wish SMF picks up and becomes more popular but long long update cycles will put off people. I know it's all volunteer, but that is the way people are.
QuoteAleksi...
Yeah, I've been with SMF since 2005, so 14 years or so, and have never heard my users complain of those "missing features" that are available on other platforms - Actually, looking at the feature list of phpBB for example, I can't say what those are...
Users might compare to social networks but not the users I think that are worried about features - more likely admins running the boards.
I used SMf for about 8 years but was testing it in 2006 for a club. It fit my specific requirements better than others. It was more active then as well with talk of 3.0.
The features in 2.1 that are mods being incorporated are not such a big thing as they were mods for a long time. I know a lot of code has been updated but as an Admin it is not much of a change.
There are features in SMF that I miss but my requirements are not as strict so I can use another forum. phpBB is easier using mods/extensions ( pretty much plugin and play with no code modification problems) and the themes are better for mobile devices (whatever Kindred says otherwise about themes here).
Hopefully SMF 2.1 will fix that - it just took too long.
Quote from: OCJ on January 12, 2019, 07:50:05 PM
I do wish SMF picks up and becomes more popular but long long update cycles will put off people. I know it's all volunteer, but that is the way people are.
Correct, that's the way people are... nowadays. That is not how people used to be.
Advancements in technology have basically spoiled people and made them lazy. "Damn it, this looks terrible on my phone... I have to zoom in and out and... ah, f*ck this.". The fact is that the site (forum) doesn't look terrible at all... the fact that they have to use both fingers to browse through the damn thing and try to browse it on a 10cm screen is what annoys them. Really ???. Have we gotten to the point when using our fingers is annoying ???. It's that bad, huh ::). Also, have you ever read the paper on a 10 x 7 cm screen ???. That's why paper sheets have the size that they have... so people can LOOK and READ them, not squirt at them.
See... the problem is... people expect to use nothing more than their thumb to mindlessly browse through content. That is what the social networks turned users into - mindless zombies who browse through stuff when they have nothing better to do (in some cases, even when they do have something to do)... and they expect to only use their thumb to view every single piece of content they find on the web. Well... excuse me for not being lazy and using all of my fingers ::). I thought that was the way we were designed... to use our extremities ::).
In conclusion, people just want more and more and more and more... it doesn't matter how much you try, most of them are never grateful and are always unsatisfied. Thus, it doesn't really matter what you bring at the table, as long as it doesn't look like FB, Twitter, Snapchat, it won't really matter.
That's why I've stopped competing... it's pointless (I'd even go as far to say mindless). People will always complain about something. I've made this clear to the users of my forum. "Don't ask for miracles. The forum looks like this, this is how it's going to stay for the time being. Small changes and modifications can be made, but don't ask me to rewrite the core. If you don't like it, there are other places on the web which you can call your home.".
Quote from: Aleksi "Lex" Kilpinen on January 11, 2019, 04:12:30 PM
Quote from: Oldcrow on January 11, 2019, 04:07:23 PM
Quote from: Aleksi "Lex" Kilpinen on January 11, 2019, 04:04:06 PM
You might just be on to something there, perhaps this topic should be split already.
Oh, and I appreciate the effort, I do - but that sounded strange, tervetuloa is a greeting like welcome in english, but what you probably meant would translate to "Ole hyvä" -> Be good. :P
Nope just saying welcome in Finnish "Peculiar Finn" I chat with Bryan (runic) to much..besides my second family are all Finnish
Cool, well - I've been around a couple of years longer than you, so didn't immediately think you were welcoming me :P
Anyhow, remind Bryan to explain you how some words in finnish have a dozen of different usages :P And the other way around.
Wait how come I came into this convo??
I'm not sure :P
hmm suspicious secret convos about me ....
Quote from: OCJ on January 12, 2019, 07:50:05 PM
...phpBB is easier using mods/extensions ( pretty much plugin and play with no code modification problems)...
Excuse me, but what?!? I use PHPBB and SMF both. Plugins and mods are a NIGHTMARE on PHPBB. Their entire extension system is a disaster waiting to happen. Any time it breaks, so does your entire forum and half your database. PHPBB was my first, but SMF got the package system right. If anything, PHPBB should make their own more like SMF's.
Quote from: BryanD on January 13, 2019, 03:35:04 AM
Quote from: Aleksi "Lex" Kilpinen on January 11, 2019, 04:12:30 PM
Quote from: Oldcrow on January 11, 2019, 04:07:23 PM
Quote from: Aleksi "Lex" Kilpinen on January 11, 2019, 04:04:06 PM
You might just be on to something there, perhaps this topic should be split already.
Oh, and I appreciate the effort, I do - but that sounded strange, tervetuloa is a greeting like welcome in english, but what you probably meant would translate to "Ole hyvä" -> Be good. :P
Nope just saying welcome in Finnish "Peculiar Finn" I chat with Bryan (runic) to much..besides my second family are all Finnish
Cool, well - I've been around a couple of years longer than you, so didn't immediately think you were welcoming me :P
Anyhow, remind Bryan to explain you how some words in finnish have a dozen of different usages :P And the other way around.
Wait how come I came into this convo??
I mentioned you..
QuoteExcuse me, but what?!? I use PHPBB and SMF both. Plugins and mods are a NIGHTMARE on PHPBB. Their entire extension system is a disaster waiting to happen. Any time it breaks, so does your entire forum and half your database. PHPBB was my first, but SMF got the package system right. If anything, PHPBB should make their own more like SMF's.
That might be your experience, but not mine.
1. In phpBB you upload the extension package to a folder 'ext', then enable it - done. Removing mods is just the same - disable and delete - no code modifications for admin to do.
There is no messing about with manual edits and package manager warnings - everything usually works 'out of the box'. The only problems I encountered was in sql with conflicts between mods.
2. Themes are better as well on mobile devices.
3. I don't need a portal as there are official extensions that provide what a portal would do.
That said, I prefer the admin panel in SMF. Also moderation is a bit of a pain in phpBB as you have to go through all posts without the ability to filter first.
No Subscription core function in phpBB - that was useful to me in SMF.
The calendar in SMF is a waste of time as functionally it is different when posting from the calendar and the board - permissions are not checked the same. Nothing but trouble (reported this).
I also (re-)reported a bug about guests not being able to reply to their own post - think that has still not been fixed!!!???
Seems it was just kept quiet here but it was fixed in a fork of SMF. That was left that way for years - shocking.
Probably more mods available for SMF - maybe that is simply because development of new versions is slow and old mods still work.
1 was done in an SMF fork but later partially undone because "it's not flexible enough" and it was never adopted for SMF because of fears of how it would not let mod authors be able to do what they can do today.
2 is fixed in 2.1
3... so you don't need a portal because you have a portal.
Quote from: OCJ on January 17, 2019, 09:01:09 AM
1. In phpBB you upload the extension package to a folder 'ext', then enable it - done. Removing mods is just the same - disable and delete - no code modifications for admin to do.
You do the exact, same thing in SMF, except it warns you of conflicts before you install it. Many mods in PHPBB still require code editing...
The issue with mods/extensions in new versions of phpBB is many developers of those addons have moved on same for SMF. But second the extensions for phpBB seems to require a higher level of coding knowledge. SMF does have hook based mods as well that require no edits. And the mod site does seem to enforce that for new mods when it is possible. 2.1 adds a ton more hooks to use.
I have worked with both soft wares and still do some phpBB. I prefer the SMF license since it is more open and perfer coding for it due to it's setup. The major issue with SMF has been its slow release cycle but it happens do to people coming and going.
Quote
I also (re-)reported a bug about guests not being able to reply to their own post - think that has still not been fixed!!!???
Seems it was just kept quiet here but it was fixed in a fork of SMF. That was left that way for years - shocking.
That has prompted me to dig through your old posts and I found [2.0.11] Guest shown reply button but on click denied (login required) (https://www.simplemachines.org/community/index.php?topic=544167.0) - seems to be what you're talking about and has been addressed in SMF 2.1 https://github.com/SimpleMachines/SMF2.1/pull/2043/files
Nice to know it got done.
QuoteThat has prompted me to dig through your old posts and I found [2.0.11] Guest shown reply button but on click denied (login required) - seems to be what you're talking about and has been addressed in SMF 2.1
I would also consider looking at how the calendar post checks permissions - not shown the same from calendar posting or board posting. In our case posting from calendar does not show the allowed permission to announce topic to forum members. The other way, posting from the board does not show the calendar post settings. Extremely annoying as users do just one and do not edit again to do the other (only way options show). Arantor did suggest it could be done with javascript when a board was selected from the calendar.
With all the trouble I had with the calendar it wasn't worth it as an events calendar. I would agree with a lot of people here who wanted to untangle it from-the software and take it out.
That stuff has all been reviewed and overhauled in 2.1.
QuoteThat stuff has all been reviewed and overhauled in 2.1.
Well, in that case I might be migrating back after it is released. If there is an updated convertor. :)
So kind of you.
Quote from: Colin on May 31, 2017, 09:21:59 PM
Dear Users,
Simple Machines is proud to announce the release of the 3rd Beta of SMF 2.1. This version contains many improvements over Beta 2 and also fixes many bugs that were discovered following its release.
Among the notable improvements:
- Added reCAPTCHA as core feature to keep spammers away.
- Upgrade.php code clean-up. Now the upgrade process should be more consistent.
- RSS general improvements.
- Added support for jQuery 3.x.
- Modified Curve2 to improve the responsiveness of the design.
- General bug fixes, code improvements, and clean-up.
- Default codification will now be UTF-8.
For full details of what has changed, please see
The general installation/upgrade procedure of this Beta release remains the same, however, once you upgrade from an older version to 2.1 you cannot go back, so please take careful consideration before upgrading any live site. Have a look at Installing and Upgrading SMF (https://wiki.simplemachines.org/smf/Category:Installing_and_Upgrading) in the Online Manual to find out more. You cannot upgrade to 2.1 Beta 3 via the package manager; instead you will need to carry out the Large Upgrade process. SMF 2.1 can be obtained from the download section (https://download.simplemachines.org/).
Please note that because this is a beta release, translations and language strings other than English have not been finalized and may not yet be complete.
Finally, as always, this topic is not for support. Discussion and support for 2.1 can be found in the
Finally, thanks to all of the team and development contributors[/url] who have brought us one step closer to a release candidate. On behalf of the project, we appreciate the time, energy and contributions you have made.
Thank you for using SMF
Kind regards,
Simple Machines Forum Team
Ok, So I'm really confused. Did someone not update the forum Clock since 2017? The Description at the top layer say's this is a 2019 post but the followups show a 2017 date?? Sup?
This topic started in 2017 and over the previous 15pages has kept rumbling.
(https://i.postimg.cc/5ykFL0ky/Screenshot-2019-01-25-Simple-Machines-SMF2-1.png)
(https://media.giphy.com/media/llkGrCNLlQxmZtki70/source.gif)
That doesn't mean it's ready, it means the issues deemed so far for RC1 are done. It'll be out when it's out.
Quote from: _max_ on January 25, 2019, 10:04:41 AM
(https://i.postimg.cc/5ykFL0ky/Screenshot-2019-01-25-Simple-Machines-SMF2-1.png)
(https://media.giphy.com/media/llkGrCNLlQxmZtki70/source.gif)
/me points at signature.
Still, it's better than 50% :)
The SMF team is taking the 3D Realms approach to development...
You mean to spend adequate time testing to avoid putting out buggy releases?
If that is what you want to call it, sure.
I just hope that by the time it's released, it's not already outdated and surpassed by the latest and greatest... ala Duke Nukem Forever.
That is what's going on, and there's been a few nasty bugs found in the build that would be horrible if released in an RC.
Quote from: FrizzleFried on January 29, 2019, 11:19:30 AM
The SMF team is taking the 3D Realms approach to development...
LOL
At least we don't have to worry about game loops and memory pointers. :D
Quote from: live627 on January 29, 2019, 05:46:31 PM
Quote from: FrizzleFried on January 29, 2019, 11:19:30 AM
The SMF team is taking the 3D Realms approach to development...
LOL
At least we don't have to worry about game loops and memory pointers. :D
Dang it, I knew I'd left a few of those & in there ;D
Quote from: Arantor on January 29, 2019, 11:28:42 AM
You mean to spend adequate time testing to avoid putting out buggy releases?
I wish those clowns behind Wolfenstein: The New Colossus had done that...
But I digress. :)
As much as I like videogame references (;)) and stable software one must admit that it's worrisome to consider how many years have passed since 2.0 final was released. (Although I do remember it like it was yesterday.)
Why is is worrisome?
We have a VOLUNTEER staff.
"Real Life"TM ALWAYS comes first.
You can track the general progress on GitHub... and note that things HAVE BEEN progressing.
So, Instead of complaining how long it takes (which is actually counterproductive as it disheartens the people who are volunteering their own personal time to make and support SMF), you have a few choices:
- go to a paid software with a full-time, paid staff. They are likely to have more frequent releases.
- suggest that we release out software with major known issues (NOT GOING TO EVER HAPPEN)
- participate in the process. Download the daily build, install it, use the upgrader, find and report issues on GitHub.
- participate in the process. Look at the GitHub list. Develop code to address items on that list. Submit the code to GitHub.
oh no kindred is here D:
oh no a dev is here
Quote from: DynaFox on February 01, 2019, 12:39:47 AM
oh no kindred is here D:
So am I. And I'm infinitely worse.
Can we form the big evil league now? What else do we need?
I'm an evil dick by profession. Can I join in?
No! Too much niceness to qualify.
Plus, we need something to show for our evilness.
>:D
Quote from: Arantor on December 11, 2018, 07:52:50 AM
Then again we have n the past had 2.0 RC 1-1 and 2.0 RC 1.2, both bad decisions that have haunted ever since.
I'm sure there was also a 1.0 beta 3.142 or something daft in the past too.
All that said though I think unfortunately the wait has been too long for me and I'm about the pull the trigger on Xenforo.
Their 2.1 release is quite something I have to admit.
Agreed. If SMF could incorporate that push notification system ...
there's a mod for that
The mod uses a third party service (OneSignal), XenForo does not.
Quote from: Gwenwyfar on February 01, 2019, 05:48:57 AM
Plus, we need something to show for our evilness.
Pyrotechnics!
SMF 2.1 has push notifications. Apparently unlike XenForo's, ours even work in Safari on macOS. (They don't on iOS, though, because Apple requires a completely different API for iOS push notifications.)
did someone said Evil ?
Quote from: Gwenwyfar on February 01, 2019, 05:48:57 AM
Plus, we need something to show for our evilness.
Me me me ... pick me
Quote from: Arantor on February 01, 2019, 06:12:57 AM
>:D
and for some weird reasons... I imagined you doing that face :|
Quote from: Sesquipedalian on February 02, 2019, 12:44:57 AM
SMF 2.1 has push notifications. Apparently unlike XenForo's, ours even work in Safari on macOS. (They don't on iOS, though, because Apple requires a completely different API for iOS push notifications.)
Unless you rewrote it when I wasn't looking, SMF has poll notifications... since I don't obviously see webworkers or anything that would work when you're not on the site with it open in a tab. If you did, great, but I don't see the tooling that would make that work.
Quote from: Antes on February 02, 2019, 03:57:27 AM
did someone said Evil ?
Quote from: Gwenwyfar on February 01, 2019, 05:48:57 AM
Plus, we need something to show for our evilness.
Me me me ... pick me
Do you have any pyrotechnics spells? Count yourself in if so :D
... If not, still in anyway, because we need a c... *ahem*, an evil cat to make the team complete. We can hire someone else for the pyrotechnics >:D
Quote from: Arantor on February 02, 2019, 04:21:39 AM
Quote from: Sesquipedalian on February 02, 2019, 12:44:57 AM
SMF 2.1 has push notifications. Apparently unlike XenForo's, ours even work in Safari on macOS. (They don't on iOS, though, because Apple requires a completely different API for iOS push notifications.)
Unless you rewrote it when I wasn't looking, SMF has poll notifications... since I don't obviously see webworkers or anything that would work when you're not on the site with it open in a tab. If you did, great, but I don't see the tooling that would make that work.
That's a name I didn't hear before. What's the idea behind it being called "poll"?
Because that's what it's doing: polling the server for updates via AJAX.
I see. Might make more sense if you know exactly what that does, because poll still sounds like an odd word choice for a request of info :P
Is it though? When you do the voting thing, you're asking for information. When you have a forum poll, you're explicitly asking other people for information.
Either way, it's not *pushed from the server* unlike XF's.
Is it better pushing than polling?
Sure, for two reasons. 1, you don't have to leave the forum open in a tab to get notifications and 2, you don't have regular hits to the forum just to see if there are new notifications.
1. Wouldn't make sense to just receive notifications when you are in the forum? I do receive push notifications from websites when I'm doing other things and I just disregard them.
2. Is the gap huge in terms of efficiency?
1. Um, no. If I care enough to get notifications, it's because I'm not on the forum and it's about pulling me back to the forum when I don't already have it open. That's what a surprising number of users care about. Consider especially this for Android users whose alternative is a native app to get notifications.
2. Hmm... how about the server doing 1 AJAX call vs every user who happens to have the forum open in their browser querying the server every 30 seconds?
Quote from: Arantor on February 02, 2019, 07:42:33 AM
Is it though? When you do the voting thing, you're asking for information. When you have a forum poll, you're explicitly asking other people for information.
Either way, it's not *pushed from the server* unlike XF's.
But by that logic, any question you make to anyone is a "poll". I'd draw the line on whether the questions are used to amass info (more than one person asked, and both linked together), instead of one single question that doesn't add up to anything.
Then again, maybe the english word is used in a less specific manner.
Quote1. Um, no. If I care enough to get notifications, it's because I'm not on the forum and it's about pulling me back to the forum when I don't already have it open. That's what a surprising number of users care about. Consider especially this for Android users whose alternative is a native app to get notifications.
Makes sense for a lot of people, but I'd also rather use it when the tab is open. I might be doing something else and don't want to be bothered. Though honestly I haven't used it anywhere to know how easy it is to change the browser settings to disable it.
Desktop users really aren't the ones who benefit from this, this is for using mobile without you having to have a dedicated app.
Like having the benefits of Tapatalk without having it installed.
Guess not. And email notifications still do the job just fine for desktop.
Quote from: Kindred on January 31, 2019, 11:38:27 AM
Why is is worrisome?
We have a VOLUNTEER staff.
"Real Life"TM ALWAYS comes first.
You can track the general progress on GitHub... and note that things HAVE BEEN progressing.
So, Instead of complaining how long it takes (which is actually counterproductive as it disheartens the people who are volunteering their own personal time to make and support SMF), you have a few choices:
- go to a paid software with a full-time, paid staff. They are likely to have more frequent releases.
- suggest that we release out software with major known issues (NOT GOING TO EVER HAPPEN)
- participate in the process. Download the daily build, install it, use the upgrader, find and report issues on GitHub.
- participate in the process. Look at the GitHub list. Develop code to address items on that list. Submit the code to GitHub.
You misunderstood. I'm not complaining. I've always had the feeling you automatically assume the worst in people. I don't know why that is. Cheer up. :)
It's worrisome because it is indicative of a lack of volunteers. A decade ago SMF (and by extension this community) was thriving. Now, well, it's still relatively strong, but it's a far cry from those days. Don't get me wrong, I dislike those who proclaim the inevitable death of SMF as much as you do, and I realize that people move on, I have, but the slow influx of new people is a bit disconcerting. I know it is not the best indicator, but just take a look at the statistics of this forum. It is very much alive, and will almost certainly be for the forseeable future, but it is in a constant decline. Food for thought. That is all.
I stand corrected. :)