Most recent edit on 2006-07-31 16:52:11 by JimmyConner [Minor change]
Deletions:
<tr><td><strong>Version</strong></td><td>v0.2</td></tr>
<tr><td><strong>Release Date</strong></td><td>04/07/06</td></tr>
Changelog
Fix problem with
MySQL importing the table
Auto-import the table if it doesn't exist
Fix issues with different header sizes (Thanks Howie!)
#0000020 Fix for errors on update page when table is not created yet
Edited on 2006-04-07 22:14:47 by JimmyConner [Update version and some info]
Additions:
<tr><td><strong>Version</strong></td><td>v0.2</td></tr>
<tr><td><strong>Release Date</strong></td><td>04/07/06</td></tr>
You do not need to setup a cron job or scheduele, as it runs immediately after the normal poller automatically. There is currently one option Update Scan Interval which can be set to Never, 1 Day, 2 Days, 1 Week, or 1 Month, This is the time before checking for updates. 1 Day between scans is the minimum amount of time allowed, this is to keep the servers from being overloaded with requests. There is a command line option -f to force the scan to run immediately, but this is for debugging use only, and if you use it excessively (ex: 3000 times a day) it is possible that you could be banned from checking for updates on the server side.
Fix problem with
MySQL importing the table
Auto-import the table if it doesn't exist
Fix issues with different header sizes (Thanks Howie!)
#0000020 Fix for errors on update page when table is not created yet
Deletions:
<tr><td><strong>Version</strong></td><td>v0.1</td></tr>
It currently does not auto-create the database tables so you will need to import the file yourself. You do not need to setup a cron job or scheduele, as it runs immediately after the normal poller automatically. There is currently one option Update Scan Interval which can be set to Never, 1 Day, 2 Days, 1 Week, or 1 Month, This is the time before checking for updates. 1 Day between scans is the minimum amount of time allowed, this is to keep the servers from being overloaded with requests. There is a command line option -f to force the scan to run immediately, but this is for debugging use only, and if you use it excessively (ex: 3000 times a day) it is possible that you could be banned from checking for updates on the server side.
Initial Release
Edited on 2006-02-19 03:43:29 by PsybeR [edit for clarity]
Additions:
- Extract the archive
- Move the extracted folder to your plugins driectory
- Add the database mysql cacti < update.sql
- Add $plugins[] = 'update'; to the $plugins = array(); section in include/config.php
- Check the Check for Updates box under User Management-> Realm Permissions
- Set the Update Scan Interval under Settings-> Misc
Deletions:
Extract the archive
Move the extracted folder to your plugins driectory
Add the database mysql cacti < update.sql
add $plugins[] = 'update'; to include/config.php
Check the Check for Updates box under User Management-> Realm Permissions
Set the Update Scan Interval under Settings-> Misc
Edited on 2006-02-19 03:02:36 by PsybeR [added install directions]
Additions:
Installation
Extract the archive
Move the extracted folder to your plugins driectory
Add the database mysql cacti < update.sql
add $plugins[] = 'update'; to include/config.php
Check the Check for Updates box under User Management-> Realm Permissions
Set the Update Scan Interval under Settings-> Misc
Edited on 2006-02-19 01:03:19 by JimmyConner [Added Thumbnail]
Additions:
</table><br>
<a target=_blank href='/screenshots/plugins/update.png'><img src='/screenshots/plugins/thumbs/tn-update.png' border=1></a>""
Deletions:
</table>""
Oldest known version of this page was edited on 2006-02-19 00:57:43 by JimmyConner [Added Update Plugin]
Page view:
Update
| Description | Displays current information about all installed plugins and checks for updates. |
| Plugin Author | Jimmy Conner |
| Version | v0.1 |
| Release Date | 02/18/06 |
Documentation
It currently does not auto-create the database tables so you will need to import the file yourself. You do not need to setup a cron job or scheduele, as it runs immediately after the normal poller automatically. There is currently one option
Update Scan Interval which can be set to Never, 1 Day, 2 Days, 1 Week, or 1 Month, This is the time before checking for updates. 1 Day between scans is the minimum amount of time allowed, this is to keep the servers from being overloaded with requests. There is a command line option
-f to force the scan to run immediately, but this is for debugging use only, and if you use it excessively (ex: 3000 times a day) it is possible that you could be banned from checking for updates on the server side.
Changelog
Initial Release
Download∞
Feature Request/TODO List∞
Bug Tracker∞
CategoryPlugins