The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
||||
|
||||
You mean likely requiring screenshots and demo links or something?
|
#12
|
||||
|
||||
Yeah, something more elaborated, bcuz as Marco stated they have all the freedoms, maybe some responsibilities for the regular Joe, in a democracy we have to advocate for the regular user...
p.s. My first hack installation required 'CHMOD' never heard of that before and I thought it was just part of that hack, so I posted on the thread and the Coder didn't feel like supporting and wait 1 day till someone told me the 'How To', nowadays I still see hacks like: 'Import+CHMOD+User Permissions and THAT'S IT! Some Coders have the education to elaborate HTML's tutorials, PDFs, Step by Step, etc |
#13
|
||||
|
||||
Well I'm making articles, but I didn't know until now that more technical articles were in demand. I could probably make a basic vBulletin modification guide article though, sound good?
|
#14
|
|||
|
|||
Great idea!!
Can't see it being implemented, though. |
#15
|
||||
|
||||
Why not? Too much effort?
|
#16
|
|||
|
|||
Yes.
Too much effort for something that can already be done without any change, but isn't done anyways. |
#17
|
||||
|
||||
It would also be a good idea to list templates & database tables that are
generated when installing some mods. To me, this would decrease the " what template do I edit" question. |
#18
|
||||
|
||||
You mean listing what tables and templates are added by each modification? That could be rather useful.
|
#19
|
||||
|
||||
Just for clarification, what I suggested can't be done currently. Of course in the main body of your modification post you could describe any changes and keep a log of the version changes. But what I suggested was a separate function under modification settings that is available when updating a mod (not upon initial creation). In that new settings section, you can choose one of four "reasons" for updating the mod, if they apply. Then, each user when marking a mod as 'installed' can also edit their settings page for that mod, and change their notification level, and only receive email notifications, for example if reason 4 (security fix) was checked but for other minor updates, they could choose not to receive email notification. This functionality is not currently available. But I can also understand that as volunteers you don't have all the time in the world to dedicate to vb.org, so it might be too much effort to implement.
|
#20
|
|||
|
|||
A level system where the user can set the level he wants to view (new version/update/security update/whatever) does benefit the users. We might have a look at implementing such feature in the next large upgrade of vB.org, but i don't see this happen very soon. Will keep the suggestion on our list.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|