The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
![]()
With each new vB release we see some modifications, such as BB Codes, being reposted under the new version even though the actual code is identical to what was posted in the first thread. The same thing happens with some template modifications that are not dependent on the vB version.
How about a new Modifications category for these types of changes so that they're only posted once? ![]() |
#2
|
||||
|
||||
![]()
I second that
|
#3
|
||||
|
||||
![]()
Thank you for the suggestion, we will add it to the list of ideas to be considered.
![]() |
#4
|
||||
|
||||
![]()
Also Add ons for 3,5 and 3.6 should be categorised into Plugins, extensions, code mods, and misc hacks (option changes,bbcodes...)
|
#5
|
||||
|
||||
![]()
Maybe just integrate an option to move a released Hack from one version to another, like most would do from vB 3.5 -> 3.6 ?
So just an improvement of your HackDB, a new function to move a thread to the correct vB-Section depenting on its compatibility ![]() |
#6
|
||||
|
||||
![]()
How about a few drop down menus when you add a new mod. One will be of vb3.0, next will be of vb3.5, and the 3rd will be be vb3.6.
You can put there what version will work. If you have 3.0 saying "not compatable" and 3.5 saying "3.5.4" and 3.6 saying "3.6 beta 3" then the mod will show up in vb 3.5 and vb 3.6. What do you think? |
#7
|
||||
|
||||
![]()
bump.
|
#8
|
|||
|
|||
![]()
Thank you for you feedback.
We will keep in mind all the input we get, when we are working on the redesign of the site. |
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|