Nate has recently revived the feature request Add option to globally disable comments on a content type and asked if somebody is interested in advocating for this issue. I don't want to advocate for the issue (have another in mind), but I'm definitely interested in reviving it. However, to me it's not yet clear what exactly we're trying to achieve there. Therefore, I suggest to discuss the goals of the issue at the weekly meeting.
This issue relates to the occasional, but common enough to warrant attention, issue of the status report showing a warning of site updates required, but when going to run updates, nothing happens: https://github.com/backdrop/backdrop-issues/issues/7010
More details in the issue and there is a Pull Request but so far no testing or review other than what I have done.
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module...
If there's some time left in the dev meeting - although it might rather be a topic for the PMC:
We have nice documentation and procedures, how to provide projects in backdrop-contrib space...
You can edit this View (/admin/structure/views) to suit your needs. The MORE link is used to display additional results, which can sometimes be useful.
Hello,
I have a question about the block “Recent blog posts”.
I've set it up so that the five most recent blog posts are always displayed on the page (mybackdrop.de/blog) at the TOP...
Comments
Nate has recently revived the feature request Add option to globally disable comments on a content type and asked if somebody is interested in advocating for this issue. I don't want to advocate for the issue (have another in mind), but I'm definitely interested in reviving it. However, to me it's not yet clear what exactly we're trying to achieve there. Therefore, I suggest to discuss the goals of the issue at the weekly meeting.
https://github.com/backdrop/backdrop-issues/issues/7010
More details in the issue and there is a Pull Request but so far no testing or review other than what I have done.
Re PHP 8.5 compatibility: not ready yet for review, but tests are passing now.
So, still work in progress with issue #7008.