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 :)
Recent comments
Preview comment flagged as spam as it contains a link to the website of an online game.
ERR_HTTP2_PROTOCOL_ERROR in Google Chrome and MS Edge
I did try something similar to this as well, but as far as I can tell, there is no option to set the timezone handling in backdrop's views. :( I can set a different date format, but I cannot...
How to Display Date & Time in Original and Local Time Zones
Being on a vacation, I can't check the option to choose a time zone format in a views block. However, here is another idea: Add the field to a layout. Backdrop allows individual fields to...
How to Display Date & Time in Original and Local Time Zones