Hope you are all having a nice holiday!
I’m looking for a bit of help with something - I’m getting married next year, and thought I’d create a few pages on Bubble to help manage the guest list and what not.
I have a list of guests in a spreadsheet, that I want to load into Bubble and send to the app to RSVP etc.
I don’t have their email addresses, so I was wondering if there is some way that I can load this list, create accounts for them, and give them a way to log in without the need for the normal sign-up process.
Important that they are users, because some of them are allowed “plus ones” and others aren’t - need a way to add constraints to the form.
Hi there, @jamie.robson.89… first, congrats on the wedding! Now, I think I speak for a lot of longtime Bubblers when I say we better be on that list, man. Do the right thing, Jay.
If these folks have to be users, they will have to log in via an email address (which you could fake when you create accounts for them) and password (which they won’t know, and you can’t send a password reset email because you don’t have their email addresses) or a magic login link (which you also can’t send because you don’t have their email addresses).
So, unless I am missing something (which could be the case because I have never tried to get super creative with trying to bypass the conventional sign up/log in processes), I can’t see how you can do what you want here. That being said, if you don’t have their email addresses, how are you going to contact them so they know where to go to RSVP?
Thanks @mikeloc! Bold of you to assume that I am the one in charge of the guest list
All of the invites are being sent in the mail, with a link that takes them into the app.
I’m wondering if a better way to do this is to create “Guests” rather than “Users” and give each of them a unique code. When they fill out the
RSVP form, they enter their unique code, and a conditional is used to show the “plus one” option.
Ha! I totally forgot about the actual mail! No, seriously, I really did.
Yeah, if I was doing what you are trying to do, I would probably go the “guest” route, too. That being said, George is typing now, and he is going to tell you what I have missed and how easy it all is.
Individual QR codes which contains a URL to a login page with parameters ?email=[email]&password=[password]. Email is a dummy email created for that user (e.g random email@example.com) Password is another random string created. When page is loaded, log user in with credentials from URL parameter and make them change the email and password.
The only thing is you have to generate a QR code for each user and print them which might take some time, but 1. you could do that programmatically 2. if you’re developing a Bubble app for your own wedding RSVPs you probably have the time anyway.
Edit: by the way, you don’t have to use QR codes - I just thought that make make the most sense if you want people to get a link from a card (typing it manually will throw loads of people off and I imagine many will be of a generation which will require a lot of support…). That or RFID cards but depends how thin your wife will let you spread the budget
Yeah I was thinking about QR codes anyway for that exact reason - I think I’ll go with a combination of that and the “guest/unique code” option, seems easier.
I like the RFID option… we already saved a £££ by doing the invites ourselves, so I could potentially repurpose that! I imagine Granny Robson will be utterly confused though.
Appreciate both of your input both, have a great new year.
To set everything up in Bubble, you could have a backend workflow that takes a Name parameter which Creates an account for someone else with the dummy email and password, then generates a QR code using an API with the relevant URL and parameters, then write it to Bubble DB or send you an email or something. Then just schedule API workflow on a list from a multiline input split by new lines. That’d be the simple method (obviously it’s not very flexible, but it doesn’t sound like you need to be)
Oh, on the unique code option, you could have a Login data type which contains login code, name, tempPassword, and tempEmail. Your QR code can just be a standard URL for all cards (easier to print). When user enters login code, use a backend workflow to bypass privacy rules on the Login data type and return an entry with a matching code. Then log the user in with those details. If it’s just an app for your friends and families and you can probably get away with just making the login data type publicly visible though
This way you have real accounts which is helpful for data segregation and avoiding any accidental bugs and your invitees won’t tell the difference.