Bug #39416
closed
Contentelement "MEDIA" don't works with Typ "AUDIO"
100%
Description
Hello TYPO3-Coreteam,
I have created a contentelement MEDIA with type "AUDIO". I have also assigned a MP3-file. After saving this element I saw in the sourcecode of my Frontend a new script SWFobject.js. Just below I can find an ID definition. And in my Contentarea I find a DIV-Tag with the same ID which is defined in the header part.
So...everything seams to be correct, but there is no player an my Frontend. The DIV-Tag has only the id defined, but it has no content. There is also no content if you look at it with help of FireBug.
I have tested the same file on TYPO3 4.6.7. There is no problem with the file. I have updated my system to TYPO3 4.7.2 and the player disappears from the frontend. I changed staticTemplate cssStyledContent to Version 4.6: But the player does not appear.
Stefan
Files
Updated by Stefan Froemken over 11 years ago
There are some people who can confirm this bug. There is a little curious workaround:
Create a new video (type "VIDEO") and instead of inserting a video file insert an audio file. After saving you choose type "AUDIO". The input element for the audio is empty now, but the file will be displayed and is playable in Frontend.
Steffen Ritter has programmed a coreupdate script for flexformvalues: class.tx_coreupdates_mediaflexform.php. In method "performUpdate" he keeps mmFile for sVideo, but moves mmFile for type "AUDIO" to Key "mmAudioFallback".
I have searched the whole TYPO3-Sources for "mmAudioFallback", but there is no other PHP-File handling "mmAudioFallback".
Please have a look into tslib_content_Media.php. As you can see, there is an use of mmFile, but no mmAudioFallback.
So in my kind of view, you have forgotten to insert a condition from where the file comes from.
Stefan
Updated by Björn Pedersen over 11 years ago
The bug must be caused by something else:
Line 98 in typo3/sysext/cms/tslib/content/class.tslib_content_media.php ahs:
$audioFallback = $this->doFlexFormOverlay($conf, 'audioFallback');
doFlexFormOverlay changes the first character to uppercase and then prepends 'mm'.
So this is gives the correct field name.
Updated by Christoph Gerold over 11 years ago
- File 39416.patch 39416.patch added
The bug seems to be caused because SWFObjects takes the field $conf['file'] as input.
But the path to the audio element (Path or URL to fallback audio source (Flash or QuickTime)) is saved to $conf['audioFallback'].
Added a Patch for it.
Updated by Francois Suter over 11 years ago
The problem is indeed that audio files were move to their own properties, but that most renderers haven't been adapted. Only the FLOWPLAYER takes them correctly into account. So I think the correct solution is to adapt the other players to use the "audioFallback" property like the FLOWPAYER does. I'll give it a spin.
Updated by Francois Suter over 11 years ago
- Status changed from New to Accepted
- Assignee set to Francois Suter
- Target version set to 4.7.5
I have a working patch locally for the SWFOBJECT. I need to adapt it to the other renderers before submitting it. And checking if the bug also exists in current master.
Updated by Francois Suter over 11 years ago
I have a working patch locally for the SWFOBJECT. I need to adapt it to the other renderers before submitting it. And checking if the bug also exists in current master.
Updated by Gerrit Code Review over 11 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch TYPO3_4-7 has been pushed to the review server.
It is available at http://review.typo3.org/15412
Updated by Francois Suter over 11 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 3055538c51adb42530065ae94dd73e98c601feb5.
Updated by Sabine Deeken about 11 years ago
strange, this bug seems to be solved, but the Problem exists (still/again?)
TYPO3 6.04, PHP5.4
Audio works with Stefans Workaround (video, then change to audio, with the absolute path; not FAL)
Updated by David Gurk almost 11 years ago
This bug is still there. Testet with TYPO3 CMS v6.1.1. The workaround from Stefan Froemken is still working.
Updated by Werner Trunk about 9 years ago
I can confirm this also in 6.2.9
Insert element switch to audio , insert file path per Element Browser /FAL = no FE output
Insert media video: switch on html 5 > add Video sources for HTML5 > leave path empty > save > switch to audio > insert audio file path per Element Browser /FAL = works.
Result: html 5 audio canvas, not tested with flash.
Updated by Mathias Bolt Lesniak almost 9 years ago
Hi!
I can confirm this appears to be true also in 6.2.14. The status of this issue should not be "Resolved".
- Mathias
Updated by Stefan Neufeind over 8 years ago
- Is Regression set to No
Since the issue here is very old, please file a new one with up-to-date details. You might of course want to link to this one here.
Updated by Mathias Bolt Lesniak over 8 years ago
Updated by Clemens Riccabona over 7 years ago
Stefan Froemken wrote:
There are some people who can confirm this bug. There is a little curious workaround:
Create a new video (type "VIDEO") and instead of inserting a video file insert an audio file. After saving you choose type "AUDIO". The input element for the audio is empty now, but the file will be displayed and is playable in Frontend.
It is just ridiculous, but I have the same problem with the EXACTLY same workaround working on TYPO3 6.2.10 ...
Unbelievable ...
Updated by Clemens Riccabona over 7 years ago
Clemens Riccabona wrote:
Stefan Froemken wrote:
There are some people who can confirm this bug. There is a little curious workaround:
Create a new video (type "VIDEO") and instead of inserting a video file insert an audio file. After saving you choose type "AUDIO". The input element for the audio is empty now, but the file will be displayed and is playable in Frontend.It is just ridiculous, but I have the same problem with the EXACTLY same workaround working on TYPO3 6.2.10 ...
Unbelievable ...
erhm, indeed i meant 6.2.26 ... sry ...
Updated by Riccardo De Contardi over 6 years ago
- Status changed from Resolved to Closed