I don't think this one needs discussion. Just action. This has been very close to RTBC for a long time. Does anyone have any final comments? Can someone do a code review? I would really like to see this in 1.29.
I'd like to discuss options for moving #2231 forward. It concerns having a simplified array syntax for database details that will support complex passwords better than the current db url and simpler than the D7 way.
There is a PR, but it is blocked when we get to trying to parse and write at install time. Greg (@klonos) proposed a better way of reading and writing settings.php by using token_get_all() in #6297 but that seems to have stalled.
I wonder whether splitting off the task into just supporting a simplified array and documenting that it is supported without changing the install process is the way to go to get some movement on this?
Hi
I added the 2 additional settings in settings.php, did a restart - and the error disappeared!
Thanks for the support!
(but the issues with the conversion still remain .....
I wonder if what is happening here is the default database settings are for utf8mb4 if the database server supports it.
In settings.php or settings.local.php if that's where you put your...
Posted20 hours 19 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
I've not done this with a menu before but something similar with different Views presentation blocks for different resolutions (i.e. not just responsive but a different presentation method...
Posted20 hours 35 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Thank you for all your help.
In the meantime I just edited the export db-file and removed the top line with the sandbox comment. --> Still the same issue.
I exported also with the...
Comments
Design / UX topics?
Some things that could get into the next release, if they make sense. Some of them are just ideas that need feedback.
A couple of text relelated ideas that MIGHT help make the layout system easier to use for some folks.
https://github.com/backdrop/backdrop-issues/issues/6698
https://github.com/backdrop/backdrop-issues/issues/6699
I don't think this one needs discussion. Just action. This has been very close to RTBC for a long time. Does anyone have any final comments? Can someone do a code review? I would really like to see this in 1.29.
https://github.com/backdrop/backdrop-issues/issues/6325
Developer Meeting:
Provide more complete template suggestions for entities in a standardized way
https://github.com/backdrop/backdrop-issues/issues/6651
https://github.com/backdrop/backdrop-issues/issues/1572#issuecomment-2099650024
Do we need a different solution that the one provided here?
Is this is an issue worth pursuing? Is there even interest in this idea?
I'd like to discuss options for moving #2231 forward. It concerns having a simplified array syntax for database details that will support complex passwords better than the current db url and simpler than the D7 way. There is a PR, but it is blocked when we get to trying to parse and write at install time. Greg (@klonos) proposed a better way of reading and writing settings.php by using token_get_all() in #6297 but that seems to have stalled. I wonder whether splitting off the task into just supporting a simplified array and documenting that it is supported without changing the install process is the way to go to get some movement on this?