Latest Tickets Added - with descriptions (82 matches)
Results (1 - 20 of 82)
| Ticket | Summary | Status | Type | Priority | Milestone | Severity | Created |
|---|---|---|---|---|---|---|---|
| #608 | comments rss returns an insufficient priviledges error | new | defect | critical | 4.7 | New Ticket | 2 years |
| Description |
http://testing.plumi.org/recent_comments/RSS can only be viewed if you are logged in. Should be available to anyone. |
||||||
| #726 | Facebook Embed - Video NOT Playable | new | defect | critical | 4.5.1 | New Ticket | 15 months |
| Description |
When user pastes in EM video/view URL the video is NOT playable in the facebook page as it used to be, and as per Vimeo, Youtube etc. ALSO Videos Controls Don't Work (mediaelement.js) http://EngageMedia.org is using mediaelement.js via Plone / Plumi ( http://plumi.org). When a user posts a video to Facebook, they can click play to activate the video for the first time. However the controls don't work (except for the fullscreen button). The user cannot click/effect the play/pause button, the scrub bar, or the volume control. Tested using Mac OS X 10.6.8 / Safari 5.1.5 Using e.g. this video: https://www.engagemedia.org/Members/Novaruth/videos/filastine_colony_collapse.mp4/view Follow this up, including ticket on mediaelement.js Github: https://github.com/johndyer/mediaelement/issues/445 |
||||||
| #775 | RSS2 Vodcast Issues | new | defect | major | 4.7 | New Ticket | 11 months |
| Description |
I tested the RSS2 latest videos feeds in Miro. feed:https://www.engagemedia.org/latestvideos/RSS2
However, the RSS2 feeds *do* work in Miro, and I can download videos successfully, unlike before :) |
||||||
| #825 | Author Page Styling & Template Fixes | reopened | defect | blocker | 4.6 | Work in Progress | 8 months |
| Description |
Still remaining things:
GO OVER THIS AGAIN. (FIXED DELIVERABLE) |
||||||
| #865 | Part of User Groups Prefs Cut Off | new | defect | trivial | 4.7 | New Ticket | 7 months |
| Description |
There is a scrollbar and a bit of "Remove User" is cut off by the content area not being wide enough. Would be much neater to somehow make this content fit within the content area in the new Plumi/EM skin. |
||||||
| #922 | buildout error | new | defect | major | 4.5.1 | New Ticket | 4 weeks |
| Description |
Installing plone. Error: There is a version conflict. We already have: zdaemon 2.0.7 but ZODB 4.0.0b2 requires 'zdaemon>=4.0.0a1'. * Overwriting versions.cfg * * Overwriting versions.cfg * |
||||||
| #925 | buildout fails | new | defect | major | New Ticket | 4 days | |
| Description |
Following the included INSTALL file instructions , the installation fails :
While:
Error: Error downloading extends for URL http://download.zope.org/zopetoolkit/index/1.0.7/zopeapp-versions.cfg: [Errno socket error] [Errno 110] connection timed out |
||||||
| #362 | Allow mixed content languages (?) | new | enhancement | major | 4.7 | -- | 3 years |
| Description |
LinguaPlone? has been following the "mixed languages sites are evil" mantra. But most Plumi sites are unlikely to have fully translated content in all supported languages at all times. plumi.app currently disables the i18naware catalog monkey patch that LinguaPlone? applies by default, so the catalog always returns all content objects regardless of language. A better behavior for Plumi sites would be to display only the selected language version for the objects that have such a translation, or the original (canonical) version for the untranslated objects. In order to support that we would have to write a different monkey patch for the catalog. I am very concerned however with the side effects such a patch could have in terms of caching, performance, inconsistencies with other components. So I'm not entirely convinced that it's a good idea. Comments are very welcome. |
||||||
| #464 | REVAMPED TEMPLATE - Author / Profile Page | reopened | enhancement | major | 4.7 | New Ticket | 3 years |
| Description |
This ticket can be updated after making some more firm decisions.
Look at possibilities for this including:
these are notes from other tickets - worth looking at: The p4a portfolio product may provide us with enhanced member profile functionality and social networking. This product needs installation, investigation, testing and an assessment of whether it should be included and what, if any, modifications it would require. Contact Tab - Enhance the author page so that the option to contact an author is a separate tab. Once more ajax comes in for plone this could really work quite nicely. |
||||||
| #561 | Copyright footer lists all videos as 2009 - should correspond to date of release | new | enhancement | minor | 4.7 | New Ticket | 2 years |
| Description |
the footer lists all submitted videos in this format, regardless of when the video was submitted. the copyright should either list the current year, or the year submitted. (ideally the latter) Copyright 2007, by the contributing author. Cite/attribute Resource. balibo. (2009, November 12). Balibo The Movie - Trailer. Retrieved November 17, 2009, from EngageMedia Web site: http://www.engagemedia.org/Members/balibo/videos/BALIBO_PRESSPACK_HD720.mov. This work is licensed under a Creative Commons License. Updated by Mike Muzurakis This is a collentlicensing/plumi issue. Plumi just gets the footer from collectivelicensing and displays it. It's easy to change the prefix in collective licensing (like change Copyright 2009 to Copyright 2010 or to 2007-2010 or something), but collectivelicensing is unaware of the video's production date. Putting the production date there, means that we have to override the contentlicensing view and provide our own. It can be done, but it's not trivial and should be moved to another milestone. |
||||||
| #625 | Unit and functional tests for plumi.app & plumi.content | new | enhancement | minor | 4.6 | New Ticket | 2 years |
| #784 | Expose ability to change iframe embed sizes | new | enhancement | major | 4.7 | New Ticket | 10 months |
| Description |
Since last week's redesign sprint you can add a width parameter to the view. That means that if you take the iframe code and change the width, you should also add a ?width=300 (or whatever) to the end of the video link. E.g.: https://www.engagemedia.org/Members/dayakvoices/videos/dayak_modang.m4v/embed_view?width=500 The video link inside the embed code that is. In the feature we can easily support multiple embed sizes like youtube, but there was not enough time to expose the feature in the UI and test it during the sprint. |
||||||
| #812 | Member Folder Design Changes | reopened | enhancement | blocker | 4.6 | Feedback Required | 8 months |
| Description |
E.g. https://www.engagemedia.org/Members/anna/ What remains to do here seems to be:
These changes should be updated in EM skin also. (FIXED DELIVERABLE) Ticket moved from: https://redmine.engagemedia.org/issues/1616 |
||||||
| #831 | Remove Large Magnifying Glass Icon in Search Bar on Firefox | reopened | enhancement | minor | 4.6 | New Ticket | 8 months |
| Description |
This appears in the search bar in the header on FF. It is not aligned well with "Search Site" text, and in fact we'd prefer to remove it altogether. https://redmine.engagemedia.org/attachments/2671/firefox-mag1.png Moved from here: https://redmine.engagemedia.org/issues/3231 |
||||||
| #833 | Re do banner and make tagline font larger | new | enhancement | minor | 4.7 | New Ticket | 8 months |
| Description |
The tagline (author name, date published, history) on any page Eg https://www.engagemedia.org/Members/ricoloco/news/papuan-voices-bakar-batu Not too much larger, but a little bit to make it more readable. |
||||||
| #849 | Ability to Feature Collections | new | enhancement | major | 4.7 | New Ticket | 8 months |
| Description |
For use in the featured sections on the front page. NOTE: Andrew pages don't have images associated with them, so probably can't feature those in the same way. Moved from: https://redmine.engagemedia.org/issues/3326 |
||||||
| #856 | Add a Contact This Member Link to Video View Page | new | enhancement | major | 4.6 | New Ticket | 8 months |
| Description |
How to do this should be more obvious to the user. We need to think about where to put it though. Yiannis, any ideas? |
||||||
| #9 | Torrent Tracker Page | new | feature | minor | 4.9 | -- | 6 years |
| Description |
A page listing all the torrents on the site with the no. of seeders, downloaders, all with a nice skin. One example might be < http://indytorrents.org/> in terms of metadata, but it is a tad ugly. |
||||||
| #20 | Productions Content Item | new | feature | critical | 4.9 | -- | 6 years |
| Description |
Develop a content item for productions improve collaborative tools on EM. This will be a collaborative tool to allow producers to announce new productions. Members could add a Production, then other members could contact that Member through the Production/view template Contact form to get involved and collaborate. This can also be a fundraising for those upcoming productions. Investigate the use of the flash widget ChipIn?? for integration or simply inspiration for a fundraising tool for filmmakers to make new productions. A user could add a "Production" and then extend that object by linking to their account on ChipIn?? or something similar, which would then display their fundraising goal and how much further they have to reach it next to the description of what their production is about. Also good for people to promote the productions they are involved in. Should be listed in Member Workspace i.e. "My Productions" Fields
We could add additional info like location, required format, submissions due by etc. but i suggest we build a first version that is really simple and get it out there and build upon that. Further development could also allow people to create their own submission form on the site. ie so people could submit their films through a Plumi site. |
||||||
| #34 | Ability to add videos from other sites | new | feature | blocker | 4.6 | Ready for Testing | 6 years |
| Description |
Create the ability to take videos from Vimeo, YouTube?, blip.tv, etc and add them to a Plumi site. This will enable broader sharing of content. Videomakers will not have to re-upload their video to another site (the Plumi site) if they have already done so elsewhere. It will also allow site editors to curate content from other sites into a Plumi site.
(FIXED DELIVERABLE) |
||||||
