-
Notifications
You must be signed in to change notification settings - Fork 7
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
Cannot enable any plugins as of latest update #17
Comments
I cannot currently reprod this issue. Can you click the little arrow next to the red X on the left and then click on the first blue link in the list, then take a screenshot of the prettified code? |
I cannot install the plugin as of the latest tidal update. I have tried reinstalling tidal and neptune |
@CookieCreations can you hit |
I meant I couldn't install neptune at all. It worked perfectly fine before the update. |
Ah, I was able to install it recently. Perhaps try doing clean install of Tidal first. |
Good to know, thanks so much. Does this happen even if you remove and re-install the plugin? (pasting the url again etc after clicking the trash icon) |
Yup. Still cannot activate the plugin |
One final thing I can think of before deferring to @twnlink If you remove all installed plugins and try installing from scratch does it still happen @CookieCreations? |
You mean installing neptune from scratch? |
No I mean removing the 3 plugins you have installed and then re-adding them. Pretty sure you effectively just did a clean neptune install anyway but if you wanna try it worth a shot if the above doesn't work. Otherwise @twnlink will need to figure out what's throwing on plugins being enabled. |
As a sidenote Inrixia/neptune-plugins#18 still persists |
Great. I'll see if that fixes it on my end and then go to resolve the other issue. Thanks for the help |
I just installed Neptune on the latest version of tidal and no plugins are able to be enabled with the following error:
I cant look into what was causing #16 and Inrixia/neptune-plugins#18 until this is resolved.
The text was updated successfully, but these errors were encountered: