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.
We don't seem to have any guidelines or procedures, how to sunset a project.
Recently there was some guessing in our Zulip chat (not the public part), what to do with a project that's obsolete, replaced by another project, and shows no installs in the stats - and nobody knew how to handle that. The suggestions sounded more like workarounds, not solutions.
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 isn't an option for me; I didn't know what else to do. I didn't want to take any actions like "archiving" it until I found out if there's an official policy.
This is a security precaution. It's not recommended and it's not documented in the settings.php file, but you can set allow_insecure_uploads to be TRUE if you wish to allow uploading files like...
You can create a small custom module using this hook:
https://github.com/backdrop-contrib/webform/blob/136c20cb1c51cea203f3f0bc5355237c1d4dbf84/webform.api.php#L652-L678
/**
* Determine...
Posted13 hours 9 min ago by Martin Price (yorkshirepudding) on:
try sample.js.gz or sample.framework.js.gz or sample.js or anything smiliar and .js even if its not the file extension or it is, it will be renamed to _js. This is hardcoded security thing and i...
You can upload them through Content > Manage files > Add files (URL: /file/add) and they will be marked as permanent. Note that you should be able to multiselect or drag multiple images...
Comments
The need for a clear AI policy is growing. Please can this be a priority.
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.
We don't seem to have any guidelines or procedures, how to sunset a project.
Recently there was some guessing in our Zulip chat (not the public part), what to do with a project that's obsolete, replaced by another project, and shows no installs in the stats - and nobody knew how to handle that. The suggestions sounded more like workarounds, not solutions.
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 isn't an option for me; I didn't know what else to do. I didn't want to take any actions like "archiving" it until I found out if there's an official policy.