Problem/Motivation
MediaFront has 3 preloaded templates: simpleblack, shockplayer, and default. If MediaFront is displayed using Views, the playlist will not display if the user has selected shockplayer of simpleblack as their preset template. When displaying MediaFront in single nodes, the simpleblack, shockplayer, and default templates can be used.
To reproduce this issue, create a View to display a playlist of videos. When editing the MediaFront preset under Presentation Settings, select shockplayer or simpleblack as the template. Once the preset is saved, the Views playlist will be displayed as a spinning wheel.
Proposed resolution
- At this time, one workaround is to select "default" as the template. If you choose "default" as the template, videos are displayed correctly.
- Configuring a customized JQuery UI theme may also resolve this problem.
- Ultimately, all of the templates that come preloaded with MediaFront should display in both single nodes and Views playlists.
Remaining tasks
Changes will need to made to the code so that all preloaded MediaFront templates work in Views playlists and single nodes.
Original report by [lionheart8]
Hi
I just noted when I do not set the template under Presentation Settings to "default", but to "shock player" or "simpleblack", the media does NOT load.
It seems there's some small problem here ...
Some solution there?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | mediafront.jpg | 152.59 KB | lionheart8 |
Comments
Comment #1
BeaPower commentedsame issue...
Comment #2
rwilson0429 commentedSame here. Only the "default" template works. When the "shock player" or "simpleblack" templates are selected, the player shows up but, the gears just continue to spin indefinitely. Clicking on the play button while the gears are spinning gets no results.
Comment #3
travist commentedI am unable to reproduce this issue. Is your drupal setup within a subdirectory? I found an issue recently where this might be related.
Comment #4
rwilson0429 commentedYes, my drupal setup is within a subdirectory (c:\public_html\drupal7) where public_html is set as the web root.
My current setup includes the latest devs of Media 7.x-2.x-dev, Styles 7.x-2.x-dev, and Mediafront 7.x-1.x-dev.
BTW, this will be a fantastic module once all of the kinks are worked out. I have a couple of other issues that I will post under a separate que.
Comment #5
lionheart8 commentedHi
I have not been able to use the other templates whether I have installed Drupal in site.com/drupalsite or in site.com, with MediaFront 7.x-1.2 & after updating to MediaFront 7.x-1.3.
I don't know if this is relevant ... site.com in is in /public_html/site.com/ <=== updated & consequently, mediafront in /public_html/site.com/sites/default/modules/
Regards
Comment #6
travist commentedThis actually may be relevant. I am currently investigating how the player behaves when loaded within a subdirectory. I made a fix yesterday with the templates, but will do some more testing with other functionality later this week and this weekend.
Comment #7
lionheart8 commentedI noted on an EXISTING test site, where I had upgraded from 7.x-1.3 to 7.x-1.x-dev & which ALREADY had some content that the shockplayer & simpleblack templates work as well, BUT only on pages.
In a corresponding view, the media does not load in the media player, though.
So I think there is some big progress, and if this were to be addressed, this problem would be solved.
Regards
Comment #8
gsquirrelI am having similar issues - I upgraded to the newest dev version and that seemed to help with i18n incompatibility issue, but still having trouble.
One video is now playing in chrome but not firefox and I can see lots of not found errors for the template images, it is looking for them in the wrong place.
My sites is on shared drupal install so the path will need to start /sites/sitename.org/modules/mediafront/players etc not sitename.org/var/www/web349/web/drupal_files/modules/mediafront/players/ which is where it is looking for them, i.e. it is taking the server path and trying to put it after the domain name which wont work.
There must be a function that determines the path to use as a base which is not quite right, will try to find it but any clues appreciated.
Comment #9
travist commentedWhen you said you tried the latest DEV, when was this? I have made some changes within the past couple of weeks that I thought fixes some path issues, but you may have already tested those changes. Please let me know when you tried the latest DEV version.
Thanks,
Travis.
Comment #10
lionheart8 commentedHi
Yesterday morning (Berlin local time), 28th September, I used the latest dev I found on the project page for the latest installation. I might be mistaken, but I think it had 26th as the release date.
Anyway, today 29th I used the dev version dated 28th Sept. & can confirm the 2 other templates, i.e. not the default one, work on content pages but not in a related view, where the media does not load.
[The concerned site is located in a folder in the root folder but has its own domain name, i.e. concernedsite.com]
Regards
Comment #11
gsquirrelI meant the 28th sept one - but it might only affect me due to the shared install and different file structure - ideally would be great if there was a setting for base path to module or something like that - maybe it is somewhere in the module code?
Thanks
Comment #12
gsquirrelComment #13
travist commentedDefine "different file structure". Drupal assumes at least a somewhat standard file structure for modules which is why a setting is not necessary, so I am curious if your issue may be that you have your files in a non-standard location.
Comment #14
gsquirrel>My sites is on shared drupal install so the path will need to start /sites/sitename.org/modules/mediafront/players
This is standard for a shared install but I guess for single installation it would be /sites/default/modules/mediafront/players instead, that was what I meant. So my uploaded files are in /sites/sitename.org/files/ too.
Since drupal allows you to set the path for uploaded documents this is normally not an issue but occasionally modules hard code path locations so that they don't work well on shared installs.
For me it does not matter which skin/template i try I get broken images for the player buttons etc.
Thanks for any clues on where these paths might be set.
Comment #15
gsquirrelI think I found something - the file in /files/css/osmplayer/mediafront_osm.css has some definate paths that correspond to my page not found errors - I will try changing the paths in this css file and see what happens. Presumably these paths are generated somehow since they are specific to my site - the problem is they seem to be using server path rather than public url.
Comment #16
gsquirrelTo confirm when I manually changed the paths in that file:
/files/css/osmplayer/mediafront_osm.css
Nearly all the page not found errors go away and the player works. Still in Chrome the "play.png" button does not appear and is looking in wrong directory. Any idea where in the module code these incorrect paths are being generated?
Thanks
Comment #17
naiptol commentedFor me only 'default' template support playlist from view. Other templates work only with single node.
Comment #18
heyay commentedHello,
I am using a free theme named Soft Technology from http://www.drupalove.com/drupal-theme/drupal-7-free-soft-technology-busi.... I have placed this theme in xampp/htdocs/sites/all/themes. Everything works perfect except MediaFront.
When I want to add a media content, the preview works fine, but once i saved and go to the front page to play the content, I only see the gears spinning indefinitely.
Please help, I need this grate module so badly !!
Comment #19
travist commentedheyay,
Please check your site in a browser like Chrome with the Developer Tools enabled. Now, look at the bottom right of the tools and see if there is a red exclamation point icon. If you see this, then it means there is something in your site that may be crashing JavaScript. This is a very common issue where the player just doesn't work. Let me know if this helps.
Travis
Comment #20
ryan.ryan commentedI'm having this same issue actually on one site install but not another. The installs are both at the directory root so I don't think that's an issue. I'm also not getting an javascript errors. Using default template works, but simpleblack and shockplayer cause the video to just spin indefinitely and not load.
Comment #21
enjoylife commentedIf you are displaying MediaFront in a node, then the simpleblack, shockplayer, and default templates are displayed. If you are displaying MediaFront using a View (for playlists), only the default template works.
This is a known issue that hopefully will be resolved in the future.
Comment #22
enjoylife commentedI have marked #1303626: MediaFront Format will not work in Views as a duplicate of this. Of the helpful information from that issue, is the following:
As a recap, in both D6 and D7, shockplayer and simpleblack cannot be used as the selected template when displaying MediaFront in a view. Instead, the user sees a spinning wheel. If you choose "default" as the template, videos are displayed correctly.
When displaying MediaFront in single nodes, the simpleblack, shockplayer, and default templates can be used.
Ultimately, all of the templates that come preloaded with MediaFront should display in single nodes and in Views playlists.
Comment #23
ryan.ryan commentedOkay, so are we going to try and get all of the templates Views-friendly?
Comment #24
travist commentedryan,
I am working on this right now with the 2.x upgrade to pull in the playlist into the other templates, so I would say that within the month this will be resolved.
Comment #25
enjoylife commentedComment #26
bakulaw commentedI cannot play videos in Views even with the default template.
I only see media player...
Comment #27
gghh2 commentedIs there any news on the "custom template ability in views" ?
Comment #28
stationarymotion commentedI just downloaded the latest RC version today and am still encountering this issue with the 2 presets not working in my view. I love the module, I'd just really like to get it off the default preset.
Comment #29
travist commentedThe issue is that the templates that you are using currently do not have views support. You can get around this, however, by creating two presets. One preset to hold the media player in the template of your choice, and the other preset to contain just the playlist from the view. You can then connect them together on the same page as if they were a single media player.
Comment #30
stationarymotion commentedI'll give it a shot, my apologies if you cleared that up above and I just missed it. Thank you for the work, it is great!
Comment #31
semanthis commentedThis problem seems not to be fixed(release from 13. September 2013). Views with playlist only work with default template. This makes it extremly difficult to create an own template, because copying the default template to custom module does not work. Actually I'm just trying to solve #1947354: creating a next video button to get a next- and prev-button to my controller. Any help would be great.
Comment #31.0
semanthis commentedEdited the issue summary to highlight the overall issue.