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

Second argument for the command "permission" result in an error + logs edits update #12

Closed
Salvi0 opened this issue Sep 29, 2021 · 8 comments

Comments

@Salvi0
Copy link

Salvi0 commented Sep 29, 2021

Same as my other report, i was testing the bot when i suddenly found out that using the command '+permission commandName remove/rmv userID result in an error thta you can found below.

proof

@ThePhoDit
Copy link
Owner

That's not the complete error, there should be a bunch more of lines above.
Can you please screenshot everything?

@Salvi0
Copy link
Author

Salvi0 commented Sep 29, 2021

yes one moment please

@Salvi0
Copy link
Author

Salvi0 commented Sep 29, 2021

that's everything i was able to get.
proof

@Salvi0
Copy link
Author

Salvi0 commented Sep 29, 2021

another thing i noticed is a critical severity problem during the initial startup of the bot.

proof

and this should be the faulty package (probably unrelated to the problem i reported above)

proof

@Salvi0 Salvi0 changed the title Second argument for the command "permission" result in an error. Second argument for the command "permission" result in an error + logs edits update Sep 30, 2021
@Salvi0
Copy link
Author

Salvi0 commented Sep 30, 2021

When the edit command is used on an already edited message, on the logs the original content should also been updated or meaby stacked with the first one. Meaby make it show the last 5 edits and then only show the new ones in a chronological order.

proof

@Salvi0
Copy link
Author

Salvi0 commented Sep 30, 2021

I found the cause of the problem. When the command is used with an alias instead of the actual command cause such problem. It seems to apply only to the 'remove' parameter. Using the same exact format but with the add parameter even with aliases works just fine. At then end you will not be able to remove a permission from an alias, so you are forced to remove it manually from mongodb.

Steps to reproduce.

+permission command_alias add user/role/server_id

+permission command_alias remove user/role/server_id

@ThePhoDit
Copy link
Owner

I will have a look tomorrow.

@ThePhoDit
Copy link
Owner

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

No branches or pull requests

2 participants