Marketplace No Update Feature

I was updating tonight and had to carefully make sure one of my modules wasnt updated.

I think it would be a cool and handy feature to add a check box and disable updates for a specific module in the marketplace so i can update all and have no worries about that one getting updated.


updated by @developer-networks: 04/26/14 06:59:55PM

Why would you not want a module to get updated? I can't think of any reason.

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

There are many reasons why I can see this useful. If you've had to modify your Jamroom and don't want it to update those files but continue to keep relevant with all others.

For example on my system I had to modify the jrAudio module and re wrote it to work with my website. Others have asked for my mod on their website. The latest update is irrelevant and not needed in this case.

But If it was I can not update my module mod with out going in and having to change over every line of code Ive added to the update so I avoid this and check the log to see if the update is relevant and worth my time.

I can see others modifying Jamroom modules to work for their website and also running in to this situation not wanting to update specific modules unless chosen.

I think that it would be an excellent idea to have an option to check a box on any module you don't want to update and its safe from getting overwritten. Then it would be safe for me to just to "update all" modules on my system.

I can also see this feature coming in handy for folks who have modified their skins and are wanting to update all the other modules but do not want to update their skin unless that is chosen.


I can see how this could benefit a lot of people.


Also this brought me to thinking about mods. Could in the future developers submit mods with functionality to a "Jamroom mod files location". where we can offer people the option to install our mod if they own a copy of the original?

And if the mod is installed it wont update with the original but looks for the latest mod update? Im not sure if that is something you want to entertain but I can see developers being able to spin creative ideas, functionality and modifications to a lot of pre existing modules so that an end user with less experience in coding can install a mod built to function as their website needs... Thanks.

updated by @developer-networks: 02/11/14 10:52:46PM

If you are going to customise, clone the module. I do that with search and replace but I think jrAparna can do it all for you.

Then when you update your inactive jrAudio module you just compare your active myAudio module to your newly updated jrAudio module, and add the new lines of code.

So in your dev site you have jrAudio (inactive) which is always up to date, and a clone named myAudio (active) which you update at your leisure, if necessary. You can do the same with skins as well.

If it is only the templates that you are changing it's even simpler - just override the module templates in the skin directory.

You can specify requirements for modules in the init function:

'requires' => 'jrCore:5.1.0,jrEmbed',
That specifies at least version 5.1.0 of the core, and any version of jrEmbed. The module will install but cannot be activated if it doesn't meet the requirements.


--
¯\_(ツ)_/¯ Education, learning resources, TEL, AR/VR/MR, CC licensed content, panoramas, interactive narrative, sectional modules (like jrDocs), lunch at Uni of Bristol. Get in touch if you share my current interests or can suggest better :)

This means you're going about it wrong - you should never modify the core scripts of any module. You should clone it, then modify the clone, enable the clone, and disable the original. Then you never have to worry about anything overwriting your changes.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

or create another module that taps into the events and listeners system to alter the output of the module.

that way you get all the updates of the original module and keep your altered way of working too.

Yeah this is really the "JR5" way to do it - make a small, separate module that defines listeners that "get in the flow" of what you want to change, and change it.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Thank you everyone. This was a big help.