-
Notifications
You must be signed in to change notification settings - Fork 2
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 run on ASF 6.0.0.3 #13
Comments
Just released V2.8.3 of the plugin which works with ASF 6.0.0.3 |
got it |
It seems that there are still related errors, I am not sure if it will affect the plugin's functionality
|
After logging in
|
The ASFEnhance error should not be an issue. Are you using something other than ASF-generic? |
I still get the same error after I have cleared all files and redownloaded and configured them (Only BoosterManager Installed) config:
|
The This newest version has only been tested with ASF-generic, and so it's very possible to be broken with other variants of ASF. If that's the case, then I don't have a fix for this right now, but will look into addressing this within a few days. |
I'm using ASF-linux-x64 |
I'm using asf-win-x64 and getting the same error. i don't mind waiting for a fix, just wanted to say thanks for keeping this project going! i appreciate you! |
That specific issue reported above you can fix by using |
Fixed this error and a few others I found. I'll post a new release tomorrow. In the meantime if you want to test the current build you can download it here: BoosterManager V2.8.4 |
New release is out which fixes this, V2.8.4. It's possible there's other errors I didn't find though, but I'm still closing this as the original problem this issue was opened for is certainly fixed. Feel free to open a new one if there's any other problems. |
just wondering incase of more issues, can you just copy the config and plugins directorys from a linux-x64 install to a generic one? |
Yes |
It seems that this plugin is not working properly after the ASF update
The text was updated successfully, but these errors were encountered: