Version: 2.2.8, by AndrewD
Developer Last Online: Apr 2010
Category: Major Additions -
Version: 3.6.x
Rating:
Released: 06-18-2006
Last Update: 02-03-2008
Installs: 661
DB Changes Uses Plugins
Additional Files Translations
No support by the author.
Version 2.3.0 of LDM is now the official release. This works with both VB3.7 and VB3.8. You can obtain it here
Version 2.2.8 remains available here, with limited support.
04.02.08: patch-cat.xml 'extra' uploaded - see first post for information
27.10.07: Version 2.2.8-post1 uploaded
French translation of product installer uploaded (other language translations are in the main release zip)
Remember to back up your current database tables before upgrading.
What this is and does
LDM is a general-purpose link and file manager, which handles user uploads and downloads in a flexible way. A range of media players is integrated into LDM and others are included as plugin extras. LDM is described below in the first post of this thread, which also contains a brief list of the currently-known bugs.
This release of LDM works correctly with all VB versions 3.6.x and recent versions of vbadvanced.
I'm worried about loosing template changes. Will upgrading overwrite all existing tables?
Thanks
Upgrading does not delete your template modifications. I can't recall if there are any important template changes between LDM 2.2.7 and 2.2.8 - if so and you have modified any of these, you may need to check on the vb admincp for suggested template reversions.
Always a good idea to take a backup before upgrades - you can also download your templates while you are at it.
I have a web farm (2 IIS servers) and the rewrite to SEO links work fine on one sever and not on the other. I know there must be something differn't but what.
I only wrote this patch recently. It uses the global_setup_complete hook in vbulletin and works the same way as the plugin that the vbulletin people use themselves for their blog software. I've no idea whether that hook was already available in vbulletin 3.6.5, or if the functions in that version of vbulletin are compatible.
Updating to 3.6.8L2 solved the problem with the search. So everything is working allright now.
Andrew,
It seems that our hits are being deleted on their own. Is this something you added? We need to keep at least the last 30 days, but when I look at today, it's only keeping back to the 26th of February.
Andrew,
It seems that our hits are being deleted on their own. Is this something you added? We need to keep at least the last 30 days, but when I look at today, it's only keeping back to the 26th of February.
Take a look on the ldm admin/settings. There's a prune_downloadtable setting which sets the number of dayshits are stored, and defaults to forever. If it's not workng correctly, let me know.
There are several levels of (optional) integration with your forums.
- there is the facility to auto-announce new entries as threads in your forum
- there is an 'extra' that will include a list of new/hot/random entries in your forum displays
and so on, and so on.
You don't need to do anything with vblinks, but I have not spent time writing a converter
Just one thing. The posting block for putting the description in is overhanging the side of the board.
If possible, i would like to make the left hand table smaller, as there is loads of space.
I have had to disable my smilies to stop it overhanging.
apart from that, brilliant hack mate.
:up:
Thanks.
The size of the description box is taken from the formwidth_usercp and messagebox_usercp style variables, which are set on vb/admin/styles/main style vars.
hmm ..tried to delete an entry : running latest versoin on 3.7.
Database error in vBulletin 3.7.0 Beta 6:
Invalid SQL:
SELECT entityid, entityvalue
FROM local_linksentities
WHERE entitytype IN (ENTITY_TYPE_UPLOAD,ENTITY_TYPE_MEDIAUPLOAD,ENTITY _TYPE_IMAGEUPLOAD)
AND linkid IN (590);
hmm ..tried to delete an entry : running latest versoin on 3.7.
Database error in vBulletin 3.7.0 Beta 6:
Invalid SQL:
SELECT entityid, entityvalue
FROM local_linksentities
WHERE entitytype IN (ENTITY_TYPE_UPLOAD,ENTITY_TYPE_MEDIAUPLOAD,ENTITY _TYPE_IMAGEUPLOAD)
AND linkid IN (590);