Enable/disable automatic update by extension

[Roberto Segura]

I really miss to be able to disable an extension automatic update check. 

Example scenario: 

I developed a fast custom extension for a customer. This extension is working and tested with K2 v.2.5.7. Someday the customer logs in and he sees a K2 update available. He updates and the custom extension developed stops working.

Now I can disable the update manually editing the XML manifest but I would love a column on the extension manager to enable/disable automatic update feature by extension. Would work as the like the status column.

What do you think about this? 

[Ole Ottosen (ot2sen)]

Hi Roberto,

 

Agree that disabling the notifications can be handy for example in cases where you maintain the updates of a site on behalf of a customer (and make sure to verify it works flawless before added to live site).

 

But in such scenario you can simply turn off all extension update checks - which can be done by unpublishing the plugin 'Extension - joomla' which handle the update sites for ext. Similarly the Quick icon can be unpublished.

 

Wouldnt a general disable as the built in be enough in most cases?

 

Cheers,

 

Ole

--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/joomla-dev-cms/-/F_TlIG9riHYJ.
To post to this group, send an email to joomla-...@googlegroups.com.
To unsubscribe from this group, send email to joomla-dev-cm...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/joomla-dev-cms?hl=en-GB.

[Roberto Segura]

Thanks for your answer Ole,

I didn't know the plugin disable method :)

It can be useful for me now but I don't want to block all the extension updates. I only want to stop showing automatic updates for extensions that can break the site functionallity. This way the customer can still apply any updates. 

Also if you disable it and the customer manually updates and breaks the site you will know that it was done intentionally.

[Nick Savov]

+1. It would be great if you could submit that as a feature patch.

Kind regards,
Nick

[Roberto Segura]

I'll code it :)

[Nick Savov]

Awesome! Post on here afterward and I'll test it :)

Kind regards,
Nick

> I'll code it :)
>

> El viernes, 7 de septiembre de 2012 05:57:06 UTC+2, Nick Savov escribi�:

>> joomla-...@googlegroups.com<javascript:>.

>>
>> > To unsubscribe from this group, send email to

>> > joomla-dev-cm...@googlegroups.com <javascript:>.

>> > For more options, visit this group at
>> > http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
>> >
>> >
>>
>>
>

> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To view this discussion on the web, visit

> https://groups.google.com/d/msg/joomla-dev-cms/-/tjMLNnGNCKwJ.

[elin]

It sounds like a useful extension for professional site implementers to be able to install for their clients.  It doesn't sound that useful for the normal web master I have to say.  So maybe code it as an extension and test the market via the JED and posting in the magazine etc. 

Elin

On Friday, September 7, 2012 10:40:21 AM UTC-4, Nick Savov wrote:

Awesome!  Post on here afterward and I'll test it :)

Kind regards,
Nick

> I'll code it :)
>

> El viernes, 7 de septiembre de 2012 05:57:06 UTC+2, Nick Savov escribi�:

[Roberto Segura]

I'll code first ;) 

[Sam Moffatt]

You could probably just nuke the entry from the update site for the
extension and then it's not going to do anything with that update site
any more. Presuming there aren't any other extensions pointing to that
site it shouldn't be a problem. The update site will be replaced when
the extension is updated however I figure you're already handling
that.

Cheers,

Sam Moffatt
http://pasamio.id.au

> https://groups.google.com/d/msg/joomla-dev-cms/-/nHV8eQ1HMz4J.

[Roberto Segura]

Thanks for the idea Sam!

Have to check update dependencies but I think it's the best & simple way to do it :)

Cheers,

Roberto Segura