search

pnews88 / ispyconnect

Automatically exported from code.google.com/p/ispyconnect
0 stars 0 forks source link

Alpha web interface: duplicate recordings listed #44

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Allow any camera to record on motion
2. Check web interface.  Multiple copies of each recording are listed in File 
Manager.  Some recordings show twice, some show up three times.  In screenshot 
that I provided below, there are actually only 4 recordings on the server.

Screenshot:  http://imgur.com/9XwJd

What is the expected output? What do you see instead?

One recording per event.  Instead, multiple recordings listed.

What version of the product are you using? On what operating system?

Upgraded to 4.6.30 today.  Also has the same issue with 4.6.0.0.  Running 
Windows 8 Release Preview 64-bit on both the server and remote computer.  
Remote computer is viewing the website with Chrome 22.0.1229.94 m

Please provide any additional information below.

Nothing else.  I realize its alpha, just want to provide useful feedback.  
Please let me know if there's anything else that would help.

Original issue reported on code.google.com by ptwea...@gmail.com on 24 Oct 2012 at 3:58

GoogleCodeExporter commented 9 years ago

Original comment by ad...@developerinabox.com on 25 Oct 2012 at 6:20

GoogleCodeExporter commented 9 years ago 
Should be fixed in latest update (old duplicates will still be there but 
shouldn't get new ones)

Original comment by ad...@developerinabox.com on 26 Oct 2012 at 2:00

GoogleCodeExporter commented 9 years ago 
Just verified that it's fixed.  Thanks!

Original comment by ptwea...@gmail.com on 26 Oct 2012 at 2:12

GoogleCodeExporter commented 9 years ago 
Well, I haven't changed anything on the viewer or server side since my last 
comment, but it appears that the issue is back.

Original comment by ptwea...@gmail.com on 1 Nov 2012 at 3:07

GoogleCodeExporter commented 9 years ago 
I just cleared the browser cache and now it's working again.  I'm not sure how 
the incorrect behavior came back after it appeared to be fixed.

I'll keep monitoring it and update this issue later.

Original comment by ptwea...@gmail.com on 1 Nov 2012 at 3:44