New feature: Mod update type/urgency

[sockwater]

It could be helpful, if when updating a modification, the author could specify what type of update/upgrade this is, which then tells the admins who have it installed how urgent it is to update the mod.

1. New features - Updating is only needed if you want the new features.
2. Minor bug fixes - Updating is needed to fix minor/cosmetic bugs.
3. Major bug fixes - Updating is highly recommended to fix bugs that cause data loss and/or interfere with vBulletin or other modifications.
4. Security fix - Updating is urgently needed to fix security flaws.

The advantage to this is that in the notification email, users can decide if they need to upgrade now or if it's not all that necessary.

Just an idea. What do you think?

[Lynne]

I like that idea!

[MagnetiCat]

Great idea!

[smooth-c]

Good idea!

[Brandon Sheley]

I think it's a good idea as well :)

[iogames]

Good idea but I thought everything was on place... :confused:

Why don't you add:
- Guidelines and Mandatory Sections to Release a Hack/Mod [since Coders post as they want, sometimes without further explanation or screenshots]
- Detailed Tutorials [ we can save a loooooooooooooot of same questioning]

but thanks again to the Coders ;)

[Spank]

It could be helpful, if when updating a modification, the author could specify what type of update/upgrade this is, which then tells the admins who have it installed how urgent it is to update the mod.

1. New features - Updating is only needed if you want the new features.
2. Minor bug fixes - Updating is needed to fix minor/cosmetic bugs.
3. Major bug fixes - Updating is highly recommended to fix bugs that cause data loss and/or interfere with vBulletin or other modifications.
4. Security fix - Updating is urgently needed to fix security flaws.

The advantage to this is that in the notification email, users can decide if they need to upgrade now or if it's not all that necessary.

Just an idea. What do you think?
Great idea. This would benefit anybody who installs mods.

[Marco van Herwaarden]

An author has already all the freedom he needs to include any usefull information when sending out an update email.

[cheat-master30]

I agree with the original suggestion and think it should indeed be implemented. Plus, you could then set to only receive updates you actually care about, and not just an email for every fix whether security, feature or bug fixing related.

--------------- Added 1218638328 at 1218638328 ---------------

Good idea but I thought everything was on place... :confused:

Why don't you add:
- Guidelines and Mandatory Sections to Release a Hack/Mod [since Coders post as they want, sometimes without further explanation or screenshots]

What in detail would this add? Sounds interesting.

- Detailed Tutorials [ we can save a loooooooooooooot of same questioning]


That's the exact purpose of the article section, except no one seems to actually read it for any information they might need.

[iogames]

Well many Authors ignore the User's curve of learning and explain like you think-what they think, or you see what they see... causing some chaotic threads [i.e. any Screenshot?]

Some guidelines to release hacks doesn't hurt to anybody, and Thanks again for their voluntary work :up:

[cheat-master30]

You mean likely requiring screenshots and demo links or something?

[iogames]

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! :mad:

Some Coders have the education to elaborate HTML's tutorials, PDFs, Step by Step, etc

[cheat-master30]

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?

[Jase2]

Great idea!!

Can't see it being implemented, though. :rolleyes:

[cheat-master30]

Why not? Too much effort?

[Marco van Herwaarden]

Yes.

Too much effort for something that can already be done without any change, but isn't done anyways.

[blind-eddie]

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.

[cheat-master30]

You mean listing what tables and templates are added by each modification? That could be rather useful.

[sockwater]

Yes.

Too much effort for something that can already be done without any change, but isn't done anyways.

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.

[Marco van Herwaarden]

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.

[---MAD---]

It's a nice suggestion. Although I do tend to check updates to plugins often anyway and read about the updates no matter what it contains.

[sockwater]

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.
Cool, thanks. :)