Allow using Content-Security-Policy without unsafe-inline • Content-Security-Policystevemaury wrote: ↑Sun May 20, 2018 8:16 pm I went to your board and looked for an hour or so, but did not see the women without underwear.
Actually it doesn't make much difference.
That's what I figured. But I've also seen Acyd Burn mention in the past that the phpBB 3.0.6 update was so big, it almost broke the updater. That is why I was considering an incremental upgrade of 3.2.10 to 3.3.0 first. Ideally, I would prefer to skip that step and go straight to 3.3.1.
I've seen those cases as well but did not know it was due to human manipulation. I thought it was the upgrade process itself which fails, possibly due to timeout issue. So going from the latest older release to the latest newer release should work.
I'm feeling better about this. I'll do that. Thanks again.
Allow using Content-Security-Policy without unsafe-inline • Content-Security-Policystevemaury wrote: ↑Sun May 20, 2018 8:16 pm I went to your board and looked for an hour or so, but did not see the women without underwear.
Anyone with common sense would agree with that. And I agree with you.Lumpy Burgertushie wrote: ↑Fri Jul 10, 2020 10:30 pm telling people don't bother updating/upgrading is really not good advice .
Allow using Content-Security-Policy without unsafe-inline • Content-Security-Policystevemaury wrote: ↑Sun May 20, 2018 8:16 pm I went to your board and looked for an hour or so, but did not see the women without underwear.
It's not supported now; if every issue has a solution of "upgrade to 3.3", then 3.2 is essentially dead.I would be upgrading because all software has an EOL, and phpBB 3.2 has officially reached it as of July 6, 2020. Yet I know that they are also preparing to release phpBB 3.2.10 soon.
This from the guy with no cell phone who can't make minor modifications for his "clients". Replacing all files requires that you re-do all of your modifications; the more mods you've made the more work "upgrading" is.the proper way to upgrade and in my opinion, the proper way to update is to do a complet file replacement except for
the files/folders that are listed in the instructions to keep.
then run the databse update from the folder named install, then remove the folder named install and you are done.
I'm running 7.3.18 on 3.2.5 with no problems. 7.3 has some very annoying upgrade traits so if it was incompatible it would show rather quickly. I think maybe they're just pushing people to run 3.3. I didn't even know it was incompatible; I installed 3.2.5 under 7.0.x, hacked in a theme and then got sidetracked; meanwhile the server was upgrade to 7.3.18 and I've never seen a hiccup from PHPBB3.Upgrading has nothing to do with a broken installation. It is about progression. phpBB 3.2 supports up to PHP 7.2, while phpBB 3.3 supports PHP 7.3 and PHP 7.4, with PHP 8.0 support coming for 3.3.1 before it's release.
I'm surprised that you're running a big enough system that you care about mysql 8 or php 8 and you're using out of the box phpBB with no customization. phpBB isn't going to benefit much from either unless you have 1000s of simultaneous users posting. PHP8 doesn't interest me too much; the big pull for it is JIT, which isnt going to help much on a web system like PHPBB. I have phpBB installed on an old system with mysql 5.1 and another with 5.7 and there isn't much noticeable difference.PHP 8.0 is being release on November 26, 2020, which means phpBB is ahead of schedule. And with PHP 7.4 support for phpBB 3.3, that means MySQL 8.0 can be used without the bug issue. Yet it would still be best to wait until phpBB 3.3.2 comes out first, since they've working on improved MySQL 8.0 support. All of this adds up to bug fixes, security patches, performance, support, features and stability. It bridges the future. Everyone should update and upgrade their forums whenever possible. And while they're at it, update and upgrade other software components of their website if they need to and if they can.
Except that your spending 100s of hours planning for it and thinking about it.Updating and upgrading phpBB really isn't a big deal. It takes less than 5 minutes.
He probably heard it on Twitterstevemaury wrote: ↑Tue Jul 14, 2020 11:43 pm Please tell us where you see an indication that 3.2.x is EOL, because it isn't. Also, the whole idea of the 3.x line was to eliminate Mods and use extensions, which generally survive updates.
Why not move on to xenforo and other forum software? They add whatever anyone requests to their core and has new features every release.BarneyC wrote: ↑Tue Jul 14, 2020 3:50 pm How ridiculous is this project in general? They''re doing an EOL while still planning another release, and they haven't tested most of the extensions for 3.3. These are all good reasons to take a snapshot of the product and support it yourself. These are guys moving on without concern for the customer base, which is pretty typical in open source projects.
viewtopic.php?f=14&t=2534536stevemaury wrote: ↑Tue Jul 14, 2020 11:43 pm Please tell us where you see an indication that 3.2.x is EOL, because it isn't.
phpBB 3.2 will directly enter a reduced maintenance mode during which it will only receive changes for major issues as well as any security issues. The timetable for maintenance and security fixes is as follows:
- End of Maintenance (EOM): April 6th, 2020
- End of Life (EOL): July 6th, 2020
Allow using Content-Security-Policy without unsafe-inline • Content-Security-Policystevemaury wrote: ↑Sun May 20, 2018 8:16 pm I went to your board and looked for an hour or so, but did not see the women without underwear.
This is the kind of thing dumb open source weenies say when they don't understand the debate. I'm arguing that you take a snapshot of open source projects and make them your own, and you're telling me to go to something commercial where I'm at the mercy of lesser programmers. It's completely backwards and ridiculous.Why not move on to xenforo and other forum software? They add whatever anyone requests to their core and has new features every release.
Frameworks are for cranking out projects without having to put together all the glue. In 20 years a project should have its own code base. You build a website with bootstrap, and over time you rip it out and replace it with your own collection of components. symfony didn't exist before 2007. Who adds a framework to a 7 year old project?If coding using symphony is what kiddie do then why don't you make your own forums? It's all so easy.
Because you don't understand anything I've said. And who is "we", the 9 guys who post regularly on the forums?Seems like you don't like phpbb at all, why don't you move on to something better? We're happy with the direction phpbb takes and want it to stay the same even a decade later.
There a 3.3 demo. What specifically should I look at to see the great new features? Please point me so I can experience this great upgrade first hand. It looked pretty much the same to me the last time I looked at it.Your statements are just ridiculous and show your own ignorance. 3.3 is a huge upgrade over 3.2 and suggesting people shouldn't do it is ridiculous.