96786
results for "wordpress"
-
Custom comment types is back on the horizon? Time to read some trac tickets
GWG
at
2026-09-22 17:55
-
and maybe a code split is the right solution, but that needs contributors to maintain these
[pfefferle]
at
2026-09-22 13:15
-
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]
at
2026-09-22 13:14
-
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]
at
2026-09-22 13:13
-
OK. This may beyond my current ability to think about
[jeremycherfas]
at
2026-09-22 13:08
-
(I have basically rephrased what @tdrayson already wrote
[pfefferle]
at
2026-09-22 13:05
-
to not run into that problem, I would love to think about options to support both platforms
[pfefferle]
at
2026-09-22 13:04
-
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]
at
2026-09-22 13:02
-
[jeremycherfas] a plugin being secure can mean that the vulnerability was simply not found at that moment
[pfefferle]
at
2026-09-22 13:01
-
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]
at
2026-09-22 13:00