Improved Joomla! extensions update handling of paid for extensions#2769
Conversation
before downloading a package
|
Here is a sample plugin to respond the download event, and insert credentials in the download request. The plugin should be in the "installer" group, but any other plugin type is fine as long as you make sure the plugin is loaded when needed. |
|
I tested this pull request and it doesn't seem to effect anything. My component still updated properly. However I did not create a plugin to test the additional install plugin trigger. |
|
Steven, FYI, I have attached a plugin implementing Akeeba Release system to the tracker item: http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=33133&start=0 (same plugin works both on 2.x and 3.x) |
Improved Joomla! extensions update handling of paid for extensions
Hi,
In starting to use the paid-for extensions updater recently introduced in 3.x (tracker 32684, #2508), I came across some limitations that make it difficult for us to actually use it.
Therefore I'm proposing the following small contribution to make this feature a bit more universal.
What could be improved:
The proposal is simply to add firing an event at the right time and place, to allow an extension-supplied plugin to alter the url and/or headers on the fly as required by the extension supplier authorization mechanism.
Drawbacks:
Benefits:
This PR is backward compatible and doesn't touch existing code, it only adds a bit more flexibility.
Also see tracker item: http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=33096&start=0