Once #49 gets in, what stopping us from using entity translation instead of content translation
Pros: unified way of handling translation (nodes, taxonomy, ...) no need of i18n
Cons: still hard to manage translations of menu, block and other things
Related - https://github.com/backdrop/backdrop-issues/issues/4198 Content translation improvements
As people weigh in here with reasons they prefer (or were forced) to use entity translation, I would love if it we could add those reasons to that issue too -- since many of those improvements will be able to be included before 2025 :)
GitHub Issue #:
52
Recent comments
I think given the warning on the source site: At this time, if your new project can afford to require PHP 5.5+, which it should, please use PHP's native password_hash() /...
July 31, 2025
I did a very quick test and if the Display format of the webform submission value is HTML then it appears but if plain text then it doesn't, so something is included regardless of if empty when...
"Hide rewriting if empty" has no effect
Just to clarify it appears that the item: Fix Search for "On the Web" module, is about the search on backdropcms.org at https://backdropcms.org/modules
July 31, 2025