Sending updates when a mod is updgraded to 4.0

[Paul M]

Please start a new thread in the vb4 area as your question is unrelated to this one. Thanks.

[TheLastSuperman]

Originally Posted by Paul M

I really want to avoid any more significant changes to vb.org code, its already complicated enough, and with one eye on eventually upgrading, its not helpful to add more complication.

JFYI, Ive been thinking about an idea based on a system we already have. At the moment you can define a modification as being an add-on to another, so it becomes like a child, and when you view the main mod, its add-ons (children) are displayed. This system is not perfect as the child mod does not list its parent (due to the way it works).

What id like when I have the time is to re-do that system so it works both ways (a parent mod lists its children, a child mod lists it parent), and also try and use the same (or similar) system to link different (major) vb versions of the same modification - so if you viewed the 3.8 version of a mod, it would list the 3.6, 3.7 and 4.0 versions as well as any add-ons.

It might even be possible to then send an e-mail when a new (higher version) link is added. So if you add a new link to your 3.8 mod, for the 4.0 release, it sends out a notification, but if you add a link to an older version (like 3.7), no notification is sent.

Anyway, just something ive been thinking about for a while, no idea if / when I will have time to actually do it.

Just glad to see this info Paul, seems we posted about the same time last night so I missed that completely but good to know and no rush, I've seen the statements before mentioning something *might be done *possibly when you upgrade the version here. I reckon all that just depends but you know me... I always have a spare 12 pack of Dr. Pepper to bribe you with... well actually my wife buys it all.. keeps me stocked lol.

Ok enough being silly time to see what vb.org has today!

[meissenation]

I just wanted to throw in my 2 cents - I saw the recent announcement and was deeply disappointed. I've gotten a few updates so far for the vb4 versions of mods I have installed and was not only happy to receive them - I was thankful that the coders took the time to let me know they had a vb4-compatible version. It cuts my time in half - now I have a separate e-mail folder to house the vb4-compatible notification e-mails (or atleast ... the ones that were sent before the announcement was made) and when I go to upgrade to vb4 in the near future, I can just refer to those e-mails instead of having to search through the vb4 mods forum. Makes my job a heck of a lot easier.

IMHO - Better to delete an unwanted e-mail than to never receive a wanted one.

To those who consider a vb4 announcement spam, with all the real spam I get already, hitting delete on a few more e-mails that I had originally opted into but now am not interested in receiving is no big deal. Fact of the matter is that by installing the modification and clicking "Installed" we're opting into receiving these e-mails.

It's too bad that people who aren't upgrading to VB4 (and thus don't want the VB4 compatible announcement e-mails) have to ruin a good thing for the rest of us.

[TheLastSuperman]

Originally Posted by meissenation

I just wanted to throw in my 2 cents - I saw the recent announcement and was deeply disappointed. I've gotten a few updates so far for the vb4 versions of mods I have installed and was not only happy to receive them - I was thankful that the coders took the time to let me know they had a vb4-compatible version. It cuts my time in half - now I have a separate e-mail folder to house the vb4-compatible notification e-mails (or atleast ... the ones that were sent before the announcement was made) and when I go to upgrade to vb4 in the near future, I can just refer to those e-mails instead of having to search through the vb4 mods forum. Makes my job a heck of a lot easier.

IMHO - Better to delete an unwanted e-mail than to never receive a wanted one.

To those who consider a vb4 announcement spam, with all the real spam I get already, hitting delete on a few more e-mails that I had originally opted into but now am not interested in receiving is no big deal. Fact of the matter is that by installing the modification and clicking "Installed" we're opting into receiving these e-mails.

It's too bad that people who aren't upgrading to VB4 (and thus don't want the VB4 compatible announcement e-mails) have to ruin a good thing for the rest of us.

That was never the intention, it's just all fubared now because everyone has their own opinions of what is easier for them and no one else. I have 3.x and 4.x and I have a reason for it. I have friends and clients who have mods that are not out for 4.0 yet so why upgrade and lose half their boards functionality.

Think before you leap ladies and gents otherwise the rest of us see it as gibberish, what? I'm sorry and I said above I hate sounding that way but it's like you missed key arguments from the other side of the fence meissenation before you posted no way to beat around the bush in regards to that and to sum it up there's other factors, more than just the few you all are causing a ruckus about as to why the system should be used for updates of only that series mod.

--------------- Added [DATE]1262728096[/DATE] at [TIME]1262728096[/TIME] ---------------

And just to be clear, I had no problem with the notices myself what set me off was friends and clients becoming confused over it and pm'ing or emailing me with questions, no matter how clear something is... if it causes confusion then it needs to be addressed. It has and now you know what to do, look for a new mod like all of us have been for years on here by browsing and using the search up top OR bookmark/favorite the coders profile and check it once a week/month.

[Carnage]

I noticed earlier while updating a mod; under member options there are the following checkboxes:

tag modification
recieve manual updates
recieve automatic (eg an email when a new version is posted) updates

There already exists the ability for people to opt out of the manual update notifications if they wish to.

[TheLastSuperman]

Originally Posted by Carnage-

I noticed earlier while updating a mod; under member options there are the following checkboxes:

tag modification
recieve manual updates
recieve automatic (eg an email when a new version is posted) updates

There already exists the ability for people to opt out of the manual update notifications if they wish to.

Exactly Carnage

The only thing I meant in regards to that is why should a 3.8 owner opt out of a 3.8 mods update because the author simply wants to send out updates about their 4.0 mod using the 3.8's update system?

3.8 = Updates on that 3.8 mod only.
4.0 = Updates on that 4.0 mod only.
= No confusion and problem solved.

Maybe we should simply ask for a new feature when the forums are updated.. Subscribe to Coder or Designer and when they post a new mod in any specified section i.e. you click checkbox to "Send a notification when [username] posts a [vBulletin 4.0 Modification]" etc and BAM you get a new message that btw you asked for specifically alerting you of a new mod by that coder in the mod or add-on forums for your version .

Hmm? Now that's an idea

[TNCclubman]

Originally Posted by Carnage-

I noticed earlier while updating a mod; under member options there are the following checkboxes:

tag modification
recieve manual updates
recieve automatic (eg an email when a new version is posted) updates

There already exists the ability for people to opt out of the manual update notifications if they wish to.

that only notifies you if there is a new update to the current version. Not when the mod is available for the latest vB version.

[Paul M]

Originally Posted by Carnage-

There already exists the ability for people to opt out of the manual update notifications if they wish to.

Doing so would mean they dont get notifications related to the modification they have installed, which is the whole purpose of the system. No one should have to opt out of all notifications so as not get notifications unrelated to their installed version.

If you want to see if a 4.0 version has been released, look in the authors profile, thats one of the reasons they are listed there in the first place.

[Digital Jedi]

Originally Posted by Paul M

I really want to avoid any more significant changes to vb.org code, its already complicated enough, and with one eye on eventually upgrading, its not helpful to add more complication.

JFYI, Ive been thinking about an idea based on a system we already have. At the moment you can define a modification as being an add-on to another, so it becomes like a child, and when you view the main mod, its add-ons (children) are displayed. This system is not perfect as the child mod does not list its parent (due to the way it works).

What id like when I have the time is to re-do that system so it works both ways (a parent mod lists its children, a child mod lists it parent), and also try and use the same (or similar) system to link different (major) vb versions of the same modification - so if you viewed the 3.8 version of a mod, it would list the 3.6, 3.7 and 4.0 versions as well as any add-ons.

It might even be possible to then send an e-mail when a new (higher version) link is added. So if you add a new link to your 3.8 mod, for the 4.0 release, it sends out a notification, but if you add a link to an older version (like 3.7), no notification is sent.

Anyway, just something ive been thinking about for a while, no idea if / when I will have time to actually do it.

You know, I've been meaning to suggest that.

Hey! Can we opt out of getting any posts that ask if a vB 4 version is ready/in the works/a general timeline on when it will be done? Just sayin'... >_>