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

Library, listen, and audio analysis, pages should work for public access scenarios #298

Closed
atruskie opened this issue Feb 22, 2017 · 0 comments

Comments

@atruskie
Copy link
Member

atruskie commented Feb 22, 2017

Now we have public access to areas of the site, our client pages should also function without requiring a user to log in.

Also, ensure the correct data and options/actions are shown.

@atruskie atruskie changed the title Library pages should work for public access scenarios Library, listen, and audio analysis, pages should work for public access scenarios Feb 22, 2017
atruskie added a commit that referenced this issue Oct 29, 2019
baw-server mostly supports the notion of public read access to pages. The client never recieved such love.

This is a hacky implementation. It spits a lot of errors but should work generally allow access as long as API resources do not return 401s.

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

No branches or pull requests

1 participant