I’ve pushed one of my websites live and it’s unable to be viewed with Internet Explorer and Safari browsers. It works on Firefox and Chrome.
If I try to interact with any part of my website that is connected to the database, I get the following error message…
“Oops, your browser seems to have cookies disabled. Make sure cookies are enabled”
t
I initially sent an emailo Bubble support about the issue, but it’s taking too long to resolve, so I’ve decided to post my problem on this forum.
Has anyone experienced this before?
Is it likely to be on my end, or on Bubbles end?
I’m stuck and don’t know what else to do.
I won’t post a link here to my development page, because it’s complete and private.
Guys, this has still not been resolved. If anyone else has any ideas, please let me know.
I’ve already begun creating a duplicate of my website in code using Visual Studio. If I finish the coded version before I get this issue resolved, I will have to scrap Bubble altogether for this particular website.
What concerns me the most is that my next website is going to be literally ten times more complex, so it doesn’t exactly give me much confidence for my next project. I’ve already built half of it in Bubble, but have put the brakes on incase my first websites issues do not get resolved.
Yep, they said they would check it and get back to me. It’s taking weeks, so I decided to make a start by coding it myself. It will take me months to finish the code, so I’m still sticking with Bubble if this gets resolved by then.
Those buttons are performing actions which access the database. The buttons that work, are accessing only custom states and not the database, both directly or indirectly.
The table on the front page is not stored as a User. If someones family member comes along to use it, I wanted them to be able to reset it. It is just a temporary-data table…
(more info below the images below)
What happens is - when a whole cycle has been completed (50 attempts), if the User is logged in, the data from that cycle will then be stored as a User and it will be stored on a different table which shows up when the user presses the “All History” button…
Yes, it was the Restart one that causes a read of the Cookie that fails. But wondered why it needed that cookie. It sort of looks like the Restart button needs something on the dummy user ID.