I wrote a blog post that reflects my own thoughts on how I personally view Backdrop CMS as part of the larger community and a service to those being left behind by Drupal 9+.
I like Drupal 9 in some situations and for some client and still consider myself part of the Drupal community. I wish there were some way for the Drupal community to acknowledge that Backdrop CMS might meet the needs of some Drupal 7 users and that adopting Backdrop CMS is not abandoning Drupal, it's just a small fork in the road.
Backdrop CMS - Providing a Soft Landing for Drupal 7 Sites
I'd love feedback.
Recent comments
My initial goal was to create a menu item that linked to a view that I had configured and that was being created on installation of the module, by including the view config file. To do this, I just...
How to programmatically create a menu link
Yep, node_save() is just a wrapper for $node->save(). This is because the latter is Object-Oriented Programming (OOP), and a lot of people aren't as familiar with that. So the former can be used...
Difference between node->save() and node_save($node)
Seems that they must be the same thing. https://docs.backdropcms.org/api/backdrop/core%21modules%21node%21node.m... I am wondering now if the different behavior I experienced was impacted by other...
Difference between node->save() and node_save($node)
My difficulties were not so much around entity references or the specifics of creating content nodes for Organic Groups. I was dealing with another unresolved conflict between creating content types...
How to add en entity reference (organic groups) programmatically to create group content
It also did it for me too... so looks like something has unfixed itself :-)
There are multiple versions of module Cron Queue test in the installation.