Ticket #355 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

playrestriction is set

Reported by: Michiel.Schok Owned by:
Priority: major Milestone: MediaMosa 2.2
Component: Core Version:
Keywords: Cc:
MoSCoW: none Estimated time after impact analysis:
Related to project: none Tested: yes
Accepted: yes Estimated Hours: 0

Description

I'm not sure why, but every upload through SURFmedia to Core 2.2 acc has playrestrictions set. In the xmlresponse I see:

<play_restriction_start>1999-11-29 23:00:00</play_restriction_start>
<play_restriction_end>1999-11-29 23:00:00</play_restriction_end>

e.g. on asset W1MCPIRmHlIpLsiAMerRNmdP

I cannot imagine SURFmedia sets those fields, but I can't rule it out. I will try to do some research on the SURFmedia side.

Change History

Changed 3 years ago by robert

This problem has been fixed, see #354 (bit related, although not clear its these fields, but they are).

I accidentally pulled play_restriction_* fields through the timezone converter.

Is fixed, will be in 2.2.1 (planned for Monday, Sep. 13th).

Changed 3 years ago by robert

  • status changed from new to closed
  • resolution set to fixed

Changed 3 years ago by Michiel.Schok

OK, in the mean time found out they got the wrong setting during an
/asset/{asset_id} [POST] call.

Wait till monday.

Changed 3 years ago by Michiel.Schok

  • tested changed from no to yes
  • accepted changed from no to yes

And indeed: it is fixed.

Note: See TracTickets for help on using tickets.