This repository was archived by the owner on Jun 9, 2025. It is now read-only.
fixes allowKick is not defined #91 #107
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
Is there anyone who can review/approve and/or merge this? Thanks. |
Contributor
|
👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is in reference to issue #91
The following is the reason for the error "allowKick is not defined":
In the moderator options that are displayed in the context menu, allowKick is one of them and the template, "message-context-menu.html" references it. However, the allowKick parameter is not passed to the template under "showMessageContextMenu" in the function "_bindSuperuserUIEvents" in the file firechat-ui.js.
To solve this error, allowKick parameter is now passed to the template with a default value of false.