Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: heisenberg on July 26, 2014, 02:00:52 am

Title: UI bug when starting/stopping server or AutoDJ
Post by: heisenberg on July 26, 2014, 02:00:52 am
Pretty annoying bug, and I finally got time to report it. The server and AutoDJ controls are not refreshed when server is started or stopped.

Steps to reproduce:
1. Log in as client. Let's say that server is stopped.
2. Click Start on the left.
3. Centova says: "Stream started successfully." - that's OK. But on the left there is still Start link, as the server is still stopped - that should be changed to Stop/Reload/Admin.
4. The AutoDJ controls (start/stop/next) also do not appear.
5. A workaround is to refresh the page or navigate to some other page in the control panel - after that the controls become as they should be.

Probably Centova should set some sort of timer which updates controls which correspond to the present server state.

The first picture shows the issue: the server is started, the station is online, but the controls on the left are not updated.

The second picture is after the page is refreshed: the controls are now as they should be.
Title: Re: UI bug when starting/stopping server or AutoDJ
Post by: heisenberg on July 23, 2015, 03:11:57 am
The bug is still there...
Title: Re: UI bug when starting/stopping server or AutoDJ
Post by: Dennis Fallon on July 23, 2015, 08:01:36 am
After you click on STOP (or START) it comes back with with the screen you have shown.

Under Status Change if you click on RETURN, it does update the status of Auto DJ or the stream.
Title: Re: UI bug when starting/stopping server or AutoDJ
Post by: Alexiu on July 23, 2015, 11:42:58 am
Steve detailed this a bit here: http://forums.centova.com/index.php?topic=1742.msg4271#msg4271
Title: Re: UI bug when starting/stopping server or AutoDJ
Post by: heisenberg on July 27, 2015, 02:26:19 am
AJAX is the best solution here. Or simpler solution, just show Start button after Stop was clicked (and vice versa) regardless of the actual server state.

As it works now, it's not acceptable. Buttons state do not reflect actual server state. This is confusing and counter intuitive for users (and for me, too).

I don't understand why Steve says it's not a bug... We can start a poll and prove him wrong :)