Fixed typos, removed unnecessary operators, updated documentation for new release

Author: Jared Hendrickson

README.md

@@ -21,22 +21,29 @@ webConfigurator are required to make calls to the API endpoints
 # Installation
 To install pfSense API, simply run the following command from the pfSense shell:<br>
 ```
-pkg add https://github.com/jaredhendrickson13/pfsense-api/releases/download/v1.0.0/pfSense-2-4-pkg-API-1.0_0.txz && /etc/rc.restart_webgui
+pkg add https://github.com/jaredhendrickson13/pfsense-api/releases/latest/download/pfSense-2.4-pkg-API.txz && /etc/rc.restart_webgui
 ```
 
-To uninstall, run the following command:<br>
+To uninstall pfSense API, run the following command:<br>
 ```
 pkg delete pfSense-pkg-API
 ```
 
+To update pfSense API to latest version, run the following command:
+```
+pkg delete pfSense-pkg-API && pkg add https://github.com/jaredhendrickson13/pfsense-api/releases/latest/download/pfSense-2.4-pkg-API.txz && /etc/rc.restart_webgui
+```
+
 ### Notes: 
+- pfSense API is supported on the pfSense 2.5 developer snapshots. To install the 2.5 package, simply change the `2.4` in the install URL to `2.5`.
 - In order for pfSense to apply some required web server changes, it is required to restart the webConfigurator after installing the package
 - If you do not have shell access to pfSense, you can still install via the webConfigurator by navigating to 
 'Diagnostics > Command Prompt' and enter the commands there
+- When updating pfSense, **_you must reinstall pfSense API afterwards_**. Unfortunately, pfSense removes all existing packages and only reinstalls packages found within pfSense's package repositories. Since pfSense API is not an official package in pfSense's repositories, it does not get reinstalled automatically.
 
 
 # UI Settings & Documentation
-After installation, you will be able to access the API user interface pages within the pfSense webConfigurator. These will be found under System > API. The settings tab will allow you change various API settings such as enabled API interfaces, authentication modes, and more. Additionally, the documentation tab will give you access to an embedded documentation tool that makes it easy to view the full API documentation with context to your pfSense instance.
+After installation, you will be able to access the API user interface pages within the pfSense webConfigurator. These will be found under System > API. The settings tab will allow you change various API settings such as enabled API interfaces, authentication modes, and more. Additionally, the documentation tab will give you access to an embedded documentation tool that makes it easy to view the full API documentation in context to your pfSense instance.
 
 ### Notes: 
 - Users must hold the `page-all` or `page-system-api` privileges to access the API page within the webConfigurator

docs/CONTRIBUTING.md

@@ -100,8 +100,8 @@ writing a model that tests user's local database credentials and do not want the
 auth mode you would specify `$this->set_auth_mode = "local";` to always force local authentication. Defaults to the 
 API's configured auth mode in the /api/ webConfigurator page.
 
-- `$this->set_read_mode` : Allows the read only API setting to be bypassed for this model. If you set this value to 
-`true` the model will be allowed to use POST, PUT or DELETE methods even when the API is in read only mode. There is 
+- `$this->set_read_mode` : Allows the read-only API setting to be bypassed for this model. If you set this value to 
+`true` the model will be allowed to use POST, PUT or DELETE methods even when the API is in read-only mode. There is 
 rarely a use case for this. Do not override this property unless absolutely needed. 
 
 - `$this->change_note` : Sets the description of the action that occurred via API. This value will be shown in the 

docs/documentation.json

@@ -123,7 +123,7 @@ class APIAuth {
         # If no require privileges were given, assume call is always authorized
         if (!empty($this->req_privs)) {
             # If API is in readonly mode, only allow GET requests
-            if ($this->read_mode === false or ($this->read_mode === true and $_SERVER['REQUEST_METHOD'] === "GET")) {
+            if (!$this->read_mode or ($this->read_mode and $_SERVER['REQUEST_METHOD'] === "GET")) {
                 # Loop through each of our req privs and ensure the client has them, also check if access is read only
                 foreach ($this->req_privs as &$priv) {
                     if (in_array($priv, $this->privs)) {

pfSense-pkg-API/files/etc/inc/api/framework/APIAuth.inc

@@ -37,12 +37,8 @@ class APIModel {
         error_reporting(E_ERROR);
         $this->config =& $config;
         $this->privileges = ["page-all"];
-        $this->client = null;
         $this->requires_auth = true;
-        $this->set_auth_mode = null;
-        $this->bypass_read_mode = null;
         $this->change_note = "Made unknown change via API";
-        $this->id = null;
         $this->validate_id = true;
         $this->initial_data = APITools\get_request_data();
         $this->validated_data = [];

pfSense-pkg-API/files/etc/inc/api/framework/APIModel.inc

@@ -88,17 +88,12 @@ class APIFirewallRuleUpdate extends APIModel {
         if (isset($this->initial_data['protocol'])) {
             $missing_port = (!in_array($this->validated_data["protocol"], ["tcp", "udp", "tcp/udp"])) ? true : false;
             $requires_port = (in_array($this->initial_data["protocol"], ["tcp", "udp", "tcp/udp"])) ? true : false;
+            $this->unset_ports();
             $protocol_options = [
                 "any", "tcp", "udp", "tcp/udp", "icmp", "esp", "ah",
                 "gre", "ipv6", "igmp", "pim", "ospf", "carp", "pfsync"
             ];
 
-            # If a new protocol was chosen that doesn't require a port, remove existing ports from the rule
-            if ((!in_array($this->initial_data["protocol"], ["tcp", "udp", "tcp/udp"]))) {
-                unset($this->validated_data["source"]["port"]);
-                unset($this->validated_data["destination"]["port"]);
-            }
-
             # Check that our protocol value is a support option
             if (in_array($this->initial_data["protocol"], $protocol_options)) {
                 # Don't add a specific protocol if any
@@ -196,7 +191,6 @@ class APIFirewallRuleUpdate extends APIModel {
             }
         }
 
-
         # Check for our optional 'disabled' payload value
         if ($this->initial_data['disabled'] === true) {
             $this->validated_data["disabled"] = "";
@@ -225,4 +219,13 @@ class APIFirewallRuleUpdate extends APIModel {
             "username" => $this->client->username."@".$this->client->ip_address." (API)"
         ];
     }
+
+    # Removes port specifications when updating to a protocol that is not port based
+    private function unset_ports() {
+        # If a new protocol was chosen that doesn't require a port, remove existing ports from the rule
+        if ((!in_array($this->initial_data["protocol"], ["tcp", "udp", "tcp/udp"]))) {
+            unset($this->validated_data["source"]["port"]);
+            unset($this->validated_data["destination"]["port"]);
+        }
+    }
 }