Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted December 8, 20231 yr We're experiencing an issue with moderators with only file permissions granted being unable to see pending versions in the approval queue. I looked into this and there's a check in ./applications/downloads/extensions/core/ContentRouter/Files.php:49 where PendingVersion is only inserted where \IPS\downloads\File::modPermission( 'unhide', $member ) is true. However, since no container is provided, this will only return true if the user has global content unhide permission.
December 11, 20231 yr Sorry, Im a little confused here. Did you mean you set them to be able to see pending versions, rather than setting them not to be able to see?
December 18, 20231 yr Author Moderators with all Downloads permissions granted do not see pending versions in the approval queue. Is there a permission I'm not seeing for pending files versions? Edited December 18, 20231 yr by G17 Media
December 18, 20231 yr If they are able to see anything else needing approval, then I wouldnt think so. Unless you dont give permission to see hidden items? If you are unsure, please let me know the name of an example moderator who cannot see these, and I can log in and take a look for you
December 23, 20231 yr Author To replicate on any IPS community: Create File Moderator subgroup, add it to Moderators, give every File/Downloads permission (including hide/unhide). Post a file where approval is required. Note that the file appears in the approval queue for a user in that moderator group. Post an update to said file, where approval is required. Note that the file is not shown in the approval queue for this moderator group, nor can they actually approve the file. I've fixed this on my community so I don't need this to be fixed upstream - but this is a heads up for a bug in Invision Community. Edited December 23, 20231 yr by G17 Media
December 29, 20231 yr Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.