-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XML bulk upload - incorrect start/stop time interpretation #193
Comments
While resetting all of the dates manually in the KMC I noticed an incorrect behavior. Say you have Which is valid. Now you want to change to current times When you submit, you get an error saying incorrect dates. I seems the clear flag leaves the old date in the database and the security check flags the problem as time inversion. |
Hi Henry, I am able to reproduce your first issue. May the source be with you, Jess Portnoy Watch the video recordings from Kaltura Connect 2014, and pre-register for 2015 - http://connect.kaltura.com/ On Sat, 12 Jul 2014, HeneryH wrote:
|
See update above |
Hi Henry, Sorry but not seeing your update..? |
One of those bad xml uploads you could reproduce... While resetting all of the dates manually in the KMC I noticed an incorrect behavior. Say you have an entry with times: Now you want to change to current times When you submit, you get an error saying incorrect dates. I seems the clear flag leaves the old date in the database and the security check flags the problem as time inversion. |
Hi Henry, Seeing how this is Core issue, I opened it here: Please keep track there and thank you for bringing this to my attention, |
I just uploaded 20 videos using the bulk xml uploader. On all of my entries I set
but many of them are getting incorrectly interpreted as 1963.
Can someone try a test by downloading the sample xml uploader file (by going to the menu area for uploading you can get a copy of the xml template). There are a few sample videos Kaltura has for download in the template. Can you change the times to above and see if they work OK?
The text was updated successfully, but these errors were encountered: