New install version 5 after using version 4

[elstaci]

First: I believe this is a much better and useful and simpler version than version 4. especially since you can use it on the a Web Browser.

I was having some issues with Version 4 KODI NPVR Addon. Martin finally helped solve that issue which turned out to be a corrupted NPVR 'Bin' folder.

So Martin recommended to download Version 5 which doesn't use that specific folder. So I did and installed it. This is what happened:

When I installed Version 5 while still having Version 4 installed on my computer:

1) Hijacked my System Tray Icon and replaced with Version 5. So I wasn't able to start Version 4 anymore using the Tray icon.

2) I was able to use Version 4 using my Task bar icon.

3) When I tried to configure Version 5 in Windows, it came up with Version 4 instead. So I was unable to configure Version 5.

4) Sub showed me what to do to resolve that error when I was being helped with Version 4 Thread. He said to uninstall Version 4 but first copy NPVR.DB3 file to Version 5. Uninstalled Version 4 and ran Version 5 installer. Installed without any issues. I did make a copy of my NPVR Data folder in Windows Public Folder. Also created a Restore point.

5) Everything now was coming up to Version 5. I inputted the generic Log in information (admin/password). Log in and was able to configure Version 5.

6) When I got to the "ACCESS" part of the Settings to change my Password and Log in name. I had some issues. I kept getting "failed log in - Incorrect password (original password "password"). At first I thought it was because maybe I changed the Log on name to a personal name rather than "admin". Changed it back to "admin" and still was getting incorrect password. But when I closed the browser again and restarted it. I found out that it finally did change my password to the new password but with the default log on name - admin. So I went back to Settings in the Web App and click again on "ACCESS" and changed the Log On name to the personal name I wanted. Received no message that it was successful. Nothing at all. But when I logged out and logged back on, the default was finally changed to the proper Log on information I wanted.

7) When I started the Desktop App and clicked on "Live TV" and the channel was a channel I couldn't receive, it basically froze with the spinning wheel. Needed to open Task Manager and close out NPVR.  I then restarted the Desktop app but made sure it would start a channel that I know is working and it worked normally. No issues.

So I have a few suggestion from my first experience with Version 5:

1)When Version 5 installer starts its installation process, it should first uninstall the previous version installed on the computer. In this case it should have automatically uninstalled Version 4 but saved the data folder. Thus preventing the previous Version from running on Version 5.

2) The Version 5 installer should automatically copy NVPR.db3 file from the previous version to the new version.

3) ACCESS in Setting needs to have more work done it.

4) Desktop APP should have a timer when trying to connect to Live TV in case it tries to start a Channel that isn't working.

5) The Installer should automatically create a Restore point in Windows if it doesn't do it now.

6)What happens if you forgot your Log on information? How can you reset the Log on back to "Default". Which is something similar that happened when I tried to change my log on information in ACCESS in Settings.

But that is mine first impressions of Version 5.

In my opinion is far superior than Version 4 once the BETA bugs have been resolved.

Thanks Subs and Martin for your help in Version 4 and previous version of NPVR in the past.

[sub]

3) ACCESS in Setting needs to have more work done it.

Like what?

6)What happens if you forgot your Log on information? How can you reset the Log on back to "Default". Which is something similar that happened when I tried to change my log on information in ACCESS in Settings.

You can reset it by editing config.xml. I do not intend to provide any reset feature in the GUI (since it does not have your email address or other identifying information that can be used to reset it safely).

[mvallevand]

Pretty much from the first time I touched initial pre-release versions of NextPVR with the access screen I have had problem problems with saving passwords and Firefox. While it likely is a Firefox issue, given that you won't be able to stop users from clicking save password or from using Firefox, it would be nice if this was improved.

Martin

[elstaci]

Well for starters:

1) It will be nice to be able to see the password you have entered to make sure you haven't made any mistakes. This is useful when a User inputs a very long or complicated password.
 
2) When the Log on information has been entered and it is accepted, In my case, I had no information the log on info was accepted or not. Even after clicking to accept the Log on data several times. Nothing happened.

3) In my case, When I inputted the new Log on data - Log on name & password - the very first time, It gave me a failure notice that the original password was wrong. Even though I inputted the default password several times. Never let me know that the password was actually accepted until I restarted the Web app and log on with the new password.

4) Since you don't want to add a "Reset Log-on" then you should have a button that when you click on it will give instructions on how to reset the Log on to default or something else. I believe the majority of Users wouldn't know that you have to enter the Config.xml file to do that or even know where to find the Config.xml file.

This is what I meant that Access needs more work. just my first experience and not sure if this happens with other Users or not. It may just be on my particular computer setup.

[sub]

1) It will be nice to be able to see the password you have entered to make sure you haven't made any mistakes. This is useful when a User inputs a very long or complicated password.

The application doesn't know what your password is, so can't show it to you. It only knows a big long random number derived from your password. This is a very common, and safer approach to dealing with passwords. It is the same reason most applications cannot show you your password.
 

2) When the Log on information has been entered and it is accepted, In my case, I had no information the log on info was accepted or not. Even after clicking to accept the Log on data several times. Nothing happened.

3) In my case, When I inputted the new Log on data - Log on name & password - the very first time, It gave me a failure notice that the original password was wrong. Even though I inputted the default password several times. Never let me know that the password was actually accepted until I restarted the Web app and log on with the new password.

Are you using firefox as your browser? As referred to above, we've had server reports of Firefox being overzealous with trying to populate password fields (even though we tell it not to) with remembered passwords (and this ends up screwing things up, because it sets the pin to the password). I'll take another look for other work arounds to stop this happening.

In general, when you click 'update login' it should tell you if the password is wrong, or if the new passwords don't match.

4) Since you don't want to add a "Reset Log-on" then you should have a button that when you click on it will give instructions on how to reset the Log on to default or something else. I believe the majority of Users wouldn't know that you have to enter the Config.xml file to do that or even know where to find the Config.xml file.

I'll add a link to login screen, to tell the user how to reset their password by editing config.xml.

[mvallevand]

I don't think he means your saved browser login information I think he meant the password we enter on login.html and change via Access. Often on other apps these fields do have the "eye" we can click which does allow users to view hidden fields.

If your are reviewing this note to include the SD password since it also gets involved in the config.xml firefox browser mess up.

Martin

[sub]

1) It will be nice to be able to see the password you have entered to make sure you haven't made any mistakes. This is useful when a User inputs a very long or complicated password.

I've created a new wiki page to describe the steps. I'll add a link to this on the login page.

https://github.com/sub3/NextPVR/wiki/Reset-Password

[sub]

Often on other apps these fields do have the "eye" we can click which does allow users to view hidden fields.

Some apps do. It's not common though. Best practice is for companies to not even store the users password (or credit card numbers etc), then this type of info not going to be included in any leak that may happen.

Realistically, this wouldn't be an option to implement unless the web server was running over https etc, and given we're a free app, and the way certs work, it's not practical for me to provide tls certs, so for the foreseeable future the application will run as http, and continue to do what it has to to protect the passwords etc.

[elstaci]

Yes, you are correct. I am using Firefox. But I have it configured in Firefox settings not to save any Log-on info or fill any forms or Log-in screens. I don't believe it is very safe or secure for a browser to save sensitive data to fill out online forms or screens. I use Roboform instead which doesn't automatically fill in a form until you click to do so. Roboform's data folder is on another HDD in my computer.

As for the Password, As long as the Users can copy and paste the password on the Log-In or Access screens then it is no problem. This would be the same as seeing the password if it is correct or not.

[sub]

As for the Password, As long as the Users can copy and paste the password on the Log-In or Access screens then it is no problem. This would be the same as seeing the password if it is correct or not.

You can paste to that screen - you can't copy from these fields, because the password is not there. As explained, we don't know what your password is, so it's there on that page for you to copy from.