From c81ef6e25d9d5f7c3a1899a21f9987dae079deca Mon Sep 17 00:00:00 2001 From: Phil Davis Date: Mon, 27 Jun 2016 14:30:14 +0930 Subject: Always use require_once The usage of require() and require_once() throughout the system is inconsistent, and "bugs" come up now and then when the order of "requires" is a bit different and some require() happens after the include file is already included/required. It seems to me that there is no harm at all in always using require_once(). --- src/usr/local/www/load_balancer_virtual_server_edit.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/usr/local/www/load_balancer_virtual_server_edit.php') diff --git a/src/usr/local/www/load_balancer_virtual_server_edit.php b/src/usr/local/www/load_balancer_virtual_server_edit.php index 97ea70b..ff0dab4 100644 --- a/src/usr/local/www/load_balancer_virtual_server_edit.php +++ b/src/usr/local/www/load_balancer_virtual_server_edit.php @@ -61,7 +61,7 @@ ##|*MATCH=load_balancer_virtual_server_edit.php* ##|-PRIV -require("guiconfig.inc"); +require_once("guiconfig.inc"); if (isset($_POST['referer'])) { $referer = $_POST['referer']; -- cgit v1.1