BETA: New Home Page, Settings re-org, and On Boarding

[maddox]

@Jackamus

The latest update ( 2023.09.29.1842) tries to setup / onboarding as if it's never been setup before after a reboot. I refreshed the page, and it went away.

Resolved in the latest pre-release:

DVR Pre-Release Notes

v2023.09.29.1924 • FIXED: Wizard would show up if loading the web admin in the middle of booting • FIXED: Some path names were overflowing the UI

[SomeOldGuy]

Version 2023.09.29.1924
If I use MS Edge on a Pixel 6 Pro to go to the remembered URL
http://[IP]:8089/admin/settings
I get a flickering page with various links intermittently flickering.

[chDVRuser]

@maddox

Sorry guys, time to change those bookmarks back

Not so fast
I set mine back to /dvr/settings and now I'm getting this on v2023.09.29.1924

A Javascript error has occurred!

Please refresh the browser after reporting this issue on Channels Community or to [email protected].
The operation is insecure.
Ti1</N82/push/<@http://192.168.1.4:8489/node_modules/history/cjs/history.min.js:1
confirmTransitionTo@http://192.168.1.4:8489/node_modules/history/cjs/history.min.js:1
push@http://192.168.1.4:8489/node_modules/history/cjs/history.min.js:1
tJ/<@http://192.168.1.4:8489/admin/components/Settings.jsx:43
h@http://192.168.1.4:8489/node_modules/react-dom/cjs/react-dom.production.min.js:262
b@http://192.168.1.4:8489/node_modules/scheduler/cjs/scheduler.production.min.js:18
Nf@http://192.168.1.4:8489/node_modules/react-dom/cjs/react-dom.production.min.js:122
gg@http://192.168.1.4:8489/node_modules/react-dom/cjs/react-dom.production.min.js:261
Oj@http://192.168.1.4:8489/node_modules/react-dom/cjs/react-dom.production.min.js:261
O@http://192.168.1.4:8489/node_modules/scheduler/cjs/scheduler.production.min.js:16
i71</oO.port1.onmessage@http://192.168.1.4:8489/node_modules/scheduler/cjs/scheduler.production.min.js:12

[maddox]

Working on it.

[maddox]

@kennyb3653

Can you make the home page landing custimizable. I like the home page to load the guide.

There is now a setting to set your default home page for the web admin. This is the page that you will be routed to when you visit the site without a path ie, the first load.

So now, not only can you set it to be Settings again and have the old behavior, but you can set it to anything else you want.

DVR Pre-Release Notes

v2023.09.29.2121 • NEW: Set which page in the web admin that you would like to load by default

[maddox]

This JS error is now resolved:

DVR Pre-Release Notes

v2023.09.29.2150 • FIXED: An infinite redirect happened if you navigated to /admin/settings

[tedfaust]

Thanks for this. Old habits die hard.

[kennyb3653]

Thank you. This is great.

[jasonmcroy]

Not sure if I am doing something wrong, but if I go to the general setting section and set the landing page to "Settings" and then go to "IPaddress:8089/admin/home" it still always takes me to the landing page that shows the library consisting of Up Next, Recently Added TV Shows and Recently Added Movies.

It doesn't seem to matter what landing page I set it to in the general settings, it always lands on that page mentioned above.

I am on Version 2023.09.30.0304

[maddox]

That’s because you’re going to that page.

The setting sets where it takes you when you go to the root of the web admin. Just /

[jasonmcroy]

Oh, I get it. I guess I misunderstood how it worked. Thanks!

[Jackamus]

Not sure if this matter but I keep getting Panic logs over and over again. Not sure what is causing the issue.

2023/09/30 08:01:25 [Recovery] 2023/09/30 - 08:01:25 panic recovered:
runtime error: invalid memory address or nil pointer dereference
runtime/panic.go:260 (0x340b46)
runtime/signal_windows.go:257 (0x340b16)
github.com/fancybits/channels-server/dvr/profile.go:155 (0x138c64d)
github.com/fancybits/channels-server/dvr/file.go:1253 (0x138c66d)
github.com/fancybits/channels-server/http_dvr_file.go:199 (0x1a2acd8)
github.com/gin-gonic/[email protected]/context.go:169 (0x19db441)
github.com/fancybits/channels-server/http_dvr_file.go:35 (0x19db372)
github.com/gin-gonic/[email protected]/context.go:169 (0x19c9f23)
github.com/fancybits/channels-server/http.go:301 (0x19c9c17)
github.com/gin-gonic/[email protected]/context.go:169 (0x19c9b8a)
github.com/fancybits/channels-server/http.go:278 (0x19c9b6f)
github.com/gin-gonic/[email protected]/context.go:169 (0x19c9aaa)
github.com/fancybits/channels-server/http.go:270 (0x19c9a8d)
github.com/gin-gonic/[email protected]/context.go:169 (0x19c9787)
github.com/fancybits/channels-server/http.go:244 (0x19c9113)
github.com/gin-gonic/[email protected]/context.go:169 (0x9ba9e1)
github.com/gin-gonic/[email protected]/recovery.go:107 (0x9ba9cc)
github.com/gin-gonic/[email protected]/context.go:169 (0x9b9b46)
github.com/gin-gonic/[email protected]/logger.go:240 (0x9b9b29)
github.com/gin-gonic/[email protected]/context.go:169 (0x144ebf9)
github.com/gin-contrib/[email protected]/sessions.go:65 (0x144ebe5)
github.com/gin-gonic/[email protected]/context.go:169 (0x1448f01)
github.com/gin-contrib/[email protected]/gzip.go:47 (0x1448ed9)
github.com/gin-gonic/[email protected]/context.go:169 (0x1a4d905)
github.com/fancybits/channels-server/http.go:391 (0x1a4d8f1)
github.com/gin-gonic/[email protected]/context.go:169 (0x9b8c4a)
github.com/gin-gonic/[email protected]/gin.go:598 (0x9b88d1)
github.com/gin-gonic/[email protected]/gin.go:554 (0x9b83f1)
net/http/server.go:2942 (0x639dd5)
net/http/server.go:2001 (0x6353a6)
runtime/asm_amd64.s:1598 (0x35ff00)

Logs if helpful: 339b0e63-ff7e-489f-8b5b-1e781cb86d1b

[Flt505]

How about an Option to use the "Old" Settings page.
Some people don't embrace change!!

[slampman]

Not sure if this is related but after the last update (I'm on 2023.09.30.1316) the web console has become really slow. Feels like I am on a really slow 3g connection. My server is an intel NUC i7 with 16GB RAM with an SSD and it is hard wired. The computer I am accessing it on is also hardwired. I just submitted diagnostics if it will help. I am going to try rebooting it when some recordings are done. If that doesn't work I will roll back and let you know if that fixes it.

I just checked my hard wired apply tv clients and they are taking 10 seconds to start playing recorded media. It is usually less than a second.

f6387f11-6d0d-4d89-957f-ddc10660723e
@maddox
update: I rebooted, no change. Console & Playback still dead slow.
I step-rolled back until I found the build that has the issue:
2023.09.29.2216 -> No issue, all playback/console responsiveness OK
2023.09.30.0304 -> slowness, spinning wheel on console, long wait times on ATV to play recorded content.

You will probably see it in my logs but there are a ton of panics. I just submitted again just in case.
ce6d68e0-3358-4646-8c2d-85526ac9f5d4

[TerryD]

I get this screen after every update. On latest pre-release currently.

[tmm1]

The panics were fixed in a later build. Are you able to check the http log or the js console network inspector to see which requests are hanging or slow

[ert]

Haven’t updated because you lost me at “more clicks”. Focus on the app ui and leave the home page alone.

On 2nd thought…. It f you make it more mobile friendly, I’m in

[slampman]

I havent but i can take a look. Its more than the webconsole though. ATV clients are slow to playback anything

@tmm1 I'm not sure if these were overwritten when I rolled back... FYI 192.168.12.20, .21,& .22 are my ATV clients.

channels-dvr-http.log

[tmm1]

Okay can you submit from the ATV then?

[tmm1]

Do speeds go to normal if you turn off embedded Tailscale