This topic is a place where folks can post agenda items for the upcoming weekly dev meeting that will happen on August 12th.
Recent topics
Posted 1 day 30 min ago by (Vicki L.) in How-To and Troubleshooting
Posted 1 day 13 hours ago by (Enthusiast) in Requests and Feedback
Posted 1 day 17 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) in Weekly Meetings
Posted 2 days 13 hours ago by (Bill_Lea) in Requests and Feedback
Posted 1 week 15 hours ago by Jason Flatt (oadaeh) in How-To and Troubleshooting
Recent comments
@yorkshirepudding Thanks for that bit of information. I checked and this is what was found: There were several json files in the active folder: field.field.taxonomyextra.json...
taxonomyextra table after migration from Drupal 6
To confirm that it is ok to be deleted, I would look in the config folder for any config files with the string taxonomyextra in. If you don't find any, then yet it is probably safe to drop...
taxonomyextra table after migration from Drupal 6
Today there was finally time to delve into this issue. First I downloaded the field_data_taxonomyextra table into a spreadsheet. There is a column called Bundle, which in my case included,...
taxonomyextra table after migration from Drupal 6
Hi Enthusiast - there is work in progress on an improvement to core that I think will help this. https://github.com/backdrop/backdrop-issues/issues/4127 I don't fully understand it...
The problem of caching the pages
As time ran out to discuss this last week, I would like to discuss https://github.com/backdrop/backdrop-issues/issues/6900 (Pre-existing field with reserved entity machine name re-used on entity...
Comments
Hi,
this week I'd like to ask for help re a pull request stuck in Zen.CI failures.
The Issue (3008) is about broken module updates in environments with a symlink as doc root.
Our problem is, that we can not reproduce the test failures outside Zen.CI, but the same failures always happen inside. And they might be related to the code change.
As long as we can't reproduce it, we can't fix it - so we're stuck.
The bugfix would be important to make Backdrop usable in more hosting environments. Symlinks as document root aren't so uncommon.
I thought it might be the branch, but I tried creating a new branch from scratch and opening a new pull request, and it has the same problem, an Internal Server Error and then the test failures. This is PR 3682.
I second that. Two common German webhosting providers (1&1 Ionos, and Strato) use symlinks as document root. Which means, you can't update modules, themes, or core via the Backdrop interface. In my case, about 3 out of 10 clients have a contract with one of these providers.
This may not fall under the topic of "dev", but it warrants discussion. Backdropcms.org is infested with spam accounts (spot-checking suggests that the vast majority of the 7K+ user accounts are spam). We need to take more aggressive steps to prevent them.
See this Zulip discussion and this issue.