ATTENTION, ATTENTION: PLUGIN NO LONGER IN DEVELOPMENT!!!

The Elgg Update Services plugin will check the plugin repository on the Elgg Community site for updates of plugins installed on your site and notifies you by email about new plugin releases. This plugin has been developed originally by Ray J. I've taken over maintaining it from Ray J because he lacks the time to develop it any further.

The automatic check for updates is partly randomized to avoid too much load for the Elgg Community site's server. The minimum time between 2 automatic checks is 7 days. To these 7 days an additional randomly created interval between 1 minute and 1 day is added, so the automatic check is done every 7-8 days. Alternatively, you can check manually for updates (the check is always done on viewing the "Manage Updates" page).

If a new version for a plugin is found, you will have the options to visit the corresponding plugin's page on the Elgg Community site and/or to directly download the latest available version.

Requirements:

• Elgg "hourly" cron enabled,
• HTTP requests using port 80 between your site and Elgg comunity. Check with your host provider if in doubt.

Install instructions:

1. If you have a previous version of the Elgg Update Services plugin installed, first remove the old elgg_update_services plugin folder from your mod directory before copying/extracting the new version to your server,
2. Copy/extract the elgg_update_services archive into the mod folder,
3. Enable the elgg_update_services plugin,
4. Optionally, enter an email address on the Elgg Update Services plugin settings page to receive notifications about plugin updates available.

Thanks (by Ray J):

• A big "thank you" to Cash for develop the community webservices and for the relentless support.
• A great "hello" to the Brazilian community. You rules, my friends.
• As always, thanks to Dhrup. He knows the reasons.

End of life of the Elgg Update Services plugin

Sorry. But I don't see any sense in further maintencance of this plugin. Elgg 4.0 and newer no longer uses the manifest.xml file to handle version information. But this file was used by the Elgg Update Services plugin to create a checksum to compare against a checksum created on the server side (i.e. the community site) among some other steps to find out if there's a new version of a 3rd party plugin available for the Elgg version used. So, a major rewrite would have been necessary for the Elgg Update Services plugin to work again on Elgg 4 INCLUDING some changes on the community plugin repository plugin on the Elgg Community server. Additionally, some developer might no longer release their plugins on the community site at all (or only with a huge delay) but rather do their development to a large extend (or only) on their own github repositories. Therefore, it would probably give often a wrong impression if the Elgg Update Services plugin wouldn't report the availability of new plugin releases - there might be some but only not for download on the Elgg community site.

Suggestions to be kept informed about new plugin releases

• follow ("friend") the developers on the Elgg community site and configure the notification settings to get an email on new activity of these developers. You'll be informed about new plugin releases,
• if there's a github repository available of a plugin you are interested in, "watch" this repository to receive status updates about new activity.