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

Can't move widgets in dashboard layout in 2.20 #577

Closed
GeoffNT opened this issue Apr 5, 2020 · 6 comments
Closed

Can't move widgets in dashboard layout in 2.20 #577

GeoffNT opened this issue Apr 5, 2020 · 6 comments

Comments

@GeoffNT
Copy link

GeoffNT commented Apr 5, 2020

I've just updated to 2.20 and now can't move or adjust the size of any widgets in the dashboard layout page. I can lock and unlock the widget but nothing else. Also the widget size in the dashboard layout edit page is not the same as it is displaying on the actual dashboard. This is using Chrome on Windows 10 PC.

@dceejay
Copy link
Member

dceejay commented Apr 5, 2020

have you re-flushed your client side browser cache ?
Is there anything in your browser client console log ?

The size is not meant to be the same - it is a representation of what you have on the screen at a smaller scale to allow more to fit and to allow dragging.

@GeoffNT
Copy link
Author

GeoffNT commented Apr 5, 2020

I'm clearing the cache as we speak but this is what I mean by the display issue. The ui node shows this item at 6x1 and it displays on the dashboard ui as 6x1 but in the dashboard layout page it shows as 3x1 and I can't move or stretch it. (EDIT this is a new widgets created on 2.20)

EDIT2. Cache now cleared and has made a difference in that it would let me drag the new widget size to 6x1. I saved it and deployed but when I go back in to dashboard layout, it has reverted to 3x1 there. Happens with existing widgets too - a lot of them are reverting to 3x1 on the dashboard layout page, but still displaying correctly on the actual dashboard UI.

Dash_UI

@GeoffNT
Copy link
Author

GeoffNT commented Apr 25, 2020

2.21.0 seems to have fixed this. Thanks very much.

@GeoffNT GeoffNT closed this as completed Apr 25, 2020
@jensrossbach
Copy link

I still have this issue with 2.26.1.

@dceejay
Copy link
Member

dceejay commented Jan 3, 2021

This issue was closed last April. Please open a new one - filling in the required info so that we can recreate it.

@mohdxb
Copy link

mohdxb commented Oct 18, 2023

I still have this issue with 2.26.1.

I fixed this issue by disabling the cache from the browser.

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

4 participants