#34: Ability to add videos from other sites
----------------------------------------+-----------------------------------
Reporter: and | Owner:
Type: feature | Status: new
Priority: critical | Milestone: 4.5.2
Component: PlumiVideoProduct | Severity: New Ticket
Resolution: | Keywords:
Who will test this: And |
----------------------------------------+-----------------------------------
Comment (by sam):
OK, an number of issues, hopefully minor, prevented this from being
deployed today:
1. /latestvideos - this view fine on my local Plumi both with and without
the em.skin applied; frustratingly, this is not the case on staging, as it
still omits external videos. At this point we don't know why.
2. Ditto for: "Other videos by this author listing - video view pages
http://staging.engagemedia.org:9080/Members/AIPP/videos/Our-Forest-Our-
Life-English/view".. I strongly suspect this to be fixed when 1 is fixed.
3. The default view for an external video is fairly plain and doesn't
match the appearance of the uploaded video view. It uses virtually the
same template as uploaded videos, but I believe Diazo is not detecting
that and applying anything to it. That should be easy to fix for someone
that knows Diazo well. Alternatively, I thought about trying to use the
uploaded videos 'video_view' (instead of the one I created:
'external_video_view') .. however that template needs a real uploaded file
otherwise it breaks. Possibly though it could be modified to work for both
- I haven't investigated how hard that would be.
4. Some validation errors don't create an 'Error:' box. Currently, the
publish form needs that error box to detect that the form has been posted
once and so to hide the big 'Upload' and 'Paste Link' buttons and show the
form instead when the page loads. I've fixed three of these but apparently
adding too much text to the summary creates an error that doesn't trigger
the error box (there is just a red outline around the relevant field). Two
possible resolutions: (1) fix the fields with non-standard validation
behaviours, or (2) find a more robust way of letting javascript know the
form has errors (eg. render something hidden) .. or both ideally.
5. Wokflow - the PlumiVideo workflow isn't being applied even though
PlumeExternalVideo implements the IPlumiVideo interface. IN particular,
the external video starts off in the 'private' state No ideas why as yet.
There is no simple workflow.xml in the profile. However, considering parts
of the PlumiVideo workflow involve processing, it might just be better to
use a variation of Plone simple publishing workflow, modified to make the
initial state 'published'.
4. Duration - even though the video templates omit the duration box if
there is none, it appears Diazo adds a box anyway and you end up with a
dot which is probably a collapsed border. This is likely best fixed at the
Diazo level.
--
Ticket URL: <http://plumi.org/ticket/34#comment:56>
Plumi <http://plumi.org/>
Plumi - FOSS Video Sharing Platform
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
