Trigger was removed from core for D8 without providing a worthy alternative other than Rules (which by many is considered a "cumbersome piece of code with a confusing UI"). Having in mind our goals to be providing as much backwards compatibility as possible and easier transition from D7 to Backdrop, should we consider bringing trigger.module back in Backdrop core ...or at least putting it in contrib as a "lightweight" alternative to Rules (which is not fully ported yet and might take time to do so)?
For the record, here's a summary of the reasons for it's removal from D8 core (from the respective issue in the d.org issue queue: Remove Trigger module from core [#764558]):
The actions API is wonky (look up your action via hash of function name?), actions/trigger has no maintainer in MAINTAINERS.txt and we have not seen the promised conversion of things like node operations into actions.
Also, the trigger UI is weak, and there's not a lot you can do with it.
In general, people use a contrib module like Rules - so let's just put this code back in contrib where it belongs and reduce some of the bloat in core.
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