-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Empty block space under Favorites #17648
Comments
@hmhealey Have you seen a report like this before, or do you have thoughts on this? |
Yeah, that might be the case since the draggable-id attribute looks like a real channel ID. If you have access to the DB, you could confirm whether or not a channel with that "s6cbh..." ID exists. Either that or there's an error in the library we use for drag and drop. If that were the case, I'd expect to see an error in the browser's console. |
I wouldn't recommend deleting it since that could leave some orphaned data that could cause other problems, but you could try deleting the row in |
That worked ! Thanks for the help. Not sure exactly what happened but at least it's fixed. |
Glad that helped! Let us know if that comes up again. The new sidebar is definitely more complicated than the old one, so stuff like that one can pop up occasionally, but since that's the first time this particular issue has come up, I don't think there's much to investigate on it for now. We can always reopen this if it reappears though. |
Summary
Since 5.33 or 5.32, I can't remember exactly, an empty block (space ?) appeared underneath my Favorites Channel section. I can move the block around but there is no option to delete it.
Steps to reproduce
Don't know how to reproduce exactly unfortunately. Appeared in 5.33 or 5.32 update. We are currently running the latest version 5.35.1
Expected behavior
No empty space
Observed behavior (that appears unintentional)
Here's a gif that shows what I'm talking about. Appears in MM Desktop client (Mac) and web version. Its fine on Mobile
Possible fixes
No idea unfortunately
The text was updated successfully, but these errors were encountered: