Hello and thank you for this fantastic module, I use it on a whole lot of my Drupal sites. I've got a few of these sites that will be moving to Backdrop CMS shortly, and they will need the Taxonomy menu module there as well. I am going to start to port this module as part of my upgrade process, but I wanted to leave a note here to see if any of the current maintainers of Taxonomy menu would be interested in collaborating on the port, or maintaining the Backdrop version as well.

I do understand that this module is already seeking co-maintainers, and it is likely that you are all too busy to take on anything else. If that is the case I will forge ahead on my own, but wanted to be sure I at least offered the project to those who know it best!

Thanks again for all you do for the Drupal community!

Comments

jenlampton created an issue.

dstol’s picture

Thanks for the note and all the work you've done so far jenlampton.

What does maintaining a backdrop port look like?

jenlampton’s picture

Thanks for your prompt reply @dstol.

@David Rothstein wrote up a fabulous three-part article on maintaining projects for Drupal and Backdrop at the same time: https://tag1consulting.com/blog/how-maintain-contrib-modules-drupal-and-...

In short, it's about what you expect. We have fewer Backdrop users than there are Drupal users, so the issue queues are currently a lot quieter.

jenlampton’s picture

The Backdrop version of the module is available if you'd like to have a look: https://github.com/backdrop-contrib/taxonomy_menu

There are some pretty significant differences between the Drupal + Backdrop versions because Backdrop does not have a Vocabulary ID, and most of the functions in taxonomy_menu were using $vid in one place or another.

The only other major difference was the use of configuration management (instead of variables), which actually resulted in cleaner code since we could eliminate the use of _taxonomy_menu_build_variable(). All other changes are pretty minor.