#wordpress 2026-09-22
2026-09-22 UTC
[Sophia] and GWG joined the channel
# 
[pfefferle] [dshanske] any ideas how we can shim/polyfill the missing features!? so that we can keep up with development, but stay backwards/downwards compatible?
[artlung]1 joined the channel
# 
[jeremycherfas] ClassicPress gets security updates regularly. I’m asking for forks of the IndieWeb plugins so that they stay secure and maybe add features that people think are valuable.
# [pfefferle] so is the suggestion to have two versions? ClassicPress and WordPress ones?
# [pfefferle] [jeremycherfas] I have not meant that ClassicPress does not get security updates, but your plugins! You mentioned that you disabled auto updates for the plugins!
# [jeremycherfas] I don’t understand. If a plugin was secure in a previous version of WP/CP, can it become insecure if only the CP/WP version changes, not the plugin?
# 
tdrayson a plugin can become insecure without anything anything changing, its just the vulnerability hadn't been found previously. I dont think it can inherently become insecure, as WordPress is pretty good at ensuring backwards compatibility, the only way would be if they changed a capability to a different role or something or changed how something you hook into works, but again WP are pretty good at not breaking backcom
# [pfefferle] I am not sure we are talking about the same thing!? Not updating a plugin to the latest version always implies the risk of being vulnerable, because updates also fixing issues. If one of the plugins you use in ClassicPress will no longer be backwards compatible because of a recent change, it will always stay at the latest compatible version. So if something is fixed afterwards, you won't be able to update the plugin to have that
# [pfefferle] fix!?
# [pfefferle] [jeremycherfas] a plugin being secure can mean that the vulnerability was simply not found at that moment!?
# [pfefferle] I can not and will not guarantee that my plugins are free of bugs and/or vulnerabilities! I do my best, but I am only human 😉
# [pfefferle] to not run into that problem, I would love to think about options to support both platforms
# [pfefferle] (I have basically rephrased what @tdrayson already wrote 🤭)
# [jeremycherfas] OK. This may beyond my current ability to think about.
# [pfefferle] the main problem is, that WordPress has a higher pace with new features and ClassicPress does not port all of them. Some are essential I would say, like the custom comment types, that might land in WordPress 7.2. This feature alone would save us a lot of code and complexity and would make interoperability with other federated systems (that store likes, faves, ...) so much easier.
# [pfefferle] I do not want to simply ignore ClassicPress users, but would really love to find a way to deal with such things in the future.
# [pfefferle] and maybe a code split is the right solution, but that needs contributors to maintain these.
[manton], ramia, realramia, ramai2, rMdes and [aciccarello] joined the channel
[Sophia]1 joined the channel