Please use this topic to suggest agenda items for our weekly meetings.
Weekly office hours
Bring your questions to our weekly virtual office hours, every Wednesday. Everyone is welcome.
Recent topics
Posted 5 hours 27 sec ago by (indigoxela) in Weekly Meetings
Posted 14 hours 29 min ago by (sergioroman) in How-To and Troubleshooting
Posted 14 hours 49 min ago by (aubergine) in How-To and Troubleshooting
Posted 1 day 17 hours ago by (seamus) in Help Wanted (Job Listings)
Posted 1 day 21 hours ago by (aubergine) in How-To and Troubleshooting
Recent comments
How to deal with abandoned projects? So far, I don't think there has ever been a deprecated, officially unsupported project (module or theme...). But it's also unclear, what the steps...
June 26th 2025 Weekly Meetings
For the second error, we need to figure out which theme hook is producing it. Are you able to enable Devel and insert a debuging line where the problem happens? In line 1102 of theme.inc,...
Error TypeError: Unsupported operand types: null + array...
Did the first error go away? Are you only getting the second error now? I encourage you to post your question on Zulip for quicker interaction. If someone helps you solve the problem, then...
Error TypeError: Unsupported operand types: null + array...
The datatables module, https://github.com/backdrop-contrib/datatables, continues to improve thanks to the work of the maintainer. The server-side processing is now working even on my dev...
Views responsive tables
Hey, that was quick! Thanks for your reply. I just tried disabling the color module in a local environment and I get the same error as clearing the cache. Error Unsupported operand...
Comments
How to deal with abandoned projects?
So far, I don't think there has ever been a deprecated, officially unsupported project (module or theme...).
But it's also unclear, what the steps are to achieve that. It's even unclear, if that's possible at all. Very likely help from someone with sufficient permissions on backdropcms.org is necessary.
I think, the approach - or to start with, the policy - should get documented somewhere.
1.4k contrib projects exist on GitHub, and people start to find broken, outdated, unmaintained, obsolete ones, which still show up in the installer. It doesn't seem ideal to leave all those zombies in an installable state (via Project Browser), because that means, site admins have to decide whether somethings safe to install, while they don't see the whole picture (last commit ages ago, open issue with warnings, might break the site worst case...).
The bug squad is a great idea, but not the solution for completely abandoned projects.
As PHP and Backdrop core move on, problems with those "zombies" will increase. At least, that's what I assume.