ironmansoftware / universal-dashboard

Build beautiful websites with PowerShell.

Home Page:https://universaldashboard.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

UD3-Beta4 - PSUniversal- Certain actions show across multiple dashboards

dcherry88 opened this issue · comments

Describe the Issue

When multiple dashboards are configured in PSUniversal, some actions will appear on the opposite dashboard page or on both dashboard pages

To Reproduce

Setup two dashboards. I utilized the v3 example dashboard for one.
Chips page - If you click the OnDelete chip, the info pops up on the test page of mine, not the demo page. Even if i shutdown my test page and restart the demo page, it doesn’t work on the demo page.
Modal page - when clicking on the examples to display modal popups, they show properly on the Modal page, but they also show on the page of my test dashboard.

Expected behavior

Action should only occur on the dashboard it is scripted into.

Version Information

Server 2019, IIS
PSUniversal 1.1.1
Utilizing UD 3.0.0-beta4, running process as powershell.exe on both dashboards.

This issue has been mentioned on Ironman Software Forums. There might be relevant details there:

https://forums.universaldashboard.io/t/certain-actions-show-across-multiple-dashboards/2875/3

This issue has been mentioned on Ironman Software Forums. There might be relevant details there:

https://forums.universaldashboard.io/t/certain-actions-show-across-multiple-dashboards/2875/3

I linked it on that thread, you've created a feedback loop!

Followup on this, I feel like the issue is the same underlying problem:

When clicking a page link on the side navigation of the demo site, i'm noticing that it's also trying to load that page on the tab for my test site.

Example: If I go to the appbar page on my demo site, URL is this 'portal.domain.com/demo/appbar'
If I then go to the tab where my test site is, at the root 'portal.domain.com/' it will now be on a Page Not Found with the url as 'portal.domain.com/appbar'

i can confirm , this bug also effects antd lib
video of the bug

Looking into this today

This has been resolved in PSU1.2. The problem was that the websocket was broadcasting to all connected clients rather than a specific client.