The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
![]()
As vBulletin 4 is progressing and more mods are available, I have a recommendations which I don't think would be too hard to add on to vBulletin.org. I read about the site going through a few changes this week because of the launch of vBulletin 4.1 PL1, so I have some suggestions for things I think should be incorporated.
1. Having all of the user's downloaded modifications show up in thier profile or usercp that way it is easier to find them again and track them down if needed to go back for support or upgrades. I understand that there is an 'Downloaded' highlight but it's still not as convenient. Not everyone knows about subscribing, so I think it would be much easier if you make it so that the downloaded mods automatically become a subscription. 2. Narrowing down searches for the mods that are supported for the member's vBulletin version. I know that there are some re-usable mods for 3.8 and it's hard for me to find the ones that are supported by vBulletin 4, same thing with a few vBulletin4 mods that are not supported by my version. |
#2
|
||||
|
||||
![]()
For the first item, click on the "User CP" link in the navbar and you'll see direct links to mods that you've downloaded, tagged, nominated for MOTM, and marked as installed.
![]() |
#3
|
|||
|
|||
![]()
Thanks!
![]() Now for the supported mods, :P |
#4
|
||||
|
||||
![]()
TBH, I dont entirely understand your point 2.
|
#5
|
|||
|
|||
![]()
#2: I guess what he's trying to say is to add an identification for mods that will work for 4.x.x from the 3.8.x's section.
An example. Maybe a 3.8.x could work for 4.x but he doesn't know that it's gonna work unless there is an identification. Is that what you're trying to say? |
#6
|
|||
|
|||
![]()
That's kinda what I am trying to say.
Let me put it this way: As I browse through 3.8.x mods and I like one, I don't see that whether it is supported by my vBulletin version or not until I click on the thread. For example, this mod is supported https://vborg.vbsupport.ru/showthread.php?t=120122 But, this mod is not https://vborg.vbsupport.ru/showthread.php?t=231021 I wish that there was a better way to narrow the search down to the ones that are supported. Like on forumdisplay, where there is a drop down box for prefixes (mini-mods, profile customization, major additions...) I think there should be an option for supported mods. |
#7
|
||||
|
||||
![]()
So you mean supported by the developer? That flag doesn't always tell you something about the support. The best thing to do is look at the last few pages of the thread and see if people are having issues and if the dev is responding. Very often, a dev sets that to Supported and then later, when they are no longer hanging out here, they never change it to Unsupported. And, sometimes it's marked Unsupported, but the dev is helping anyway and/or the users are helping out.
|
#8
|
||||
|
||||
![]()
You know a lot of people get confused over what "supported" really means, might be worthwhile to address this during the next big site upgrade... like changing it to "Supported by Developer" or such.
|
#9
|
||||
|
||||
![]()
Except, as I said, there are some mods that are marked Supported (by Developer) and yet the developer hasn't been seen for a couple of months. I know Paul added some code that would automatically change it to Unsupported if the developer hasn't show up online in X months (3, I think?), but there are some mods marked Supported where the Dev has been seen online but for some reason is no longer supporting that mod. It could be they forgot it was marked supported or that they are sick of the same questions all the time, or who knows, but it's misleading to still have it marked as Supported. That is why I recommend anyone wanting to install a mod to actually read the thread. You can then judge just how much, and how often, a dev is supporting the mod. (Of course there are other reasons to read the thread also, but that is a good one.)
|
#10
|
||||
|
||||
![]()
Then maybe get rid of "supported" all together and leave it up to the mod author to mention in their description... I don't know... just throwing things out there. Another option would be to have the support tag expire every 3 months unless the mod author visits the thread to renew it.
|
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|