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.
Issue to track necessary changes once #1227706: Add a file entity access API API goes in.
Comment | File | Size | Author |
---|---|---|---|
#6 | 1730730-6-file_access.patch | 502 bytes | circuscowboy |
#1 | 1730730-1-file_access.patch | 571 bytes | Jackinloadup |
Comments
Comment #1
Jackinloadup CreditAttribution: Jackinloadup commentedComment #2
kmadel CreditAttribution: kmadel commentedPostponed until updated release of File Entity.
Comment #3
Jackinloadup CreditAttribution: Jackinloadup commentedFile entity patch is now in. This patch can move forward
Comment #4
agoradesign CreditAttribution: agoradesign commentedThe patch has to be modified a little bit. The change of the access arguments is correct, but the access callback has to stay unmodified at "file_entity_access"
Comment #5
klonos...set to NW as per #4
Comment #6
circuscowboy CreditAttribution: circuscowboy commentedFixed the patch
Comment #7
agoradesign CreditAttribution: agoradesign commentedWorks for me :)
Comment #8
Marty2081 CreditAttribution: Marty2081 commentedPatch works for me too.
Comment #9
lpalgarvio CreditAttribution: lpalgarvio commentedplease prioritize. impeding projects require Media Colorbox (not sufficing with just Colorbox, and there's no time to rebuild Views)
Comment #10
lord_of_freaks CreditAttribution: lord_of_freaks commented#6 Works for me too, i will come to the same solution after being researching for a solution about permission
Comment #11
PI_Ron CreditAttribution: PI_Ron commented#6 Didn't work for me against media_colorbox-1.x-dev
I downloaded to media_colorbox folder and patched like so: patch -p1 < 1730730-6-file_access.patch
Comment #12
oystercrackher CreditAttribution: oystercrackher commented#6 Worked for me but I had to clear the caches.
Comment #13
Desi Raaj CreditAttribution: Desi Raaj commenteddidn't work for me
Comment #14
Barry Tielkes CreditAttribution: Barry Tielkes commentedpatch #6 worked fine for me. Need to clear cache first. Thx!!
Comment #15
lord_of_freaks CreditAttribution: lord_of_freaks commentedI agree with #14 but you need to clear just menu cache
Comment #16
Kirk CreditAttribution: Kirk commented#6 worked for me too. Clear cache.
Comment #17
dwatts3624 CreditAttribution: dwatts3624 commented#5 works great! As the thread says...clearing the cache is a must.
Comment #18
rovo#6 worked for me too. Clear cache.
Solved the "This image failed to load." message I was getting for YouTube Popups.
Comment #19
circuscowboy CreditAttribution: circuscowboy commentedSeems like this has been reviewed and tested.
Comment #20
lpalgarvio CreditAttribution: lpalgarvio commentedworks!!!
please commit =)
Comment #21
MurzConfirm fixing permission problem, please commit.
Comment #22
jide CreditAttribution: jide commentedThe module breaks badly without this patch, does not look good on a production site, maintainers should really commit this :)
Comment #23
chippper CreditAttribution: chippper commentedJust echoing the chorus - the patch seems to fix this issue. Please commit!
Comment #24
marktheshark CreditAttribution: marktheshark commentedWith no disrespect intended toward maintainers, but given the 26 weeks that there has been no commit for this module, wouldn't it be useful for the community to be able to flag a module as having critical issues and have such a warning appear on the main project page to help other assess whether they want to use the module right now or not?
Again, I would like to clarify that this recommendation is in no way intended to undermine the work of the maintainers, but I feel community feedback would be a real time saver for a lot of end users.
What do you think?
Comment #25
agoradesign CreditAttribution: agoradesign commentedgood idea!
Comment #26
lord_of_freaks CreditAttribution: lord_of_freaks commentedCompletely agree with #24, maybe this module Maintenance status should be "Minimally mantained" instead "Actively maintained"
My total respect for module maintainers, nothing as far of my (i think our) intention is undermine the work of the maintainers.
Comment #27
aDarkling CreditAttribution: aDarkling commentedFixed the issue myself in exactly the same manner and THEN found this issue/patch as I was about to submit mine!
I agree with the others. The module does not work for anonymous users without this fix.
kmadel, I'm willing to volunteer as a backup maintainer if you'd like...
Comment #28
klonosI've filed #1134450: Automatically degrade maintenance and development status of projects over time a couple of years ago, but no response :/
Comment #29
Pomliane CreditAttribution: Pomliane commentedMarked #1844912: File access problem as duplicate.
Comment #30
nodecode CreditAttribution: nodecode commentedWrote the maintainer a PM, hoping for a response.
Comment #31
nodecode CreditAttribution: nodecode commentedPatch works for me too. Thanks so much!
To get this committed let's get some new project maintainers or co-maintainers. Please support this issue #1952272: Media Colorbox appears unsupported with reviewed/tested patches waiting
Comment #32
pschuelke CreditAttribution: pschuelke commentedpatch in #6 fixed my 403 for users viewing youtube videos in a colorbox
Comment #33
Greg BoggsThe fix has been commited to the dev branch.
Comment #34
Terebinth CreditAttribution: Terebinth commentedI'm still getting this file issue "Request unsuccessful: Forbidden" with 7.x-1.x-dev
Comment #35
AmiGator CreditAttribution: AmiGator commentedthe same error after 3 years!!! disgusting :-(
Comment #36
Greg BoggsDid we really go 2+ years with only 1 person testing this? It's possible I made a mistake on the commit 2 years ago, but it surprises me that no one would have tried it.