this commit will cause your 1.0 environment to break. to fix, please
run the script 'profile_migrate.php'. this commit includes a major new
feature to allow your Cacti system to have multiple polling intervals
and for you to create identical graphs using multiple polling intervals
in a sane way. this is an initial commit, one that has been tested.
however, there will be subsequent commits. however, after migration,
this should be considered stable.
They had different fontsizes so they need individual heights.
Note:
In latest IE Edge it moves a minimal bit no matter what value you give. Chrome is perfect.
back port the following features from main:
1) vdef support
2) new graph items
3) new graph options
this covers all the high points available in rrdtool today.
also change the following:
1) allow forms to include spacers
2) reorganize graph template form with spacers
3) many help wording back ports from main
for those testing, if you are going to start using this version, you
will have to implement the changes in the upgrade script or reinstall.
also note that this change may break new aggregates.
devices should be created and graph automation rules executed with this
change. still need to validate tree rule creation. the scope include
initial device creation, and any network scanning.
If you are running in development, you have to issue these two commands
rename table settings_graphs to settings_user;
rename table settings_graphs_group to settings_user_group
There are still three steps to go in this overall. The first is to
replace all the page filtering session storing and validation functions
and the second is to propagate those changes into various areas of the
lib directory that include the use of the various variables, lastly,
developer mode will have to be enable to see if there are any variables
used in the code that have not been sanitized. Note, at this point the
develop branch should be thought of as slightly unstable
this is part three of project to remove the use of $_GET, $_REQUEST, and
$_POST in the code. Parts one and two have already been completed.
Part one was to remove the use of $_GET throughout the code, part two
was the incorporation of wrapper functions to handle specific
validation, verification and sanitization cases. This third part will
remove the use of the get_request_var_request() from the code. Part
four, and beyond will include the removal of both $_REQUEST and $_POST
super globals from the code.
cigamit