Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I am just getting familiar with views 2 and its new interface, but I don't see any way to create a custom view of audio nodes. Any suggestions? Or is this feature still being developed for Audio 6?
Thanks in advance for any help with this.
Comment | File | Size | Author |
---|---|---|---|
#17 | audio.20090204.patch | 49.12 KB | rwohleb |
#14 | 273082_download_and_player_fields.patch | 4.18 KB | deviantintegral |
#11 | audio_273082.patch | 2.3 KB | drewish |
Comments
Comment #1
silvercat CreditAttribution: silvercat commentedI'm interested in this too. I would like to have a views-field with the player embedded.
Comment #2
drewish CreditAttribution: drewish commentedthe views support hasn't been upgraded yet.
Comment #3
bomarmonk CreditAttribution: bomarmonk commentedViews 2 Release Candidate for Drupal 6 has now been released. This should at least provide the stability needed for other modules, such as audio, to develop their integration with views 2. I just thought I would note it here, just in case.
Comment #4
drewish CreditAttribution: drewish commentedmarked #311557: Audio and Views 2 problem as a duplicate
Comment #5
drewish CreditAttribution: drewish commentedI just committed default views for audio.module and a couple of audio specific fields. Still a lot to get converted though.
Comment #6
monjohn CreditAttribution: monjohn commentedThanks for working on this! I, for one, appreciate it!
Comment #7
vph CreditAttribution: vph commentedThank you!!! I'm looking forward to audio working with D6 and Views2.
Comment #8
roger6106 CreditAttribution: roger6106 commentedI am also looking forward to Audio being completed for Drupal 6. It looks like exactly the module I've been looking for.
Comment #9
monjohn CreditAttribution: monjohn commentedIs it possible to expose the player or the "download this file" to views? I would like to make a view of the certain audio files with the titles, the player and the download link all listed in a table.
Comment #10
bomarmonk CreditAttribution: bomarmonk commentedYou can do it with the old 5x version, so it's a matter of porting that functionality to 6x. I imagine views 2 is making this a more difficult transition (although I'm guessing views 2 is well worth it)
Comment #11
drewish CreditAttribution: drewish commentedmarked #347936: Views2 Sort by Audio Metadata as a duplicate.
committed the attached to HEAD. it adds support for the audio metadata.
Comment #12
Flying Drupalist CreditAttribution: Flying Drupalist commentedSubscribe, in field none of the meta data are links, they should be links that link to sorting by artist/album etc mechanism.
Also can you please add the player as a field? Thanks for your wonderful module.
Comment #13
Fr0s7 CreditAttribution: Fr0s7 commentedDitto to #9:
- Audio player field for Views 2
- "Download" link field for Views 2
Thanks again for your work on this module. 5.x is wonderful, and I know porting to 6.x is a lot of work. Excellent job.
Comment #14
deviantintegral CreditAttribution: deviantintegral commentedHere is a patch which adds a "download" and a player field. This is my first work on views 2, so there's probably some more work to be done here. It might be good to make the download text an option; right now, it's just a t()'ed string.
Comment #15
drewish CreditAttribution: drewish commentedthe download link looks fine but the player seems a little overly complex... maybe a few comments would help explain it?
Comment #16
Roulion CreditAttribution: Roulion commentedwould be nice if we could have the image too.. withimagecache support as well ;-) !!!
thank you
Comment #17
rwohlebThis is a views 2 support patch, based on the patch by deviantintegral. This patch moves all views code into a views folder, to fit more inline with other contrib module handling of views. Additionally, this module adds custom link text support, as well as introduces a 'play' link field.
This patch removed all node_loads where possible. However, the 'player' field still requires a node_load per result due to the requirement of a full node object in all player theming functions.
Comment #18
criznach CreditAttribution: criznach commentedI manually moved the views and handler files into the audio/views folder. Actually I copied because I wasn't sure if the handlers had to go too.
Now I get:
Error: handler for audio > player doesn't exist!
after I add the player field.
Comment #19
criznach CreditAttribution: criznach commentedI could swear that I posted this already... I later moved the handler files into audio/views/handlers and everything seems to work.
Comment #20
elally CreditAttribution: elally commentedSubscribing
Comment #21
RWWood CreditAttribution: RWWood commentedGreat job with the patch from #17. It gives the functionality I was looking for with views.
Comment #22
kjv1611 CreditAttribution: kjv1611 commentedSubscribing
Comment #23
Flying Drupalist CreditAttribution: Flying Drupalist commentedCan this be committed please? I'm really bad with patches.
Comment #24
tvaughan CreditAttribution: tvaughan commentedYes, committing this one would be really helpful!
Comment #25
andrewfn CreditAttribution: andrewfn commentedI have tested it and am running it on a production site. It would good if this was committed soon.
Comment #26
bcobin CreditAttribution: bcobin commentedI applied the patch in #17 successfully to the 6.x-1.x-dev version, but I still get broken/missing handler in Views. Seeing no views folder in the audio module folder, I then copied the views/handler files to audio/views/handlers - still no handlers.
Any ideas? I'd be glad to know how some folks seem to have gotten this working.... thanks much!
Comment #27
drewish CreditAttribution: drewish commentedI did some cleanup on the handlers and committed those. The patch was moving all the broken views1 code into audio/views/audio.views*.inc which seemed kind of useless so I left the view1 code in audio/audio.views*.inc and moved all the views2 code out. This makes it easier to see what's left to be ported.
Marking this as active until the tag filter/argument handlers and can be ported to views2.
Comment #28
bcobin CreditAttribution: bcobin commentedSo - just to be clear - using a player with an argument (which is required for doing a music search) will not be available in Views until the filter/argument handlers are ported, correct?
Thanks for the work you're doing, drewish - much appreciated!
Comment #29
drewish CreditAttribution: drewish commentedi think there's some argument handling but IIRC things like the track numbers are wierd. i just rolled a new release so grab that and try it out.
Comment #30
roger6106 CreditAttribution: roger6106 commentedWhen using views and setting the option to rewrite the output of an audio field, the audio replacement patterns are "[value_3] == Audio: Track", "[value_2] == Audio: Title", etc. Is this part of this bug, or should I open a new bug?
Comment #31
kjv1611 CreditAttribution: kjv1611 commentedBy the way, I recently (within past couple weeks) finally updated to the latest Audio module release, and it's working great from what I noticed so far. Haven't had much time to mess with it yet, but so far so good! Thanks to drewish and any other developers who assisted!
Comment #32
theohawse CreditAttribution: theohawse commentedHey guys, this is working fine for me, no problems with audio in views for me at all, except one little thing: audio playlists.
Looks like the guys below are stalled because the audio module is still labeled "unstable", hope this is a friendly enough bump!
http://drupal.org/node/393306
http://drupal.org/project/views_bonus
Awesome work!
Comment #33
yngens CreditAttribution: yngens commentedsubscribe
Comment #34
evoltech CreditAttribution: evoltech commentedThe audio player flash controller is still not working for me in on the -dev or -unstable branch. Im guessing there was a revision on the -dev branch that was working for others and now it isn't?