Installing the Securantis module on PrestaShop (1.7 → 9) and verifying prerequisites

But

This guide explains how to install the Securantis module on a PrestaShop store (supported versions: 1.7 to 9), verify the minimum prerequisites and perform the first checks in the back office to ensure the module is operational.

Prerequisites before installation

• Prepare a full backup (files + database). Any security operation must be reversible.
• PrestaShop administrator access (back office) with module installation rights.
• Verify that your PrestaShop installation is version 1.7 to 9. Do not install the module on an unlisted version without consulting us.
• FTP/SSH access and access to the PHP/server manager if needed for troubleshooting (error logs, PHP version).
• Have the ZIP file provided by Securantis (do not download from unofficial sources).

Installation steps (standard procedure)

1. Check the store status

   • Put the store into maintenance mode if you prefer to avoid any production impact during installation.
   • Note critical third‑party modules that are active (payment, shipping) in case a back‑office reload is required.

2. Install the module via the back office

   • Log in to the PrestaShop back office as an administrator.
   • In the module installation section, choose the option to add a module from a ZIP file.
   • Upload the Securantis ZIP and start the installation.
   • Wait for the installation confirmation without closing the page if the back office shows progress.

3. Immediate checks after installation

   • Confirm that the installation completed without errors.
   • A Securantis group of pages should appear in the administration menu (dashboard, scanner, firewall, 2FA, CAPTCHA, quarantine, logs, etc.).
   • If a message requests license activation, have your license information ready (separate activation, according to your contract).

4. Verify default settings (initial protections)

   • The module enables manual quarantine by default, but does not automatically allow quarantined modules/themes (secure behavior).
   • Administrator account protection (attempt control) is disabled by default; plan to enable it after configuring a protected administrator account.
   • Enable sending reports/notifications if you wish to receive alerts and summaries by email (check email configuration first).

Useful technical settings (observed behaviors)

• The scanner has a configurable maximum file limit; if no custom setting is provided, a reasonable default is used to avoid overload. You can adjust scan depth according to site size and available time.
• The module provides dedicated pages for the firewall, quarantine, notifications and the security report. These pages appear in the back office after installation.

Expected result

• The module is installed and appears in the back office with the Securantis sections.
• You can run an initial scan, review the logs and access quarantine and firewall options.
• Default settings protect without automatically deleting anything: any action on quarantined files or deletion requires a human decision.

Prudent settings recommended after installation

• Do not immediately change sensitive production settings (automatic quarantine mode, aggressive firewall rules): first test on a pre‑production store.
• Enable protection for one administrator account before activating global account protection.
• Configure email notifications and perform a send test from the module to confirm alerts.
• Enable SSL in PrestaShop configuration if not already enabled (recommended to secure administrative access).

Common errors and their causes

• Installation fails with a permissions error: check write permissions on the modules folder and the file owner on the server.
• The Securantis menu does not appear: refresh back‑office tab permissions and verify that module installation executed tab creation. If installation reported a warning, check server logs.
• The module installs but the scanner hangs or stops: PHP resource limits (max execution time, memory) may be insufficient for a full scan. Adjust PHP configuration or reduce the number of scanned files.
• Email notifications are not sent: verify PrestaShop email configuration (SMTP sending method), check the mail queue and test from the module notification test page.

Step‑by‑step troubleshooting

1. Check the logs

   • Review PHP/server logs (fatal errors, timeouts) and PrestaShop logs visible in the back office to find the source of an error.

2. Reinstall cleanly

   • Uninstall the module from the back office then reinstall after correcting permissions.

3. Verify PHP versions and extensions

   • Ensure the PHP version in use is compatible with your PrestaShop. If PHP extensions are missing (e.g. hash, OpenSSL), install them via your host.

4. Lightweight scan test

   • Run a scan with a reduced number of files to confirm the scan engine works before launching a full scan.

Important precautions

• Securantis offers quarantine actions and alerts, but does not automatically delete malicious files without human intervention. Any deletion or restoration must be validated by an administrator.
• Never transmit your passwords by email or chat.
• If you share access for paid assistance, use only the secure client area provided after payment.

When to contact Securantis support

Contact support if:

• Installation fails despite permissions and log checks.
• Securantis tabs do not appear in the back office after a successful installation.
• You encounter repeated scan blockages or abnormal firewall behavior impacting legitimate access.
• You need help activating the license or interpreting a critical security report.

What to provide to support (no passwords)

• Exact PrestaShop version (e.g. 1.7.x or 8.x/9.x).
• PHP version and enabled extensions.
• Precise description of errors and screenshots of the back office if possible.
• Server logs (PHP errors) or relevant excerpts of PrestaShop logs.

Conclusion

Installing the Securantis module on PrestaShop 1.7→9 is straightforward via uploading the ZIP from the back office. Respect the prerequisites, perform a backup before any operation, check permissions and test features (scan, notifications, dashboard access). If in doubt or if problems persist, contact Securantis support with the requested information for prompt assistance.