The Hide Items by Status Addon module for WHMCS requires a specific set of system and PHP extension components to run reliably. Our developers have tested it only under the following conditions, although it may function in other environments. You must have working knowledge of WHMCS addon and gateway configuration, PHP 5.6 or higher, WHMCS 7.x, OpenSSL with TLS 1.1 or higher support, cURL with TLS 1.1+ support, and IonCube Loader v10.1.x or higher. These constraints ensure the encoded module loads correctly, secure connections succeed, and no deprecated functions cause errors during operation.

#Why These Requirements Matter

Modern PHP versions deliver performance improvements, bug fixes, and critical security patches that older releases lack. WHMCS 7.x compatibility guarantees that the addon's hooks, database calls, and admin area integrations align with expected core behavior. Requiring OpenSSL and cURL to support TLS 1.1 or higher eliminates exposure to known protocol vulnerabilities and allows safe communication with external services or gateways the module may contact. The IonCube Loader is mandatory because the distributed addon files are encoded; an incompatible or absent loader produces fatal errors or displays raw encrypted code instead of executing the intended logic. Practical WHMCS experience helps you correctly place files, activate the addon, and diagnose any post-installation issues.

#System Requirements

  • Working knowledge of WHMCS, installing and configuring addons, gateways etc. Without this background you risk misconfiguration that prevents the module from hiding items by status as designed.
  • PHP 5.6 or higher. This baseline supplies language features and security updates required by the addon.
  • WHMCS 7.x. All testing was performed against this version family.
  • OpenSSL w/ TLS 1.1+ support. Essential for any outbound encrypted connections the module initiates.

#PHP Extension Requirements

  • cURL w/ TLS 1.1+ support. Must be compiled against an OpenSSL library that understands these protocols.
  • Ioncube loader v10.1.x or higher. Decrypts and runs the protected PHP files shipped with the addon.

#Using the Requirements Test Script

We supply a lightweight PHP script that inspects your environment and reports missing or outdated components. Download it directly from https://billing.aspnix.com/dl.php?type=d&id=138. Place the file in a publicly accessible directory on the same server that hosts your WHMCS installation, then open it in a web browser. The output lists every checked item with a pass/fail status, version numbers, and specific guidance for any failures.

Run the script before uploading any addon files. It examines the PHP runtime, loaded modules, TLS capabilities, IonCube presence, and attempts to detect your WHMCS version. This single step prevents hours of troubleshooting later. If you prefer command-line verification, the following commands provide a quick manual cross-check.

bash 
php -v
php -m | grep -E 'curl|ionCube'
curl -V

Review the curl -V output for supported protocols. Look for "TLS 1.1" and "TLS 1.2" in the list. If they are absent, you will need to update your cURL library or PHP package.

#Common Pitfalls and Resolutions

  • Running PHP older than 5.6. Upgrade the PHP handler in your control panel or via CLI, then re-test. Confirm the new version remains compatible with your WHMCS license.
  • IonCube Loader not installed or too old. Fetch the matching loader package for your PHP version and architecture from the official IonCube site, add the zend_extension line to php.ini, and restart the web server.
  • cURL lacks TLS 1.1+. Rebuild cURL against a recent OpenSSL or install an updated OS package. Verify with curl -V after changes.
  • WHMCS outside the 7.x branch. Although the module may load, untested behavior could surface. Stay on a supported WHMCS release or wait for an updated addon build.

After the test script returns all green indicators, follow the addon's included readme to copy files, activate it inside the WHMCS admin area, and configure status-based hiding rules. Address every flagged requirement first; doing so eliminates the majority of installation and runtime problems. If issues persist after meeting these specifications, supply the test script output when contacting support.