Login toboggan is 'ported', but apparently never tested. hook_user_update has exactly one parameter in backdrop cms, but function logintoboggan_user_update uses three. I fixed it leaving only one, and submitted an issue in ghithub.
If I recall, Login Toboggan also has some features that can be removed from the module since they are now included in Backdrop core (such as ability to login with email address, maybe others).
Here are some more details about my setup. Yes, I am using a contextual filter.
Specifically, I have several content types that have an entity reference field meant to hold references to...
There's a few way to accomplish it, but it really depends on your full requirements.
I'm working on a contact management module but it won't be released for a few months.
There...
I'm fairly sure that some people have done this successfully in Backdrop. Please can you list the modules you are using; that should help us get the right people to join this conversation.
Posted1 day 3 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Another content type for the addresses is a good option, and there are some more, for instance:
Use the Address Field.
If you already use Paragraphs (or are open...
Posted1 day 3 hours ago by Olaf Grabienski (Olafski) on:
Comments
Thanks for doing that. That maintainer might no longer be involved. I can look into adding your fix and look for a new maintainer.
If I recall, Login Toboggan also has some features that can be removed from the module since they are now included in Backdrop core (such as ability to login with email address, maybe others).