You can see a that a couple pretty-important sections of the relaunched site are still not working.
If anyone has experience troubleshooting or building reactJS apps, satellites, etc. please chime in here with contact info, as I don’t have much knowledge of these platforms.
-mwic

Hi mwic,
I did some tests with the beta page and tried the login which failed on this page:
https://beta.ccmixter.org

When I open the console in the browser I get following error message:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://ccmixter.org/api/user/current. (Reason: CORS header ‘Access-Control-Allow-Origin’ does not match †http://dig.ccmixter.org’).

This usually means that your webserver has a configuration problem.
The CORS system is there to protect the webpage, so i can not load data from any other site on the net, when its not allowed by CORS.
When I look at the server response of a beta page, it sends the header:
Access-Control-Allow-Origin http://dig.ccmixter.org
The error is the wrong subdomain “dig”. It should be “beta”!

I did a test with the free Firefox addon “Allow CORS: Access-Control-Allow-Origin” and with the right settings
the beta page works fine. This addon can manipulte CORS settings for testing.

So a solution could be, if you change the configuration of the webserver which hosts the beta.ccmixter.org page.
If it is a apache webserver, here is a page with instructions on how to add Access-Control-Allow-Origin headers
https://ubiq.co/tech-blog/set-access-control-allow-origin-cors-headers-apache/

You have to add the additional header
Access-Control-Allow-Origin beta.ccmixter.org

Hope, that helps! Has been a longer time since I logged in. I did not notice the problems.
kind regards
David

UPDATE:
Found a page descirbing how to add CORS header for node.js:
https://www.section.io/engineering-education/how-to-use-cors-in-nodejs-with-express/