chef 3745 Posted November 23, 2019 Share Posted November 23, 2019 (edited) Hi it seems when I try to open my plugin web page, alemeda is looking for 'libraryMenu.js' and then throws and error and will not load the configuration page. Edited November 25, 2019 by chef Link to comment Share on other sites More sharing options...
chef 3745 Posted November 25, 2019 Author Share Posted November 25, 2019 (edited) Sorry guys, I'm still experiencing thing weird thing happening when loading plugin UI. This is the Error in chrome. There is nothing in the logs. The plugin loads fine and still works, but the UI is broken. Chrome Error: What is that? What do I need to fix? Many thanks Edited November 25, 2019 by chef Link to comment Share on other sites More sharing options...
speechles 1917 Posted November 25, 2019 Share Posted November 25, 2019 (edited) A cookie was set without the SameSite attribute. That causes all the errors below it looks like. It causes that insecure origins error below. That leads to the 404. Edited November 25, 2019 by speechles Link to comment Share on other sites More sharing options...
chef 3745 Posted November 25, 2019 Author Share Posted November 25, 2019 (edited) A cookie was set without the SameSite attribute. That causes all the errors below it looks like. It causes that insecure origins error below. That leads to the 404. But those address are inside the LAN, all the outside address are TLS. Do you know why my plugin is still looking for 'libraryMenu.js' after the latest update. I can confirm that 'libraryMenu.js' is no longer part of the Emby dashboard UI. I have made sure that I updated all the Nuget libraries, but this seems to be a loading error because somewhere in the Plugin libraries, it still wants 'libraryMenu.js' which isn't there. Edited November 25, 2019 by chef Link to comment Share on other sites More sharing options...
Solution chef 3745 Posted November 25, 2019 Author Solution Share Posted November 25, 2019 (edited) Hey I found it! I'm an idiot! I forgot we were writing node javascript, which means there is a 'define' at the top of the code looking for something that isn't there: 'libraryMenu'. This is fixed. LOL Edited November 25, 2019 by chef Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now