-issue#920: Issue with scrollbars after update to 1.1.19 related to #902
-issue#921: Tree Mode no longer expands to accomodate full tree item
names
-issue#929: Overlapping frames on certain themes
If the plugin architecture does not exist, install will fail. Also
found php function version_compare not working in PHP 5.3.x.
There were additionally issues with the upgrade functions as well.
Resolving those too.
1) Make forms responsive. Work on mobile
2) Add a new header option to not hide specific columns
3) Resize textareas and text during resize to match window size
4) Change the responsive viewport media size for going responve
5) Make classic more responvie
6) Hide tabs fully in responive mode: todo: Generalized Elipsis
auth.php:
- get_auth_realms() small refactor
- is_graph_allowed() unused variable $graph and unnecessary if-statement
- auth_check_perms() one count of $objects instead of multiple
- is_device_allowed()unused variable $host and unnecessary if-statement
- is_graph_template_allowed()unused variable $template and unnecessary if-statement
- is_view_allowed() unnecessary if-statement
html_tree.php:
- 2x query refactor for use of index reference instead use of function
- deleted unused select statement
html_utility.php:
- isset_request_var() unnecessary if-statement
Convert all core pages to use multiple column sort. There may still be
some pages around automation that are required to be migrated. However,
they will continue to operate as is.
with this validation function, you can validate that a request variable
is a valid regular expression. this essentially will allow Cacti
developers to include regex's for search terms safely.
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