96786
results for "wordpress"
-
fix
[pfefferle]
at
2026-09-22 13:00
-
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
tdrayson
at
2026-09-22 12:40
-
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
[jeremycherfas]
at
2026-09-22 12:29
-
[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
[pfefferle]
at
2026-09-22 11:19
-
so is the suggestion to have two versions? ClassicPress and WordPress ones?
[pfefferle]
at
2026-09-22 11:18
-
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
[jeremycherfas]
at
2026-09-22 10:50
-
[dshanske] any ideas how we can shim/polyfill the missing features!? so that we can keep up with development, but stay backwards/downwards compatible
[pfefferle]
at
2026-09-22 06:37
-
If it becomes too much of an issue I'll step up
GWG
at
2026-09-22 00:06
-
[pfefferle]: I am using the plugins on ClassicPress and am concerned about how we'll maintain the split
GWG
at
2026-09-22 00:05
-
I think it is not removing features, but not implementing them
[pfefferle]
at
2026-09-21 22:05