New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playlist doesn't load in FF when using direct link to party #201
Comments
Hey! Could you open the console (Right Click > Inspect Element > Console Tab) and show us the output if there is any? |
Yeah I can reproduce this. Working on a fix now. |
Fixed. Thanks for the heads-up! |
Wow, that was fast, thanks a lot! :) I assume I have to be patient a little longer for the changes to be deployed? |
Yeah this is not live yet. :) |
I see :) Last question, I promise: |
Very likely, but is this really a big problem to you? Seems like it would only occur once "in a lifetime", no? |
Well, there will be numerous international guests and if only 100 of them try to use Festify with Firefox resulting in the queue not loading properly the first time they try it, they might be confused, disappointed or might even complain (not all of them are tech savvy), so the overall impression will suffer and that's something I'd like to avoid. I'd also like to keep the voting process as easy and streamlined as possible, so I'd definitely prefer the direct URL over the intermediate step of entering the party code. On the other hand I need to get print material (timetables, handouts, etc) done asap on which I planned to include the Festify URL and some instructions. So I'm depending on you and your decision when you're going to deploy the fix... Please don't let me down ;) |
Fix is released now ✅ |
Amazing! Thanks a bunch! |
Thanks for your support! We have a donation button at the bottom of our website festify.rocks :) |
Hi,
when opening a party URL (https://festify.us/party/-L************p) in Firefox without entering the party code beforehand the playlist and party title can't be loaded / load infinitely (see screenshot for details).
Tested in FF 60.0.2 (Ubuntu 18.04) and FF 61.0 (Win7), both 64bit.
Note: Refreshing / reloading the page seems to fix the issue temporarily but after clearing FF's cache the issue reappears.
Can u help, pls?
The text was updated successfully, but these errors were encountered: