Thanks @julian

Tags are lowercased so we don't have to deal with different versions, NodeBB and nOdEbB would be different tags if we allowed uppercase letters. If you want them to have the first letter capitalized you can add the text-capitalize class to the tags. [image: 1702343859542-1d0937cb-ddad-4a7f-9467-c30201c5cd53-image.png]

@baris, nevermind, I just had to restart the app on Cloudron, not sure why.

@baris yes, I am using ios, but cannot test the same thing on android right now... and it is the same for firefox and safari...

@julian said in How do I create a registration interstitial?: The hook is fired on POST /register so that the user can be redirected to the interstitial during the registration process. So you do need to have it respond there in order for the flow to work. Interesting, the flow still seems to work perfectly (the custom interstitials do show up on redirect to /register/complete) with the following code right at the beginning of the hook handler: const url = data.req.originalUrl; if (!url.startsWith("/register/complete")) { return data; } How is that possible?

Yes, but you need some custom js. You would need to insert a dropdown for the languages and then make an api call to set the users language and refresh the page.

@julian, I am trying to implement your suggestion. @julian said in Share your opinion on my unique user registration process, please?: As long as those form fields have name, then it is added to the form data, and sent to the backend. So, I would still need to implement some backend code to save this to the user object, right? using the setter here: https://community.nodebb.org/topic/16994/how-do-i-add-custom-user-fields-to-my-theme Because, doing db.objects.find({username: "test"}) doesn't include the custom fields. @julian said in Share your opinion on my unique user registration process, please?: You probably can't see the additional info in the registration queue template, so you may have to modify that one too. The API response for /api/admin/manage/registration does not contain the custom fields. Am I doing something wrong, or is this expected? What is the easiest way to add these fields to the API response? Thank you.

Most likely all server-side hooks are not specific to users (unless the UID is in the hook name, but I doubt we have any), so you'll have to just do an early-return if the condition doesn't match. It is likely not going to cause issues with the server. There are a thousand things that would need to be optimized before something like this causes a slowdown