Not yet (quite)

It will be in version 2.2.7, as of the next beta (just added it)

Thanks - maybe we get to win this time - LDM's been nominated twice, I think, but got outvoted both times.

I've kept meaning to do this, but never got round to it. I still do plan... Maybe soon

I'm not familiar with how that works? Do you mean a progress bar during the download?

This is how I propose that it will work in the final 2.2.7:

(already implemented in the version you have)

- The main admin settings gives two options (currently in the "How Entries are Displayed" section, but they move to their own section). These are links_expiry_days and links_expired_catid. These options are also available on a per-category basis, in the edit category/display settings.

- When links_expiry_days has a non-zero value, then entries only become visible on their submission date (which, as you know, can be forward-dated), and then remain visible for links_expiry_days. Otherwise entries become visible immediately submitted/moderated and remain visible until explicitly deleted.

- When links_expired_category is set (either globally or per-category), expired links are moved to that category the first time their current category is viewed *after* the expiry date.

(in the final 2.2.7)
- there is also an option on the add/edit entry form to immediately expire the entry. This is probably more useful during 'edit entry' than 'add entry'. It gives you a way to force expire certain entries early.

- when an expire entry is moved to a different category, it is automatically given the forum viewing privileges that apply to that new category. Otherwise it keeps its current forum permissions

- the LDM group permission can_view_hidden (up to 2.2.7 alpha, can_view_expired) defines which users can still see expired entries. Other users cannot see these.

So, this gives you the freedom to set up a range of possible behaviours, for example:

- set link_expiry_days but not link_expired_catid: expired entry remains in current category and is visible only to users who have can_view_hidden permission

- set link_expiry_days and link_expired_catid on the global admin page: expired entry is moved to new category, stays expired, and is visible only to users who have both can_view_hidden permission and the relevant forum permissions for the new category

- set link_expiry_days and link_expired_catid for one category only: entries only expire in that category, are then moved to new category, are no longer considered to be expired but are only visible to users who have the relevant forum permissions for the new category

And so on.

Does this cover all your needs?

Hi I'm a new LDM user. Just installed it to my vBulletin 3.6.4. First of all, big thanks to AndrewD for creating such a wonderful mod! I managed to get it up and running smoothly.

I'm now trying to get the vBa modules to work. I tried importing ldm_new and ldm_hot. It prompted that there are already existing modules with those names. I suppose its referring to the modules that came with the default LDM install. So I renamed them to vba_ldm_new and vba_ldm_hot. Confirmed that they are checked within my one and only VBadvanced page. Also included the following in the portal header:
However, my "What's new" and What's Hot" box on the portal appear empty. It currently only shows the headers. Any idea what could be wrong? Or what else I can check?

any help would be greatly appreciated. :)

The pre-module version has an incompatible version of the adv_portal_custom_ldm_hot, adv_portal_custom_ldm_new, etc templates.

Try uninstalling and reinstalling the module, being sure to select the 'overwrite the templates' option.

If this doesn't work, I'm happy to take a look.

You're right about the php code. Pre constructing these modules, the php files were provided in the modules directory.

Andrew, I've noticed that you have something named "limit-uploads-byuploads," which comes as a plug-in with the latest official release. If I use this plug-in now, will all the settings be retained if this functionality is implemented in version 2.2.7. That is to say, if I use this plug-in, and if users upload images and files according to these settings, will I lose these settings and will they have to do it all over again if I upgrade to 2.2.7 in the future?

Beta code for 2.2.7 has been uploaded - see main post of this thread.

Please backup your database before upgrading.

Reports please!!!

No, you will not lose track of user's uploads by changing from the plugin to the new code.

The beta 2.2.7 has just been made available, which includes the new code for upload checking.

Like, the user chooses the file to download, then they get sent to a redirect page which says something along the line "Your download will automatically start in 5 seconds", it counts down until the 5 seconds are up, then the file downloads. Oh, also, is there any way we can choose permissions for categories rather than the entire LDM manager and forum permissions? Like, say in one category, I have a bunch of WMV videos that people can stream in the jukebox and save, and in another category they can only stream the WMV files in the jukebox, not save them.

EDIT: I just installed beta 2.2.7 and I'm now getting this error when I try to go into the admin panel for LDM (I took out the IP and script variables):