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 3 days 15 hours ago by Francis Greaves (themetman) in How-To and Troubleshooting
Posted 1 week 2 days ago by Francis Greaves (themetman) in How-To and Troubleshooting
Posted 2 weeks 4 days ago by (izmeez) in How-To and Troubleshooting
Posted 2 weeks 5 days ago by (izmeez) in How-To and Troubleshooting
Posted 2 weeks 5 days ago by (ian) in How-To and Troubleshooting
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
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.
This may be somewhat difficult to address for various reasons.
Some projects may look abandoned to someone new looking at it and yet may show a number of installs. The number of installs may not indicate it is actually being used, or it may indicate use on old sites that are still present and becoming unmaintained themselves.
So what is the goal:
There may be more goals.
The primary goal is clarity: what happens / has to happen if... ;-)
Currently, for example, I couldn't even deprecate my own projects, they will still show up in all project installers. And there's nothing I could do about it.
The other thing is: what happens with projects that are definitely unmaintained, and nobody wants to take over, and the project's already known to break sites only by installing (an extreme example, of course, but that can and will happen at some point, as PHP moves on).
Is it even (technically) possible to prevent such a rotten tomato from showing up in the installer? Be it, because a maintainer wants it, or because it's clear, that tomato will never get fresh again, as several attempts to fix the problems failed (example: a module that depends on a 3rd party service that has passed away).
There are probably several situations, where a defined way to sunset a project - clearly documented - is beneficial. Currently I don't think, there is a way.