[ 
https://issues.apache.org/jira/browse/ROL-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-851.
----------------------------

    Resolution: Not a Problem

I believe MediaCast URL refers to today's per-entry Enclosure URL (we don't 
appear have the former anymore in Roller, this bug report is from 2005).  
Enclosure URL can be obtained and used in templates as described in our 
Template guide.

> MediaCast:  Include Logic to Display MediaCast URL, If Present, in Weblog 
> Display Pages 
> ----------------------------------------------------------------------------------------
>
>                 Key: ROL-851
>                 URL: https://issues.apache.org/jira/browse/ROL-851
>             Project: Apache Roller
>          Issue Type: New Feature
>          Components: Media files / uploads
>    Affects Versions: 1.3
>         Environment: All
>            Reporter: Greg Hamer
>            Assignee: Roller Unassigned
>
> A MediaCast URL value can be specified for each weblog (since Roller 1.1).
> Though MediaCast URL values are entered by weblog users, currently none of 
> the themes include logic to display the MediaCast URLs (if a MediaCast URL is 
> present). Also no Velocimacro is provided for display of MediaCast URLs.
> From a usability perspective, the implication of the current design is 
> highlighted by the current draft of UserGuide20 which, under section [3.2] 
> Podcasting with Roller, says:
>   -- Create a new Roller Weblog entry via Create & Edit:New Entry describing 
> your new Podcast. You might want to provide a link to it so that those 
> without a Podcast client can click to download it directly.
> These User Guide instructions suggest the user should enter the MediaCast URL 
> twice: first in the MediaCast URL field, and second as a link in the body of 
> their weblog entry. In addition to being repetitious, this opens the 
> possibility of a disparity between the two values (which can be problematic).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to