We’ve been testing the application builder and to be honest it seems like a dream come true. However, the problem is that whenever you publish changes to the site, the domain (domain.baserow.site) gives a 500 Server and the site just doesn’t function. The only way to get it to work again is to clear your cookies on the site and reload. Obviously, this is not practica as we cabn’t have users clear their cookies every time we publish a change. S I’m wondering what is going on here. Seems to be some bug in your system.
Hi @ddsgad,
Sorry to hear about the continued issues with this. It definitely sounds like a bug!
Could you share some details on how you are using Baserow (Locally/Cloud) and how you have set up the application within the App Builder? We are aware of one issue with user roles and permissions that was causing a similar problem. Perhaps you could try removing the user auth table from the app settings and adding it again? This will also require you to update all element / pages that were using that functionality.
If that is not something you have implemented in your app or it’s not a practical solution, could you DM me some mroe details about your domain so we could look further into this?
It’s baserow in the cloud. Yes, there is a bug in your Auth for sure. That’s why when you clear cookies it works. We have already tried deleting auth and adding it again. The same problem reoccurs. Others have reported it from what I can see in searching past posts. If you use auth, and then make changes and republish, the site gives a 500 error unless you clear cookies.
This is happening also on custom domain, and it’s causing issues for our users as well.
To be more specific, we don’t get a 500 error, but after publishing changes the page gets blank without any possibility to log in or out. The only option is to clear the browser cookies. This is a huge pain when there are many users relying on the application to work.
If you view the code in developer tools, you will see the 500 error. There is some bug in their Auth code. Unfortunately, if you need people to log in, it’s not possible to use the application builder yet in production, due to this bug. I don’t see any issue to fix this.
1 Like
Hey @patrick are all your elements invisibles to the loggued out users for he given path? May be you could add a link to return to the login page that is visible to only loggued out visitors? Later we will have an automatic redirection to the login page, but it’s not implemented yet.
Hey @ddsgad could you send me a screenshot of the error when an authentication error happens? Could you also tell me if it happens with all browsers or certain browsers or at least the browser you are using?
Does this error happen with all publish or only when you do some specific changes?
@jrmi Thanks for the suggestion. I’ll try this and report back.
1 Like
@jrmi - All my pages have a button that is only visible to logged out users, linking to the login page. Unfortunately nothing is displayed on the pages after I publish changes to the app, except for the background color of the page.