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?
Some of it isn't intuitive.
Enable the locale module, which is needed for translating the interface, if you haven't already.
Download the language files if you haven't already: https...
Tried, it changes for all languages.
There should be a button or tab somewhere in the site info page for translation and next to some fields should write "this is a multi language field".
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?