You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying open-saas for the first time. The very first thing I saw after the installation was a completely empty page in Chrome at http://localhost:3000.
It took me some time to realize that was because of the Windscribe VPN Chrome Extension. Apart from VPN service they also block some analytics requests. Usually, on other websites, the only thing that is not working in this case is analytics. But with open-saas the whole website becomes completely broken.
If you look at the Chrome Developer Console, you would see that it's actually analytics requests that are failing:
While it may seem the issue is not on the Open SaaS side, I was wondering if it's possible to ignore error/blocking requests in analytics and continue rendering the site.
The text was updated successfully, but these errors were encountered:
Thanks! This is an analytics-related request, right? I mean there is the "analytics" folder in the path. What if at some day they decide to block SourcesTable.tsx as well? Is it possible to make the site work (not render an empty page) even if the analytics requests fail?
Hmm. Good question @lukyanov. These are analytics components for the Admin Dashboard so I assume in blocking any of the components the app will fail.
We could experiment with different renaming of the folders and components to see what results we get. If you'd like to dig deeper and report back, that would be much appreciated.
I'm trying open-saas for the first time. The very first thing I saw after the installation was a completely empty page in Chrome at http://localhost:3000.
It took me some time to realize that was because of the Windscribe VPN Chrome Extension. Apart from VPN service they also block some analytics requests. Usually, on other websites, the only thing that is not working in this case is analytics. But with open-saas the whole website becomes completely broken.
If you look at the Chrome Developer Console, you would see that it's actually analytics requests that are failing:
While it may seem the issue is not on the Open SaaS side, I was wondering if it's possible to ignore error/blocking requests in analytics and continue rendering the site.
The text was updated successfully, but these errors were encountered: