Skip to content
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

Empty page on fresh install (conflict with Windscribe Chrome Extension) #324

Open
lukyanov opened this issue Nov 20, 2024 · 3 comments
Open

Comments

@lukyanov
Copy link

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:

image image

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.

@vincanger
Copy link
Collaborator

Hey @lukyanov we actually fixed this but haven't deployed the changes yet.

The fix is to rename the PageViewSourcesTable.tsx to something like SourcesTable.tsx

@lukyanov
Copy link
Author

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?

@vincanger
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants