Customer Extra Info (IP Ban): setup and help

1. Upload Customer Extra Info (IP Ban) in Modules > Module Manager.
2. Open Configure to reach Settings.
3. Review the collection and order-panel switches and save.
4. Log in to the storefront as a test customer. Wait for the collector request, then inspect the customer in the back office.
5. Add trusted addresses in IP Whitelist before testing a ban in Banned IPs.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.

The module also installs TRACK_OS, TRACK_BROWSER, TRACK_SCREEN and TRACK_USERAGENT as 1. The collector reads them, but the current Settings form has no controls for them. They govern operating-system, browser/version, screen and raw user-agent storage. They do not suppress IP, country or device-type collection.

The customer panel shows the latest collected IP, country, operating system, browser/version, screen dimensions, device type and collection date, plus recorded IP history. When Show Info on Orders is enabled, the order panel uses the order's customer record.

The browser collector loads through displayHeader and requests the module's collect controller about 1.5 seconds after the page is ready. It sends window.screen dimensions, not viewport dimensions. With working sessionStorage it records a sent request once per browser tab session. If storage is unavailable it can try again on later pages.

Server-side collection also runs after successful customer login and new account creation. It suppresses a new row for the same IP and customer or guest within one hour. A later screen request can fill missing dimensions in an existing recent row. These recorded dates are not a continuous live-presence history.

Country detection tries Cloudflare's country header, then available PrestaShop GeoIP support, then the country cookie. It can return no country. Country rules depend on those values.

Open IP Whitelist and add your trusted address or network:

Examples include exact 203.0.113.10, wildcard 203.0.113.* and CIDR 203.0.113.0/24. Whitelist matching uses the same IP matcher as bans. It runs before ban matching and overrides country and user-agent rules too.

Records store the shop context. Whitelist checks in multishop include the current shop and entries with shop ID 0. Ban rules with a positive shop ID apply only to that shop; 0 means all shops.

Open Banned IPs, add a rule and fill one matching criterion for your first test.

The stored values are full, checkout and auth. If several matching criteria are present in one rule, they act as alternative matches. They do not mean the visitor must match every field.

Full bans apply everywhere in the front office. Checkout scope matches controller names order, orderopc, cart, supercheckout, onepagecheckout and checkout. Account scope matches authentication, my-account, identity, registration and password. Scope follows the requested page controller; custom checkout or account routes must use the matching controller names.

A matching rule returns HTTP 403 Forbidden with the Access Restricted page. There is no redirect. Expired active bans are deactivated during a later ban check, not by a required cron job.

Test from an address that you control while keeping your own trusted connection whitelisted. Confirm a full ban blocks browsing, a checkout ban affects the expected checkout controllers, and an inactive or expired rule no longer blocks that request. Confirm whitelisted requests pass.

The admin lists support filtering, edit/delete and export. The ban list includes bulk enable/disable. Review staff access to those module screens using PrestaShop employee profiles.

For a temporary checkout test, use an IPv4 range, Ban Type checkout, Active Yes and an expiry in the future. Dates earlier than the test time deactivate the rule.

• If a ban does not apply, check Enable IP Banning, Active, expiry, scope, shop and whitelist matches first.
• Check the IP and country that the shop detects, especially behind a proxy. A browser's location or your expected public IP may differ from the request data used by the module.
• IPv4 ranges and CIDR use ip2long. Use exact matching for IPv6; the module does not implement IPv6 subnet matching.
• Regex matching runs only when the first and last characters are /. A pattern with flags after the closing slash is treated as plain text by this detection rule.
• If customer screen information is empty, inspect the delayed collect request and JavaScript errors. A blocked request or an already-set sessionStorage flag can prevent a new request.
• If an order panel is absent, check Show Info on Orders and your admin page's hook support. Collection history starts when you enable collection; there is no historical-device import.

The module uses displayHeader, actionFrontControllerInitBefore, displayAdminCustomers, displayAdminOrder, displayBackOfficeHeader, actionAuthentication and actionCustomerAccountAdd. Theme/admin stylesheet adjustments can target .mprceiipban-panel, its .panel-heading, .badge and table cells.

Turn off Enable Data Collection and Enable IP Banning separately to suspend those actions. Uninstall from Module Manager removes module configuration, admin entries and the module schema, including collected information, bans and whitelist records. Back up those records first if you need them later.