#wordpress 2023-02-13

2023-02-13 UTC
[aciccarello] joined the channel
#
GWG I migrated Compass which required PHP 7.4 to a new server and upgraded the one I use for development to PHP8.2 and I'm getting errors.. time to check plugins
[asuh] joined the channel
#
[asuh] gwg are you going to continue 7.4 compatibility even if you support 8.x?
#
GWG [asuh]: Yes, I was hoping to continue all the way back to PHP5.6
#
GWG But need to accommodate the strictness of 8+
#
[asuh] nice. i would recommend letting go of anything before 7, esp since WP docs say 7.4 minimum
#
[asuh] but, i get it, we’re supporting as many as we can
#
GWG [asuh]: I'm wondering if there is a difference codewise?
#
[asuh] gwg, it’s a great question. Many syntactic sugar additions that I enjoy like null coalescing operators and `use` declarations to group imports, and even more niceness up to 7.4 like arrow functions. The biggest benefits is speed. But, yeah, it seems many of the changes are preference and conciseness
#
GWG I love the idea of null coalescing operator.
#
[asuh] Same, it’s quite useful in modern JS as well
#
GWG [asuh]: I'll get there.
#
[asuh] You’ve given us so much already, I’m just one little opinion 🙂. Thanks for everything you do!
#
[asuh] Interestingly, WP says 5.6 is still used by 4.6% of sites. I wonder what would be a good target % to drop older PHP?
#
[asuh] https://wordpress.org/about/stats/
#
GWG [asuh]: When WordPress drops support for it.
RasAlGhoul joined the channel
#
[snarfed] [asuh] already mentioned ^, evidently they already did. https://wordpress.org/documentation/article/before-you-install/#requirements-on-the-server-side says they now require 7.4
#
[asuh] [snarfed] It appears WordPress’ code is still 5.6 compatible but is recommended to run 7.4.
#
[snarfed] ^ that link says required, not just recommended. So evidently they've already technically dropped support
#
[asuh] Best I can understand is when they move 5.6 to the `allow_failures` section of this file, that’s when they abandon compatibility.
#
[asuh] https://core.trac.wordpress.org/browser/trunk/.travis.yml?rev=44950
#
GWG https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/
#
[snarfed] Yay five different places that all say different things 😆
#
Loqi 😊
#
GWG You can see why I'm reluctant to drop support for 5.6 yet.
#
GWG As much as I'd like the null coalescing operator
#
GWG PHP8's strictness helped me find a very subtle typo in my code that older versions accepted.
#
[asuh] Yeah, it makes sense to hang on to 5.6. Despite that, it’s fascinating to see how quickly majority usage went from 5.6 to 7.4 in the last four years.
#
[snarfed] Sounds like right now testing should be the higher priority, especially with the merge about to launch?
#
GWG [snarfed]: We have one problem with Webmentions, triggering the upgrade on plugin install.
#
GWG I had suggested a technique I use in other plugins, which is triggering it on load or settings page.
#
[snarfed] Have you tested on multiple PHP versions? That's what bit synd links, right?
#
[chrisbergr] If you go to /wp-admin/site-health.php on your install on php <7.4 it'll give you the invitation to update as part or critical problems
#
[chrisbergr] *of not or
#
GWG [snarfed]: No, that was just one person's problem. The problem was I didn't test with the flag that loaded the disabled webmention files enabled.
#
GWG Since I'd disabled them.
#
[snarfed] Ah, so the final code that got released didn't get tested?
#
[snarfed] Ok
#
GWG [snarfed]: I need to add a test that loads the pieces that are disabled and then tests them.
#
[snarfed] GWG++ testing++
#
Loqi testing has 2 karma in this channel over the last year (4 in all channels)
#
Loqi GWG has 13 karma in this channel over the last year (60 in all channels)
#
GWG [snarfed]: My code coverage isn't as complete as yours, I admit.
#
[snarfed] Different situations anyway
gRegor, GWG, [marksuth], irl25519, [pfefferle]1, [tantek]1, [asuh]1, [KevinMarks]1, [tw2113_Slack_]1, [aciccarello]1, [marksuth]1, [snarfed]1, [chrisbergr]1, [jacky]1, IWSlackGateway, [tantek]2, _IWDiscordRelay, _Skyther[d], [pfefferle]2, Kaja_ and pmlnr joined the channel
#
[pfefferle]2 [chrisbergr] [dshanske] but what about auto updates in the background? How many people are using the wp-Admin especially in the IndieWeb community (micropub)
#
[chrisbergr]1 Good question, I would never allow auto-updates of plugins, thats way to risky... But of course I can not make conclusions from my behavior to others.
#
[chrisbergr]1 Is this simple answer helpful? - https://stackoverflow.com/a/40824099
#
sebbu wordpress by default auto-updates itself, but maybe not plugins and themes
vo1d and [zetareticoli] joined the channel
#
[chrisbergr]1 You can opt in for auto updates for each plugin individually on the plugins list. It's in the right column.Also, non-security core updates are not automatically per default.
#
GWG I wonder if there's a way to require that a major version update for a plugin be manually updated
#
[chrisbergr]1 I guess not. But there are more ways to auto update. e.g. I have a lot of client sites secured with the wpmu dev suite, I can auto update everything on every connected page from within the wpmu dashboard. And there are some hosting solutions also stuffed with update processes.
#
GWG The upgrade triggering is our last blocker concern.
#
GWG The migration code is good...so it is mostly how it runs
#
GWG Maybe...
#
GWG If the view code detects a Webmention comment type..it schedules a migration check.
#
GWG If the settings page is loaded, it triggers one
#
GWG So 3 ways to check and schedule one
RasAlGhoul, irl25519, IWSlackGateway, jeremych-, jeremycherfas, [tantek], [KevinMarks], [aciccarello], [jacky], gRegor, gRegorLove_, [chrisbergr], [dave], [snarfed], [tw2113_Slack_], [campegg] and angelo joined the channel