Closed (fixed)
Project:
MediaElement
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Dec 2011 at 05:53 UTC
Updated:
28 Jan 2012 at 19:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
lyricnz commentedI have the same issue:
- start from empty D7 site
- download and enable Link (7.x-1.0) module and Mediaelement module (7.x-1.1)
- add a Link field to Article with default settings
- change the display of the field to MediaElement Audio
- create an article, set the URL to something - I used http://www.robtowns.com/music/blind_willie.mp3
- view article, error emitted
Problem is caused by mediaelement using $item['uri'] - when the actual url is stored in $item['url']
Comment #2
lyricnz commentedThis was caused by commit http://drupalcode.org/project/mediaelement.git/commit/6192196 which refers to compatability with Media module. I am not using Media module at all.
Comment #3
lyricnz commentedHere is a patch that re-implements the functionality removed in the commit above - but checks for link_field in particular, rather than file.
Comment #4
lyricnz commentedUpdated patch, with a fix relating to url query parameters from #1177430: Query parameters are stripped for link field.
Comment #5
lyricnz commentedHmmm.. it seems that adding query parameters to the URL breaks the control (I get just a black box). Put that "needs review" back to #3 until I sort it out.
Comment #6
robbielink commented#3 failed for me but I'm new to patching and realized I had already patched that module with #9 from #1170536:Undefined variable: link_types in mediaelement_field_formatter_settings_form().
Can you use the patch command to add another patch or do you have to do it manually? Seems like the line numbers would have changed.
Comment #7
lyricnz commentedYou can "patch -R" to unapply that patch, then apply this one.
Comment #8
robbielink commentedSorry, but I'm confused (new to Drupal)....
Since the other patch I applied appeared to correct an error I was getting I assume I want to keep that patch and also apply yours. In which case it sounds like you're saying the answer to my general question is that no, you can't auto patch an already patched module - it has to be done manually.
Or are you saying that I don't need the other patch if I apply this one and so I should reverse the previous patch and just add this one?
Or is the idea that perhaps I do need the other patch but I should unapply it in order to test your patch and then go from there?
And if that is the case, is it safe to say that the proper way to test a patch is to work only with the original unpatched module?
(The more I think about it it seems that this last thought is what's going on).
Sorry for these general questions - just trying to understand how things work around here. Thanks!
Comment #9
robbielink commentedOK - trying to get into the spirit of things here....
Went back to a clean copy of mediaelement.module and applied patch #3.
Hunk #1 FAILED at 129.
Hunk #2 succeeded at 120 (offset -26 lines).
What am I doing wrong?
Edit: Scratch that complaint - my installation of this module may be corrupted in some other way. After that last patch going to the config screen just brought up a blank blue screen (wow - haven't seen that since dumping Windows!).
I'll reinstall and start from scratch tomorrow.
Comment #10
lyricnz commentedYou probably did it right - I just tried this on a stock 7.x-1.1 download, and got the same error with Hunk 2. My patch is actually against the latest code in git 7.x-2.x branch - it's a bit unclear what the module maintainer is doing with this branch vs main. Here's a patch against git trunk (which is the same as 7.x-1.1)
Comment #11
robbielink commented#10 worked for me.
Interestingly - the other patch I mentioned in post #6 is apparently not needed now. I applied your patch over a clean version of the module and get no more errors and the player displays fine and works fine.
Comment #12
chrowe commented#10 worked for me as well.
Drupal 7.10
MediaElement.js 7.x-1.1
Comment #13
scottrigby#10 is definitely a better solution than #1248572: Support for the Link Module, and works like a charm.
Comment #14
dave reidCommitted with a few trivial modifications (and used the wrong issue # in the commit message, oops).
http://drupalcode.org/project/mediaelement.git/commit/53eee42