This topic is a place where folks can post agenda items for the upcoming weekly dev meeting that will happen on August 12th.
Backdrop LIVE
April 3-4, 2025
An interactive online event for anyone interested in Backdrop CMS. Everyone is welcome.
Recent topics
Posted 17 hours 37 min ago by RS Snyder (theflightrs) in How-To and Troubleshooting
Posted 2 days 22 hours ago by (Egmund) in How-To and Troubleshooting
Posted 3 days 45 min ago by (Z4N8r) in How-To and Troubleshooting
Posted 4 days 45 min ago by (dd123) in How-To and Troubleshooting
Posted 4 days 17 hours ago by (dd123) in How-To and Troubleshooting
Recent comments
Thank you for sharing your final solution. This may be very helpful for future visitors trying to do the same.
Views Accordion as primary navigation
I think this is good enough. Thanks for the surprise, @yorkshirepudding! Here's the CSS i use for future references. (Works on black, very minimal): /* ========== ACCORDION...
Views Accordion as primary navigation
Glad to hear it helped
Views Accordion as primary navigation
On top of that, i turned on "Use group header as the Accordion header" like: Excluded the taxonomy term Now: Another important setting: No autoheight (...
Views Accordion as primary navigation
In the View, under Format, click Settings next to where it will say Views Accordion for you: Set grouping field Nr.1 to be the Taxonomy Term: Name
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.