@BWPanda - I think your instructions would have worked fine, if I hadn't tried to outsmart them. I thought for a second that the services part of the file was going to install `b` in the /user/local/...
It's my assumption that "b" will be better than drush, just because it will get more support for Backdrop in the future. Isn't the backdrop extension of drush pretty much limited to deprecated...
I have been using only drush + the Backdrop extension for drush with lando, and it's been working fine for what I need it (automating the repetitive creation and tear-down of my many local sandboxes...
Posted6 days 9 hours ago by Greg Netsas (klonos) on:
Comments
This issue may be related (and it looks like it has a PR that can be tested):
https://github.com/backdrop/backdrop-issues/issues/2134
That PR wont be in production any time soon. But you could make a quick access condition module, its quite simple. Use as a guide: https://github.com/backdrop/backdrop/blob/1.x/core/modules/layout/plugins/access/path_layout_access.inc or https://github.com/backdrop-contrib/block_scheduler
Your form function would probably be something like:
And your access function:
Some adjustment may be necessary.
As an easy workaround without any coding Views could be your friend.
We'd need some more info about your use-case though. Could you describe a bit more, please?