Say you upload the update of a module(s) then turn around and either forget to upgrade it in admin > modules or get side tracked and forgot about going in a doing the update. How about a flag or something that says update me in the admin > module area.

example:

Modules and Addons

[ . ] denotes a module hidden from view in the Modules block

[ * ] denotes a module that has an upgrade available to install

Activate All | Deactivate All

bumping this

Good idea that gets my vote.

certainly gets mine i have brain like a sieve also with all modules the proper place to get the download and dated with version i.e. full info

maybe dragonfly make this as a given standard code of practice for everything created specially when it prides its self on security and speed.

This would save me and every dragonflyer sooooo much time

cheers from Tim

mine too. how about the same thing for themes and blocks too.

yeah Good Idea...

Yep aggree hard to remember where you get all your mods, blocks and themes from.

I like what www.myndworx.com/ have done.

Quote::

The Dev Team here at Myndworx Asylum is proud to announce the launch of the Myndworx Asylum Update Service. This service, much like the Update Monitor for Dragonfly itself, will notify you, whenever you enter the admin page of a MwA module, if you are using the most currently released module or if there's been an update released. If so, you'll be given the url to go and get it so you can stay on top of updates for the modules we release. This is just another of the value added services that Myndworx Asylum builds into it's "Pro" series of modules.

Sorry for the shameless plug Im not connected to them but its what I would like to see with all mods, blocks and themes.

not shameless at all. everyone knows and respects myndworx immensely.

one thought about this though. what would the security implications be for something like this. imagine something bad happening and an exploit gets threaded back to every single site running that module. ugh. i would love to see this happen but security comes first. maybe someone from mwa can chime in?

Also, how many sites have released modules and themes and now the site is dead?

Another thing is that there really isn't a way to centralize this, each module and theme developer would have to be willing/ready/able to not only code this in, but to keep their site online and up to date as the upgrade beacon. This could cost them bandwidth if enough people are using their product.

LOL, sorry to be the voice of doom on all these request ideas, but someone has to play devil's advocate

I don't particularly want all my modules to updated at once, however it would be good to have an indicator that the code I had installed myself didn't match the version in the database. (The original idea).

Since I've made slight changes to a few modules (web links is a prime example), keeping up with the latest releases is not what I want, nor do I want a constant reminder that I don't have the latest version available since it might often to better to wait a bit to see what falls out. (the myndworx idea).

Therefore a way to turn off the upgrade notification should be included. Bandwidth is not a concern for me but others it might be. How much bandwidth would a simple text message take up. Probably much less than even 1kb. I don't think that's so bad. Hmm but it will request that upon each page refresh. Again, maybe mwa can clue everyone into the possiblities here as they are the only independent module to be running an update service.

Throughs up some food for thought.

As a end user I would like to see some complaince - min standard that all modules, blocks and themes must met and then be passed by say a team before being approved and avaible to all. (prob. do allready)

Im coming from the point where dragonfly and some developers (theres lot of great work here) like myndworx (appreciate the work by many on this site) that this is becoming professional software way past a improvment on nuke that it all needs to be going in the same direction and any newbie can upload, install and run (not saying its not like that now) Im talking about the big picture dare I say it Mambo and the likes.

Back to the point I think all modules, blocks and themes should have some sort of update service being say a manditory option where a admin person is advised of a update or where there is a option to upgrade on the fly.

I have used mambo and to upgrade a module etc is way easier no ftp needed.

All great stuff here and I think dragonfly is still the best overall.

The MwA update service queries the server the first time you log into the administration section and go to the modules administration page. It then caches the result in your session. It doesn't check again until you re-login or lose your session. This keeps the number of queries down and keeps your server from having to connect to the update service every time you go to the main module administration page. Our code was pretty much copied from the Dragonfly update notification code, I just templated it.

The amount of data it pulls back is quite small, usually between 0.5KB - 2KB depending on what version of the module the user is running and how many messages you've added. The script that runs it is quite simple, all it does is queries the database based on the version the module sends and creates an xml page in response. Here is an example of the dragonfly update response.

This could easily be built into the core, just add a function that takes the server to check, the version of the module and the module name. Then the module author would only have to add a call to this function into their module and handle the output properly.


Back to the original topic, adding a notification to the modules administration page is possible, I did it in this mod. It just adds an upgrade link in the functions column, right after the install/set as home/uninstall links.

Ya'll have missed my point. well, some of you.

Say you uploaded the updated files to a module, then get side-tracked or forget to go into admin>modules>MODULE>edit>Upgrade to 1.0.1 and click the upgrade link.

Then a little * next to the module says goto to edit and hit the upgrade.


What myndworx has done is great. But that links off site like the DF upgrade. And I dont think most devs of these modules feel like doing all that. And their site might not be there a month from now as Sarah said.

I know what you mean, a way to have it locally notified you that you have a new version that you had uploaded to your server (let say a few days back when you had to ran out and forgot to come back to it) When you come back a few days later and login to the Admin panel and go to manage you modules you see the [*] instead of [.] that tells you that you had not run the upgrade option yet.