Version: 2.3.0, by AndrewD
Developer Last Online: Apr 2010
Category: Major Additions -
Version: 3.7.0
Rating:
Released: 12-24-2007
Last Update: 06-13-2009
Installs: 576
DB Changes Uses Plugins
Re-useable Code Additional Files Translations
No support by the author.
What this is and does
LDM is a general-purpose tool for managing libraries of links and files, and handling uploads and downloads in a flexible way, while tracking and control user access. It has a range of integrated media players and a large library of 'plugin' extras.
Installation and Usage Explained in the on-line Wiki, with a brief explanation in the file instructions.txt in the release zip. The recent revision history is given in the first post of this thread.
Please use carefully and always backup your database before upgrading. Post reports of problems and suggestions for enhancements in this thread.
14.06.09 Version 2.3.0 is now the the officially-supported version. Works with 3.7 and vb 3.8. Please post comments in this thread
22.06.08 Version 2.2.9-post1 - This is the previous supported version. Works fine with all versions of vb 3.6 and vb 3.7. All standard features except profile integration and forum prefix selection work fine with vb 3.8.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
I can use 0 for force_redirect, but it eats up a ton of memory, equal to the size of the file.
I don't have a local file prefix set either, and all of the files are located in the web dir.
Any thoughts?
I think this is my fault. I put in a check to stop use of force direct when files are outside the web dir, and the check is too rigid. Will provide a fix today.
My ultimate goal is that all file downloads are done via hard coded URL links posted in posts that look like this "http://uber-goober.com/forums/local_links.php?action=jump&linkid=931". This makes a popup box appear and the user can download just that one file.
OK, understood
Quote:
Originally Posted by josiespencer
(1) When I new user signs on for the first time he finds a file he wants to download:
(2) So he clicks the hyperlink and gets the prompt for accepting the download terms:
(3) He clicks Continue and gets:
(4) He clicks Go and sees:
I understand.
Quote:
Originally Posted by josiespencer
(5) OK, first of all he isn't supposed to see this screen ever, he is just supposed to get a popup box asking him where he wants to save the file. Regardless, now he can do/see things he shouldn't be able to see. So he clicks on Categories to get a list of those:
(6) And then clicks on the LDM hyperlink and gets a list of all files in the LDM category:
(7) And now he can search for any file he wants including hidden files:
I understand that you don't want people to go via the main LDM pages but I am surprised that they can see entries that you don't want them to see, particularly hidden entries.
If you don't want people to see hidden entries, then you should take away *can_view_hidden* permission from their usergroups.
Quote:
Originally Posted by josiespencer
If I switch "off" the can_view_category for that users usergroup, he never gets the download acceptance terms in (3), instead he gets this:
This is true, and correct behaviour.
The basic problem is that the "accept rule" forms were not designed with your route through LDM in mind. I think it's easy enough to change. I will see what I can do.
I think this is my fault. I put in a check to stop use of force direct when files are outside the web dir, and the check is too rigid. Will provide a fix today.
I understand that you don't want people to go via the main LDM pages but I am surprised that they can see entries that you don't want them to see, particularly hidden entries.
If you don't want people to see hidden entries, then you should take away *can_view_hidden* permission from their usergroups.
This is true, and correct behaviour.
The basic problem is that the "accept rule" forms were not designed with your route through LDM in mind. I think it's easy enough to change. I will see what I can do.
They do not have can_view_hidden.
OK, looking at it another way, is there a way to allow one group of people to see only things in directory PUBLIC and another group of people to see things in both PUBLIC and PRIVATE? Is there a loophole around that maybe? Or maybe with two different forums? Because the hook to permissions for forums for a file doesn't seem to restrict this either. Once you get in that post-acceptance screen, it is like you are an admin or something.
I want to work within in the rules to do what I need to get done, without you having to code anything.
OK, looking at it another way, is there a way to allow one group of people to see only things in directory PUBLIC and another group of people to see things in both PUBLIC and PRIVATE? Is there a loophole around that maybe? Or maybe with two different forums? Because the hook to permissions for forums for a file doesn't seem to restrict this either. Once you get in that post-acceptance screen, it is like you are an admin or something.
I want to work within in the rules to do what I need to get done, without you having to code anything.
It's quite possible there's a bug, but without further information, I can't help you. There's nothing special about being 'post-acceptance'.
There are two ways to let one usergroup see PUBLIC and another see PUBLIC + PRIVATE.
a) you go to PRIVATE, edit category/user permissions, and take away can_view_category from the first usergroup *in that category*
b) you go to PRIVATE, edit category and associate the category and all its entries with a forum to which only the second usergroup has vbulletin *can_view_forum* permissions.
Do you want me to take a look at your site? Send me a PM if so.
Links and Downloads Manager Details »»
About Developer
Visit Web Site
DB Changes 
No support by the author.
06-14-2008, 12:59 AM
